# Deploying Apostrophe to a Linode linux server quickly
Linode is a popular provider of Linux VPSes (Virtual Private Servers). A VPS is a great fit for most Apostrophe sites because it can easily accommodate MongoDB, Apostrophe and your content at a fixed, low monthly price. Setting it up is usually much simpler than using a "cloud provider" like AWS or Heroku, unless you have a true need to operate at a very large scale.
You can follow our deployment tutorial on Linode — in fact, we tested it on Linode, although it works fine with any Linux server. And we recommend skimming that tutorial first to get the general idea. But, you can skip most of the steps by using our Linode "Stackscript."
To do that, just follow along:
Log into your Linode account, or create one if you're new to Linode.
Create a new Linode (a new VPS). Make sure your "instance type" has at least 2gb of RAM ("Linode 2048" or bigger). As of this writing this is priced at $10/month.
Click on the new Linode in your dashboard. (Tip: it'll be the one that says "Being Created.")
Click "Deploy an Image."
Click "Deploying using StackScripts."
Under "Community StackScripts," search for Apostrophe.
The correct StackScript will identify itself as "punkave / Apostrophe CMS"./ Click that entry.
Supply a secure, unique password for the "nodeapps" Linux user. You'll need this password for deployment; write it down. Do not use your Linode password.
Supply a secure, unique password for the "root" user too, and write that down. Do not use the same password.
Leave the other fields as-is.
When the "Disk Create" step finishes, click "Boot."
When "Boot" completes, click "Remote Access." Under "SSH Access," you'll see a suggested command to access the server as root. Write down the IP address.
deploymentfolder of your Apostrophe site on your computer,copy
settings. Then change the
PROJECT=apostrophesetting to match your
deploymentfolder, also copy
a.b.c.dis the IP address of your new VPS (check the "Remote Access" tab in Linode).
Windows users: stagecoach can be run under the Linux subsystem for Windows.
- Deploy your site for the first time:
At the end of the run, you should see:
First startup, chose port 3000 for this site
- Your site is up, but it can't be reached at the usual HTTP port yet. Let's fix that with
ssh to your server as root. We can do this conveniently with the
sc-shell command, but you could also do it manually:
mechanic add to configure nginx to proxy traffic from port 80 to port 3000, taking care of caching and serving static files quickly along the way:
mechanic add myshortname --host=example.com --aliases=www.example.com --static=/opt/stagecoach/apps/myshortname/current/public --backends=3000 --default=true
As long as you specify
--default=true, you should be able to access your site right away at its IP address:
Change the DNS "A" records for
www.example.comto point to your IP address,
a.b.c.d. Be aware DNS changes can take time to propagate, hours or days depending on your DNS configuration.
That's it! Your site is up at your own domain name:
- In the future, to deploy updated code, just run
sc-deploy productionagain. This will not disturb your website's content; Stagecoach makes sure the
data/folders survive each new deployment.