![]() Once configured, your database.yml should contain something like this: For each database, ensure that the username and password match the username and password you gave your Postgres user. This is handy because, for example, the test database is emptied and rebuilt every time you run Rails tests. By default Rails will expect a different database for each environment. There are a few databases listed here for different environments development, test, and production. It uses YAML, a data serialization standard. The database.yml file is used by Rails to connect to the appropriate database for the current Rails environment. In the above example, it would be at /myapp (relative to your current location). Note: RAILS_ROOT is the Rails root directory. This is done using the database.yml file, located at: We will now configure which database Rails will talk to. Rails expects the name of the database user to match the name of the application, but you can easily change that if need be. This creates a directory called "myapp" which houses an app called "myapp" (you can name it anything you like when running the command). To create a Rails app configured for Postgres, run this command: Then create a user (or a "role", as Postgres calls it):Ĭreate role myapp with createdb login password 'password1' To do this, switch into the Postgres user: To do so:Ĭreate a Postgres user for the Rails app we'll create in the next step. pgAdmin isn't the prettiest tool in the world, but it does the job.įinally, you'll want to install the pg gem so that you can interface with Postgres from Ruby code. If you are installing Postgres on a local machine you may also want to install a GUI (though this guide assumes command line usage). Generally it's easiest to use a package manager such as apt-get on Ubuntu or Homebrew on OS X. The method of installing Postgres depends on your OS. This will install Rails and any other gems it requires. Instead you can simply install Rails by installing the gem: If you already have RVM installed, you don't need to re-install it. This is useful as you may require different versions of Ruby for different projects. ![]() You can now use it to manage your Ruby versions. Note: you should review the RVM install script before running it (or any other remote script that you pipe into bash. RVM can install Ruby and Rails automatically as part of its installation. If you already have RVM installed, skip to the next section. To install RVM you will need to ensure your system has curl installed (how you do this depends on your OS). The easiest way to install Rails is using RVM, which also installs Ruby. ![]() You can follow the guide on your local machine or a VPS. By default it assumes that MySQL is being used, but it's quite easy to use with Postgres instead.This guide will step you through creating a Rails application that uses a Postgres database. Rails is database agnostic, meaning it can be used with a variety of different databases. If your application requires the scalability, centralization, and control (or any other feature) that is provided by a client/server SQL database, such as PostgreSQL or MySQL, you will need to perform a few additional steps to get it up and running. Ruby on Rails uses sqlite3 as its default database, which works great in many cases, but may not be sufficient for your application.
0 Comments
Leave a Reply. |