Hacker News new | past | comments | ask | show | jobs | submit login

I have a really extensive Ansible playbook for setting up my stack; nginx with extra modules, postgres, redis, and others like fail2ban. It all targets CentOS and also configures SELinux when appropriate. It all works well, until I want to do something that doesn't fit the mold that I've put myself in.

For example, I wanted to get off Google Analytics and try out Piwik, which uses PHP and requires MySQL, Postgres isn't supported. It would have been really difficult to write out a bunch of Ansible config for PHP and MySQL, both technologies I'm not familiar with and don't know their best practices. So, I'm still using Google analytics. A similar story happened when I wanted to host a Tor relay.

The allure of just pointing Dokku/Flynn to a pre-made Dockerfile for Piwik/Tor/ownCloud/etc. is pretty compelling. It let's me mix and match technologies without feeling like I'm polluting my server with a bunch of random services and tech. Containerization provides just enough separation to make me happy.

I'm not sure if Dokku or Flynn is the golden goose I'm after, but it seems like a step in the right direction.

I still use Ansible to do basic provisioning like users and SSH keys, setting up Fail2ban, and installing Dokku.




Hearing your workflow/tooling is handy and I may borrow an idea or two while playing around, thanks for writing this up :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: