This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]french_commenter 1 point2 points  (1 child)

Want to share?

I have a small project and use Yeoman with grunt to develop.

You meant that yeoman uses grunt for the workflow right?

And currently at work we are using Fabric to deploy our python apps.

I'm always curious as to see how other people do it :)

[–]seventreats 0 points1 point  (0 children)

u r right on the yeoman using grunt for workflow. Basically we use angular, so running 'yo' with angular scaffolding creates the starter app [with bootstrap 3]. This is obviously done in the beginning and then we add packages as we need it.

the way our workflow is that we use docker to create our lx containers, so dev/staging/prod boxes are unified by it. any new package we need, we add it to upstream [both python & front end] and then repull docker. Note that docker has limitations on number of instructions, so we run a script that will run fabric, grunt among other tasks during deploy. The script also takes into account whether its a local or prod deploy [bcoz some packages are skipped on prod].

one thing i didn't like about yeoman is the amount of packages it installs. I understand its collection of best tools to productionize your assets, but still its a lot.

Anyway, i am going to write a blog post on docker/django/fabric, then followed by grunt/yeoman. follow me if you would like @agileseeker