Il 14/apr/2016 03:47 AM, "Ryan Lerch" <rlerch(a)redhat.com> ha scritto:
As a designer, when I jump into doing a UI review, or hacking on the
CSS of a new project, one of the most painful steps for me is
getting my dev environment set up.
Most of our webapps do have very good documentation on getting a dev
set up, but invariably this takes a good chunk of time and
fiddling for me (being someone that is not super-familiar with setting up
and running the back-ends of webapps). This is especially relevant if what
i am trying to fix is just a simple template change, and TBH manually
tweaking postgres config files is not really my idea of a good time. :)
Long story short, i am asking for comments and thoughts on how to make
setting up a
dev environment simpler and easier (and perhaps even
standardized between all our apps).
I recently started playing with Vagrant, and made this vagrant setup
bootstrapping a bodhi dev envirionment using Vagrant on top of
vagrant-libvirt, and it works pretty well for me -- i can just use one
command to spin up a new clean instance of a bodhi dev environment, with
the DB configured and populated and ready to go. Note that i chose libvirt
with Vagrant here, primarily because i am not well versed in Docker, but
Docker on Vagrant is possible too.
 - https://gist.github.com/ryanlerch/577eb8cd9d8ff66023cb2f98dc78bfe5
infrastructure mailing list
I agree with Ryan that we could probably have an easier way to set up local
instances of our apps, this would help not only designers or websites folks
but also new contributors.
On the other hand it is rather difficult to make a unified way to launch
all apps the same way, because they are sometimes very different. Recently
we have only Flask based apps, so that could help, but the thought about
vagrant or docker solutions is really nice.
I'll try your bodhi development environment, maybe this is a good start.
Thanks for sharing.