We have postscripts all set up on our development machine but

now it's time to install it in production as well.

I'm using an Ubuntu server Linux installation on a virtual machine but

the process should be similar if you have a web host.

See the teacher's notes if you'd like more info.

So first we're going to need to establish an ssh connection to the host.

So I'm going to log in as my deployment user on my host machine.

And then we need to install postscripts itself which will do using a Ubuntu

package manager software.

So this is an administrative command so I'm going to need to prefix it with sudo.

Then I'll run the apt get command.

That's Ubuntu package manager or on the install sub command and

then we need the names of the software packages we wanna install.

The first is going to be postpressql itself.

And the second is a set of development libraries that we're

going to need to compile the pggem so that rails can communicate with postgress.

So I'm going to install libpq-dev.

Hit enter to run that only to provide my deployment user's password.

Since I'm running a sudo command.

I'll confirm that I want to install everything.

Now as I mentioned post press ports multiple users we're going to need to

create a postscripts account for our rails out to actually connect to the database.

So let's run a command to create that now.

In addition to installing the postscript server, the apps get command we

ran will create a postscript user with full control over postscript.

So, we are going to run this command as that postscript user.

So we use this sudo command and will specify with the -u command line flag.

That this command should be run as the new postgres user.

Then we're going to run a command that got installed along with postgres called

the create user.

This will create a new user for the postgres database.

We want this user to be a super user, so

we'll add the command line flag double dash superuser

that will give them full control over that of base and we want this use it be named

deploy the same as the deployment user that we use for our rails out.

Note that this is also the same username that we set up

in our database dot yaml configuration for the Rails app.

So we'll run this command and create the user we need.

Now let's change into the directory for Rails app.

I've committed the configuration changes I made on my own development machine to get

and I've pushed them out to the origin repo.

Now pull them down to the production app.

With git pull, we're also going to be back shortly to create

the database here production to do that with RAILS_ENV =

production to set the RAILS-ENV environment variable.

And then we run the bin/rails command, db set up just like we did in development.

That will create the production database for us and load the schema.

And now we should be ready to run the bin/rails server command in production.

Let's visit our browser.

Type in the address for our host.

Port 3000, And here's our list of signatures.

Let's try creating a New Signature.

Looks like it was saved.

Our app is working with our postgrass database in production.

So there you have it, we have our rails app configured to work with a postgrass

database, pretty easy right.

Postgrass is by and large a drop in replacement for SQLite.

But you'll find that it's much faster and more stable.

If you having trouble replicating these steps on your own set up,

be sure to check the teacher's notes for hints and troubleshooting tips.

Hope you have fun trying out your new database.