SQLite & Rails in Production article

,
1

Not sure whether this is the place to do it, but I’d like to suggest a correction/update to this article: SQLite & Rails in Production · The Ruby Dispatch

It says after running fly launch

This will create a fly.toml file in your project working directory environment, and provision resources on Fly.io. A Dockerfile is also generated, which is a description of the server that will be running in production.

You should see a LITESTACK_DATA_PATH environment in your Dockerfile that points to /data. Litestack uses this path to know which folder to save SQLite databases for caching, job processing, and ActionCable.

Much later in the article it says:

When the fly launch command is run, Fly.io runs the dockerfile-rails gem, which detects the Litestack gem and configures the Dockerfile with the VOLUME and ENV directives needed to store and access SQLite databases on persistent volume.

The problem is if you have a fresh Rails app of your own and you don’t have that dockerfile-rails gem installed, you might end up going down the rabbit hole like I did of reading up about creating your own volumes etc when the gem sets up the scripts to do all that for you.

Otherwise great article and the reason I started using Fly.io in the first place :smiley:

cc @Brad

1 Like
2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.