1001495 - Serve the static files

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Description

[Andy McKay]

On the production, dev and stage servers serve out the spartacus files. This will mean figuring out how to grab spartacus and ensure the files are in the correct place for serving.

Comment 1

[[e-mail]]

npm / bower installing out of git would probably be a nice way to do this for getting hold of the files. Would mean npm / bower versioning would control the version of spartacus being run.

Comment 2

[[e-mail]]

Looking at this I think it would be better for consistency if the way Spartacus public files are deployed is the same as how we do fireplace and everything else e.g with a fabfile. That way this can be tagged like we do everything else otherwise we're going to need to constantly bump a version file and that will be less automatic e.g. seeing changes to Spartacus automatically pushed out on -dev 

At the moment the commands that would need to be carried out are:

npm install # install grunt + deps for the build processes
grunt stylus # Build the CSS
grunt nunjucks # build the templates

Once the build processes are run only the public folder needs to be published to the CDN. https://github.com/mozilla/spartacus/tree/master/public

Minification needs to be done but that can come later and be a simple amendment to the fabfile.

For now we'll only need this on -dev and -stage and prod can come later.

Comment 3

[[e-mail]]

Add an ops bug to cover setting up the fabfile in bug 1011561

Comment 4

[[e-mail]]

https://github.com/mozilla/webpay/commit/976154513ed4d0d62d16b5b1da48674179bfb40f