... | ... | @@ -565,7 +565,22 @@ powerful and provides a reasonably easy to deploy, high availability |
|
|
service, at the cost of some level of obscurity, complexity, and high
|
|
|
disk space requirements.
|
|
|
|
|
|
### Replacing with GitLab and cache
|
|
|
## Cost
|
|
|
|
|
|
Staff, mostly. We expect a reduction in cost if we reduce the number
|
|
|
of copies of the sites we have to keep around.
|
|
|
|
|
|
## Alternatives considered
|
|
|
|
|
|
<!-- include benchmarks and procedure if relevant -->
|
|
|
|
|
|
* [GitLab pages](https://docs.gitlab.com/ee/administration/pages/) could be used as a source?
|
|
|
* the [cache system](cache) could be used as a replacement in the
|
|
|
front-end
|
|
|
|
|
|
TODO: benchmark gitlab pages vs (say) apache or nginx.
|
|
|
|
|
|
### GitLab pages replacement
|
|
|
|
|
|
It should be possible to replace parts or the entirety of the system
|
|
|
progressively, however. A few ideas:
|
... | ... | @@ -632,21 +647,6 @@ This would mean a new service, but would allow us to retire Jenkins |
|
|
without rearchitecturing the entire static mirroring system (see above
|
|
|
for the idea of replacing it with GitLab pages).
|
|
|
|
|
|
## Cost
|
|
|
|
|
|
Staff, mostly. We expect a reduction in cost if we reduce the number
|
|
|
of copies of the sites we have to keep around.
|
|
|
|
|
|
## Alternatives considered
|
|
|
|
|
|
<!-- include benchmarks and procedure if relevant -->
|
|
|
|
|
|
* [GitLab pages](https://docs.gitlab.com/ee/administration/pages/) could be used as a source?
|
|
|
* the [cache system](cache) could be used as a replacement in the
|
|
|
front-end
|
|
|
|
|
|
TODO: benchmark gitlab pages vs (say) apache or nginx.
|
|
|
|
|
|
<!-- LocalWords: atomicity DDOS YAML Hiera webserver NFS CephFS TLS
|
|
|
-->
|
|
|
<!-- LocalWords: filesystem GitLab scalable frontend CDN HTTPS DNS
|
... | ... | |