django-simple-deploy VS dockerfile-rails

If it will not handle any kind of personal information, I use django-simple-deploy and deploy it to fly.io

A library called django-simple-deploy can help here massively https://github.com/ehmatthes/django-simple-deploy, but it still requires some CLI knowledge. Another option for easy hosting would be Appliku (https://appliku.com/) again their aim is to make it easy for you deploy without needing all the other stuff.

Hello there, you can use this https://github.com/ehmatthes/django-simple-deploy which essentially deployment steps grouped and wrapped to be reusable and simple to use , currently support heroku and platform.sh and once your comfortable with it you can expand support to other platforms .

If you want to automatically generate Dockerfiles for more versions of Rails (not just the latest) that detect OS packages that need to be installed from gems present in your Gemfile, check out https://github.com/fly-apps/dockerfile-rails

You can install it in your rails app by running:

1. bundle add dockerfile-rails

2. rails g dockerfile

> I felt bad

Don't. I can honestly say that I didn't write this post targeting HN. I'll go further... this post wasn't meant for people who are unlikely to use https://github.com/fly-apps/dockerfile-rails#overview. I recently added some features to that gem whose usage may not be intuitively obvious. I wrote this post to explain some of the motivation for those features.

I don't know how to mark posts as not intended for HN (and truth be told, if there was such a feature, I'd be inclined to overuse it). I don't know where else I should have posted this content, but I'm not sure I would be inclined to move it. In any case, this post, as written, serves a purpose for me. Somebody not you and not me felt it belonged here. We can both second guess that decision. Either way, there is no reason for either of us to feel bad.

Did you try migrating with this guide? https://fly.io/docs/rails/getting-started/migrate-from-herok...

The issues you ran into with older versions of Rails was probably because the Dockerfile that `fly launch` generated was for new versions of Rails. We switched to https://github.com/rubys/dockerfile-rails to streamline Dockerfile generation and support older versions of Rails.

If you try it again and run into issues you can open an issue at https://github.com/rubys/dockerfile-rails/issues or post in https://community.fly.io and somebody will help get that sorted out.

The more versions of Rails we can deploy the better!

At the moment Rails is focused on simplicity/readability. I've got a gem that I'm proposing (and DHH is evaluating) that adds caching as an option: https://github.com/rubys/dockerfile-rails#overview

even though the article does not go deep into multistage builds Fly.io does provide cookbooks and even a link to a Rails generator there.