In the first post in this series discussed the some of the reasons for building a prototype, and introduced the MEAN stack. Then in the second post I covered what I found when I tried to follow this guide to build a MEAN prototype that is integrated with the StormPath user management service I have decided to use. The guide uses yeoman and in particular the angular-fullstack-generator, to quickly create a working app by generating a lot of boilerplate code.
In the first post in this series discussed the some of the reasons for building a prototype, and introduced the MEAN stack. Next I am going to talk about what I found when I tried to follow this guide to build a MEAN prototype that is integrated with the StormPath user management service I have decided to use. The guide uses yeoman and in particular the angular-fullstack-generator, to quickly create a working app by generating a lot of boilerplate code.
Once I had finished figuring out how I would provision environments using Ansible and build and test software using Snap-CI as I have over my last few posts, I thought the next step I would take would be to do a small part of the work that needs to be done for the ALSL project - that is design an API. This seemed like a reasonable first step since the API defines the interface between our users and the system. I was all ready to get into talking about Domain Driven Design, and I had started looking at ways to define the API in a technology agnostic language such as RAML when I started talking to a friend about a project he wanted to do.
This post has been a while coming because I jumped down a couple of rabbit-holes while working on it. I have concluded that client side stuff is not as bad as it was during the worst days of the browser wars, and I still like angularjs but creating polished rich web applications is still much more difficult than implementing server side business rules. I will have some future posts about what I found down those...
I thought this would be the final post in the series, where I finally got around to adding at least another form to the application. As I was thinking about what need to be done I discovered that there was too much little stuff to be resolved, including the technical debt incurred by using a yeoman generator. I managed to clean up a lot of things working on this post which should make delivering new...
Once the tests were working I decided to build a continuous deployment pipeline in Snap-CI which you can view here (Edit: This build was moved to Travis-CI when Snap-CI shutdown. Now this is where you can view it. The first stages run the npm install and bower install commands to get dependencies and then various grunt tasks to run tests and build (minify, etc) the project.The last step runs grunt buildcontrol which uses configuration from...