As we march towards v1 I would like us to tighten up our base docker image for release.
Issues I would like to see addressed:
- Sane/comprehensive logging strategy.
- Review of cron jobs.
- Update all software, add missing stuff.
- Document the base image
Comprehensive logging strategy
Logging is a bit all-over-the-place, some stuff shows up in
./launcher logs , some stuff is trapped in
/var/logs. We need to have sane simple logging story. Log rotation should be running, logs should be pulled out of container in sample configs so you don’t lose a pile of logs on re-bootstrap.
Review of cron jobs
What cron jobs do we need to run? Does it make sense to even backup discourse seeing it is built in?
Update all software, add missing stuff.
For v1 we should be on latest ruby 2.0, NGINX should be updated, PG updated to latest stable, OS packages updated. I always trip on VIM missing, I think we should add it.
###Document the base image
Explain what the base image is, what it has and how its configured somewhere. Even as a meta topic.
@supermathie feedbacks? anything missing? Ideally you can take this one.
Also, we should review @honglilai’s GitHub - phusion/baseimage-docker: A minimal Ubuntu base image modified for Docker-friendliness to see if we want to borrow any concepts.