A TECH PLACE

Getting comfortable with Terminal is extremely important for Rails development, and general administration needs.

Here are some of the common commands.

Show the logged in as user

$ whoami

$ whoami

List contents of the current directory

$ ls

$ ls

List contents of current directory and permissions

$ ls -li

$ ls -li

Change directory – go back one level

$ CD ..

$ CD ..

Change directory – go into directory “xyz”

$ cd "xyz"

1	$ cd "xyz"

Show your current path – print working directory

$ PWD

$ PWD

remove / delete a file “xyz.file”

$ rm "xyz.file"

1	$ rm "xyz.file"

remove / delete a folder and all of its sub contents (be careful with this one)

$ rm -rf "xyz"

1	$ rm -rf "xyz"

Create a directory – make

$ mkdir "xyz"

1	$ mkdir "xyz"

Create a file

$ touch "xyz.txt"

1	$ touch "xyz.txt"

copy a file

$ cp "xyz.txt"

1	$ cp "xyz.txt"

run as super user

$ sudo "your command"

1	$ sudo "your command"

clear screen

$ clear

$ clear

If you already have Rails setup the defaults are to create a connection for a SQLite database.

To switch this to a PostgeSQL database.

First install a PostgreSQL database on your machine for dev and test.

For apple computers, I suggest the Postgres.app.

You also need the PG gem which connects PostgeSQL to Rails. To verify everything is ready to go, run

$ gem install pg

1	$ gem install pg

To create a new project with a PostgreSQL database run

$ rails new 'mynewproject' -d postgresql

1	$ rails new 'mynewproject' -d postgresql

This creates a new project connected postgresql

The connection settings for you new project are in the database.yml under config. Here are the default settings as of rails 4.2.4.

# PostgreSQL. Versions 8.2 and up are supported.
#
# Install the pg driver:
# gem install pg
# On OS X with Homebrew:
# gem install pg -- --with-pg-config=/usr/local/bin/pg_config
# On OS X with MacPorts:
# gem install pg -- --with-pg-config=/opt/local/lib/postgresql84/bin/pg_config
# On Windows:
# gem install pg
# Choose the win32 build.
# Install PostgreSQL and put its /bin directory on your path.
#
# Configure Using Gemfile
# gem 'pg'
#
default: &default
 adapter: postgresql
 encoding: unicode
 # For details on connection pooling, see rails configuration guide
 # http://guides.rubyonrails.org/configuring.html#database-pooling
 pool: 5

development:
 <<: *default
 database: mynewproject_development

 # The specified database role being used to connect to postgres.
 # To create additional roles in postgres see `$ createuser --help`.
 # When left blank, postgres will use the default role. This is
 # the same name as the operating system user that initialized the database.
 #username: mynewproject

 # The password associated with the postgres role (username).
 #password:

 # Connect on a TCP socket. Omitted by default since the client uses a
 # domain socket that doesn't need configuration. Windows does not have
 # domain sockets, so uncomment these lines.
 #host: localhost

 # The TCP port the server listens on. Defaults to 5432.
 # If your server runs on a different port number, change accordingly.
 #port: 5432

 # Schema search path. The server defaults to $user,public
 #schema_search_path: myapp,sharedapp,public

 # Minimum log levels, in increasing order:
 # debug5, debug4, debug3, debug2, debug1,
 # log, notice, warning, error, fatal, and panic
 # Defaults to warning.
 #min_messages: notice

# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
 <<: *default
 database: mynewproject_test

# As with config/secrets.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database.
#
# Instead, provide the password as a unix environment variable when you boot
# the app. Read http://guides.rubyonrails.org/configuring.html#configuring-a-database
# for a full rundown on how to provide these environment variables in a
# production deployment.
#
# On Heroku and other platform providers, you may have a full connection URL
# available as an environment variable. For example:
#
# DATABASE_URL="postgres://myuser:mypass@localhost/somedatabase"
#
# You can use this database configuration with:
#
# production:
# url: <%= ENV['DATABASE_URL'] %>
#
production:
 <<: *default
 database: mynewproject_production
 username: mynewproject
 password: <%= ENV['MYNEWPROJECT_DATABASE_PASSWORD'] %>

# PostgreSQL. Versions 8.2 and up are supported.

# Install the pg driver:

# gem install pg

# On OS X with Homebrew:

# gem install pg -- --with-pg-config=/usr/local/bin/pg_config

# On OS X with MacPorts:

# gem install pg -- --with-pg-config=/opt/local/lib/postgresql84/bin/pg_config

# On Windows:

# gem install pg

# Choose the win32 build.

# Install PostgreSQL and put its /bin directory on your path.

# Configure Using Gemfile

# gem 'pg'

default: &default

adapter: postgresql

encoding: unicode

# For details on connection pooling, see rails configuration guide

# http://guides.rubyonrails.org/configuring.html#database-pooling

pool: 5

development:

<<: *default

database: mynewproject_development

# The specified database role being used to connect to postgres.

# To create additional roles in postgres see `$ createuser --help`.

# When left blank, postgres will use the default role. This is

# the same name as the operating system user that initialized the database.

#username: mynewproject

# The password associated with the postgres role (username).

#password:

# Connect on a TCP socket. Omitted by default since the client uses a

# domain socket that doesn't need configuration. Windows does not have

# domain sockets, so uncomment these lines.

#host: localhost

# The TCP port the server listens on. Defaults to 5432.

# If your server runs on a different port number, change accordingly.

#port: 5432

# Schema search path. The server defaults to $user,public

#schema_search_path: myapp,sharedapp,public

# Minimum log levels, in increasing order:

# debug5, debug4, debug3, debug2, debug1,

# log, notice, warning, error, fatal, and panic

# Defaults to warning.

#min_messages: notice

# Warning: The database defined as "test" will be erased and

# re-generated from your development database when you run "rake".

# Do not set this db to the same as development or production.

test:

<<: *default

database: mynewproject_test

# As with config/secrets.yml, you never want to store sensitive information,

# like your database password, in your source code. If your source code is

# ever seen by anyone, they now have access to your database.

# Instead, provide the password as a unix environment variable when you boot

# the app. Read http://guides.rubyonrails.org/configuring.html#configuring-a-database

# for a full rundown on how to provide these environment variables in a

# production deployment.

# On Heroku and other platform providers, you may have a full connection URL

# available as an environment variable. For example:

# DATABASE_URL="postgres://myuser:mypass@localhost/somedatabase"

# You can use this database configuration with:

# production:

# url: <%= ENV['DATABASE_URL'] %>

production:

<<: *default

database: mynewproject_production

username: mynewproject

password: <%= ENV['MYNEWPROJECT_DATABASE_PASSWORD'] %>

Terminal 101 Basic’s

Basic Rails commands on Heroku

Basic Heroku setup

Create a Rails project with a postgresql database

Common Rake Commands

Managing your Gem’s

Create a new Rails project with a specific version