One of the benefits of building stateful client-side apps, is that you can make them independent from the rest of your backend, having a separate repository and deploy process. The advantages of this is that it keeps your backend and frontend decoupled, and was the principal point behind my article on using Rails as an API.
To be fair, there’s no shortage of asset compilation libraries on GitHub, and I was a bit loath to reinvent the wheel. Having said that, the key principal behind Catapult is simplicity. It’s suits my personal use-case perfectly, and customizing it is absolutely trivial.
Now let’s explore some basic usage. To generate an app, use the
Now you can start a catapult server:
$ catapult server
And open up the app in your browser. During deployment, you’ll want to serve the files statically. You can write compiled files to disk using the
$ catapult build
You can even watch the files for changes, and then automatically build:
$ catapult watch
As I say, the source is incredibly simple. In the spirit of @fat’s talk on documentation, I invite you to dive in.