Dokku + DigitalOcean droplet and managed postgres.
1. The migration - from "I just learned about Dokku" to "deployed my app for testing" - took about two hours.
2. I'm an urban planner who dabbles in front-end development. DevOps is not my thing.
3. Not too valuable of learnings. Overall, the dokku commands are almost identical to heroku commands (by design). So the transition was smooth and comfortable.
4. Costs: I chose droplet and postgres services with DO that equaled our heroku costs. But we get about 4x the ram now. The site is much faster.
5. Rails/postgres. We don't track hits, but it's pretty popular in terms of, uh, maps for finding pinball machines.
6. I haven't figured out how to set up logging. I would like some kind of "last 5 days of logs, being piped to somewhere." It seems simple, but I don't quite get it yet. I also miss the "usage" metrics from heroku that showed ram and stuff throughout the day. But I guess I pretty much get that with DO and Scout APM.
1. The migration - from "I just learned about Dokku" to "deployed my app for testing" - took about two hours.
2. I'm an urban planner who dabbles in front-end development. DevOps is not my thing.
3. Not too valuable of learnings. Overall, the dokku commands are almost identical to heroku commands (by design). So the transition was smooth and comfortable.
4. Costs: I chose droplet and postgres services with DO that equaled our heroku costs. But we get about 4x the ram now. The site is much faster.
5. Rails/postgres. We don't track hits, but it's pretty popular in terms of, uh, maps for finding pinball machines.
6. I haven't figured out how to set up logging. I would like some kind of "last 5 days of logs, being piped to somewhere." It seems simple, but I don't quite get it yet. I also miss the "usage" metrics from heroku that showed ram and stuff throughout the day. But I guess I pretty much get that with DO and Scout APM.