Make changes to drastically simplify site maintenance; Make blog and wiki to use static site generator
Opened this issue · 1 comments
renoirb commented
We run with about 20 VMs. 14 of them are about sustaining possible load and to support both WordPress and MediaWiki.
Objective of this task is to simplify system infrastructure and maintenance.
Tasks
- Export Wiki edit history into Git and make a static site generator version of the wiki (see webplatform/docs README file for progress report)
- Migration scripts and library in webplatform/content-converter, and import script in webplatform/mediawiki-conversion
- Content migrated in webplatform/docs
- WPD namespace in webplatform/docs-wpd
- Meta namespace in webplatform/docs-meta
- User profiles and old comments
- Export Blog content into a static site generator
- Refactor the homepage to use the same static site generator as the blog and wiki
- Rebuild only required servers
VMs in use
| Quantity | Role name | Required only by blog/wiki/project |
|---|---|---|
| 4 | app | yes |
| 2 | sessions | (incidental) yes |
| 2 | redis | (incidental) yes |
| 2 | db | (incidental) yes |
| 4 | frontend | no |
| 1 | blog | yes |
| 1 | bots | no |
| 1 | project | yes |
| 1 | source | no |
| 2 | docker | no |
| 1 | stats | no |
| 2 | elastic | no |
| 1 | postgres | no |
| 1 | salt | yes |
| 1 | accounts | no |
Since we are’t going to host Discourse, that we’ll shut down project.webplatform.org to use GitHub issues, let W3C monitor the IRC channel, and stop using our own installation of Piwik we can also remove most of the infrastructure by this work item.
All that would be left is the static content, we might only really need only [frontend, salt]
renoirb commented
This should be closed, but since I'm going to write about it, here are a few links I had scattered around about this.