Skip to content

Instantly share code, notes, and snippets.

@kellishouts
Last active May 12, 2016 05:52
Show Gist options
  • Save kellishouts/93ad5648aa68decf94752003d6a7fe08 to your computer and use it in GitHub Desktop.
Save kellishouts/93ad5648aa68decf94752003d6a7fe08 to your computer and use it in GitHub Desktop.
Airship Core Dev - Setting up Local Development

1. Using pgAdmin, setup an Airship site.

  • Add a new site to airship_sites
  • add the landing root page. Set application.html layout and root.html template.
  • add a superadmin user. It's easiest if you copy user1's password for your superadmin user. Also copy the created at from user1, this is needed for checking the hash
  • add struts for the appropriate application.html layout and root.html template.

2. Set up the Airship .env file and /etc/hosts file

  • make sure .env file is pointing to the right domain: DEV_CNAME=pokebowls.airshipcms.io
  • In the Airship terminal, source .env
  • while developing locally, make sure /etc/hosts is setup for pokebowls.airshipcms.io. In the hosts file: 127.0.0.1 localhost pokebowls.airshipcms.io
  • In Airship terminal, env $(cat .env | xargs) gulp

3. Build the site content

  • set up website pages and sections in pokebowls.airshipcms.io:2233/admin (or was it localhost:2233/admin??)

4. Set up the CLI Tools

5. Connect Local dev to the project api

In the PROJECT directory (not Airship directory. This is a NEW directory)...

  • do "First Time Project Setup" to create the PROJECT .env file in Running Airship Cli
  • airship login env $(cat .env | xargs) airship login
  • airship land env $(cat .env | xargs) airship land [subdomain]
  • set up a git repo
  • airship env $(cat .env | xargs) airship serve
  • work on site locally a bit. View changes at localhost:4000.
  • push changes to git
  • airship manifest env $(cat .env | xargs) airship manifest [subdomain]
  • airship launch env $(cat .env | xargs) airship launch [subdomain]
  • view site on staging pokebowls.airshipcms.io:3899
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment