Member-only story
Tutorial: setting up Continuous integration with Includable
It is now super easy to set up continuous integration for projects running on the Includable platform. In this tutorial we’ll show you how to use Travis CI to build static assets and deploy the result to Includable.
The basics
First make sure you have the latest version of the Includable CLI installed: npm i -g includable
Then, you can start creating your first Includable module: inc create
. Let’s go for the svelte
starter pack. Svelte is a super cool front-end framework that is compiled beforehand, resulting in a super tiny javascript file for deployment. By default, this starter kit will require the developer to compile their assets themselves (happens automatically when running inc run
) and checks those into their Git repo.
A cleaner solution would be to automatically create those when a new change is committed, and automatically deploying those assets to the Includable Platform. In order to do that, we’ll use Travis CI, one of the many available continuous integration solutions (some others to check out are Circle CI and Codeship).
Updating Gitignore
First off, we want to make sure that compiled static assets are never checked into version control, since they will be created before deployment by our Travis CI script.
In order to do so, we add the following line to .gitignore
: