gulp release

[lookfirst]

What sort of workflow are you planning for gulp release?

When I think of a release, I think of an artifact that is built that can be distributed to my servers. Something like a .tgz, .zip, .jar, .deb, .rpm. Right now, the system doesn't really do that. Can we improve on it?

I'd like to propose that we move the system.config.js and index.html into the src folder. These files are then copied into the dist folder. This allows for a gulp prod (which calls gulp release) to just point at the dist folder as the root of the application to serve things from. It also allows us to test the built application easily.

Thoughts?

[amcdnl]

Gulp release is the command the CI server calls for distro to prod. We use .net so it packages the files internally.

[lookfirst]

I've done all this in my project. Take a look if you'd like to port it back over. =)

[amcdnl]

I think a better approach would be to inject this into the app.js file . We probably also need to handle the system and config file cache busting too.

[lookfirst]

Yea, I agree. I'd like to get rid of the whole rewrite of the index.html thing. It is kind of ugly. =)