Public | Automated Build

Last pushed: a year ago
Short Description
Github version of the indatus-website.
Full Description

indatus.com

Staging: staging.indatus.com


  1. Installation
  2. Workflow / Plugins
  3. Deploying
  4. Alerts
  5. Notes

Installation

Running for the first time:

  1. Clone repo
  2. Make sure node.js is installed
  3. Edit /etc/hosts file
  4. sh build.sh installs dependencies and runs the default grunt command

After every git pull

grunt (for production):

  • Compiles all the code

grunt dev (for development):


Workflow / Plugins

Grunt

See above

Bower

Default to npm, but Bower is installed and is an option

NPM

Install and manage Grunt packages with npm via shell (preferred) or package.json

When adding Grunt or Bower packages:

  • New SCSS files should be added to the base.scss via @import at the top of the file
  • New JS files should be added to the concat task in Gruntfile.js
  • Plugins that contain many assets may be moved to the plugins directory of the project by adding to them to copy task in Gruntfile.js

Deploying

Staging - http://staging.indatus.com

Docker Hub builds a container based on the name of the latest push to each branch.
For example, when building a new feature on branch frontpage-copy-update, Docker
Hub will build a container with the name levelonedev/indatus-website:frontpage-copy-update
once the commit is pushed.

  1. Login to Rancher. (You can get this information from another developer if needed.)
  2. Update the existing Indatus-Website service in the staging environment with the new container image name.
  3. Wait for deployment.
  4. Check and double check the new version.

Production - http://indatus.com

For the master branch, Docker Hub builds a container with the name
levelonedev/indatus-website:web. This will need to be deployed to the production
environment using the same steps as listed in the staging environment.

  1. Login to Rancher. (You can get this information from another developer if needed.)
  2. Update the existing Indatus-Website service in the production with the new container image name.
  3. Wait for deployment.
  4. Check and double check the new version.

Alerts

We are currently using Hellobar to alert users of outages, etc. Ask a teammate for creds if needed.


Notes

Site is built on Kirby v1.1.2
http://getkirby.com

Documentation
http://v1.getkirby.com/docs

Docker Pull Command
Owner
levelonedev

Comments (0)