Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update what Rackspace is used for #1849

Merged
merged 1 commit into from
Jul 10, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,8 @@ Fork https://github.com/theforeman/foreman-infra and add your key into the [file
A list of the hosting we have, who provides it, and what capacity it has

### Rackspace
* Previously sponsored, [being phased out](https://community.theforeman.org/t/rfc-moving-off-of-rackspace-infrastructure/17932)
* Hosts Jenkins and Foreman
* Previously sponsored, now paid by Red Hat
* Used for Mailgun to send email from Redmine and Discourse
* Contact support from our account as needed
### Scaleway
* Previously sponsored, planned to be phased out
Expand Down
1 change: 0 additions & 1 deletion docs/webserver.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,6 @@ The major points of the configuration are:
* Set the backend to `web02.theforeman.org`
* Enable shielding: a central system fetches the assets and then distributes them across the CDN instead of each CDN node fetches them itself, this costs more CDN traffic, but less traffic for web02 which is more expensive
* Configure a health-check and serve stale content when it fails
* Log requests to a RackSpace CloudFiles (S3-like) bucket

#### TLS

Expand Down