#Postgres app rails code

Rails should now have everything it needs to run. I’ve set both the rails app and the db (PostgreSQL) to always restart with restart: always.

To find out which version you can define at the top of your file check docker -v and compare to the version reference here. Saving your file concludes all initial configuration steps of the app. Next create a docker-compose.yml file in the root directory of your project. This was taken into account when creating the database.yml file so that value was pre-populated for us.Īs for the database names, Rails assumes that’s how they’re going to be named, first the name of the app followed by the environment, all lowercase and words separated by underscores.

need to make sure there is a database named postgres in your TimescaleDB deployment.

When creating the app we specified a database adapter with -d postgres. Lets start by creating a new Rails application configured to use. Ive always worked with Postgresql (postgres).

#Postgres app rails code

Now notice how there’s three blocks, why is that? It is because Rails has three environments that it makes use of, development is the one running on our machine, production is the one everyone gets to use and test is used to run tests that make sure our code does what is supposed to do.Īlso notice that the database for each environment matches the database names of the ones we created earlier and the adapter is already set to postgres but the Rails default is sqlite. .gives you all you need to get started developing an application, notably using SQLite as the default datastore.