For b, we are using a similar approach. Everything works fine but live-reload given that the plugin wants to trigger a URL open when there is no GUI :). Grant Rettke | ACM, ASA, FSF, IEEE, SIAM [email protected] | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson
On Fri, Aug 8, 2014 at 2:19 AM, Rhys Gareth <[email protected]> wrote: > What's the best container setup if I want: > (a) production containers to match development containers, and: > (b) I want to support a full grunt-based workflow automation setup for > development? > > If I build a node.js/Apache container which then also includes all the grunt > watch/rebuild/livereload/etc then it seems I am not satisfying point (a) > above. So then in a vagrant/docker world, would we have an "app" container > which is the same for production,staging, test and dev - just containing > node.js and Apache - and then a second container for dev-only which contains > all the workflow tools/dev dependencies and shares the files with the app > container? > > Rhys > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
