-
-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install npm and Sage packages? #124
Comments
Bedrock and hence this playbook has nothing to do with Roots/Sage. I think the proper solution is for us to create another repo under the Roots org which would be a role to install what's necessary for deploying our theme. |
What if we had a create-your-own-adventure role, a role that's run specifically for whatever theme you're looking to use? We could create one for Roots/Sage as a demo. Two birds with one stone. |
I agree with @swalkinshaw. Perhaps I can create a teeny tiny buildpack for Sage themes that gives you everything you need + a standard process to follow. |
Could also be a separate Ansible Galaxy module. |
Keep in mind that the only thing required for Sage is Node and maybe globally installing some packages. Everything else will be part of the deployment process which is already in progress at #95. There's also the debate about doing the compiles locally and uploading assets which wouldn't make any of this necessary. |
Awesome. Really excited about 8.0.0!
How would you deploy if this was the methodology? Can Ansible copy it up? |
@mAAdhaTTah yeah exactly. Ansible can run tasks locally or do local actions and then copy/upload the files. |
In light of the conversation here: roots/sage#1257, does it make sense to make installing node, npm, bower, & gulp an optional install for deploying a sage theme?
The text was updated successfully, but these errors were encountered: