Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Continuous Delivery with Divshot and Codeship

DZone's Guide to

Continuous Delivery with Divshot and Codeship

· DevOps Zone
Free Resource

Best practices for getting to continuous deployment faster and with dramatic results in reduced outage minutes, development costs, and QA testing cycles. Brought to you by Rainforest QA.

Written by Manuel Weiss

I am happy to welcome a new member to our Codeship Integrations family: Divshot! Divshot offer Static Web Hosting for Developers and we’ve been partnering with them for quite a while as you can see on their perks page.

Set up Continuous Delivery with Divshot and Codeship

At Codeship we want to help you to develop your software as efficiently as possible. That’s why we’ve built an easy integration with Divshot.

To deploy from Codeship to Divshot you first need to setup your application locally. To do so please follow the Getting Started guide. Don’t forget to commit the divshot.jsonfile to your repository. Once you can deploy your site successfully from your local machine you need to setup your Divshot user token on the Codeship project. Grab the login token by running the following command and save it as an environment variable called DIVSHOT_TOKEN.

divshot auth:token

Then, on Codeship, add a new script based deployment to your project and include the following commands

npm install -g divshot-cli
divshot push development --token "${DIVSHOT_TOKEN}"

Don’t forget to specify the actual Divshot environment you want to deploy to (development in the example above).

If you want more information you can check out the Divshot documentation.

Ready to get started? Head over to Codeship and set up your Deployment to Divshot!


Discover how to optimize your DevOps workflows with our on-demand QA solution, brought to you in partnership with Rainforest QA.

Topics:

Published at DZone with permission of Moritz Plassnig, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}