Containerise small services on Ridley
Opened this issue · 3 comments
grischard commented
Left to containerise on Ridley:
Wordpress
- 2007.stateofthemap.org
- 2008.stateofthemap.org
- 2009.stateofthemap.org
- 2010.stateofthemap.org
- 2011.stateofthemap.org
- 2012.stateofthemap.org
- blog.openstreetmap.org
Mediawiki
- board.osmfoundation.org
- dwg.osmfoundation.org
- mwg.osmfoundation.org
- osmfoundation.org
Wordpress with civicrm
- supporting.openstreetmap.org
Perl
- otrs.openstreetmap.org (#518)
grischard commented
Discussed this with Grant today. For wordpress, he's working to an immutable container (with all plugins / themes baked in). Runtime cannot be changed and runs effectively underprivileged user.
Compared to letting chef handle the wordpress container and the themes/plugins, this makes CI testing and running staging/dev versions easier, at the cost of significant development time. Grant and I have agreed that if the immutable container route wasn't in production by our Monday meeting, we'd go the 'quick' chef route.
Firefishy commented
The initial cut of the immutable wordpress container is available here: https://github.com/openstreetmap/wordpress-container
- Container has additional PHP extensions and dependencies baked in as required by plugins.
- Container runs underprivileged (eg: cannot modify any wordpress files).
- Container bundles all plugins and themes (baked-in).
- On start-up DB migrations are run and all plugins are activated (needs DB access).