I've made an update available. Turns out it requires the development copy of packer in order to automatically upload to vagrant-cloud.
As of now, if you are using Python 3 for TG 2.3.4 along with PostgreSQL, you can get an easy working environment with vagrant. Run these commands in the same directory as your setup.py and development.ini vagrant init pedersen/tg2pg9 vagrant up You might need to modify your development.ini to get it to connect to the local PG database (pg name/password: vagrant/vagrant). And you might need to update the host parameter to 0.0.0.0 so that your host OS can see it. I've got more thoughts on what to do with this going forward that I'll share in detail next week. The short version is that this should be more than just development environment. This should be recipes to help people create development and production environments. This should include centos/rhel, ubuntu, py2, py3, ansible, chef, puppet, virtualbox, vmware, vagrant. A whole bunch of work to do there to show how to make it all happen, and I need some time to get all the ideas put together properly. Early next week I'll type it all up. In the meantime, happy hacking. And I hope this is somewhat useful. On Wed, Mar 11, 2015 at 12:27 AM, Michael Pedersen <[email protected]> wrote: > Just as an update for everybody on this: I've just pushed a change to the > template I've built (though the base box is not yet pushed, just the config > files at https://github.com/pedersen/tgcloud ) that will now have the > base box automatically run "python setup.py develop" on your app (if it's > present under /vagrant), and will get your postgres database prepped. > > There's still more to go (mysql and mongo support need to be done, as well > as docker and aws), but this is starting to turn into something that could > be genuinely useful for people to use as a reference. > > On Sat, Mar 7, 2015 at 9:41 AM, Michael Pedersen <[email protected]> > wrote: > >> Thank you Alessandro. I've actually created an issue for it: >> https://github.com/pedersen/tgcloud/issues/1 >> >> I'm going to work on trimming down the postgresql image. There has to be >> a way to remove a bunch of the disk usage, though I'm running into a wall >> there. After I get that to the point where I'm happy with it, I'll work on >> docker support next, I think. >> >> On Fri, Mar 6, 2015 at 4:28 PM, Alessandro Molina < >> [email protected]> wrote: >> >>> On Thu, Mar 5, 2015 at 3:15 PM, Michael Pedersen <[email protected]> >>> wrote: >>> >>>> Alessandro had mentioned that somebody already did a Docker >>>> configuration, so I'm going to find that at some point to incorporate it. >>>> >>> >>> I was referring to >>> https://groups.google.com/forum/#!searchin/turbogears/docker/turbogears/58G5xKIuwXg/ud8uSWVDXh4J >>> But I haven't tried it, so not sure it can help you or not :D >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "TurboGears" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/turbogears. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Michael J. Pedersen >> My Profile: http://www.icelus.org/ >> Google+ https://google.com/+MichaelPedersen >> >> > > > -- > Michael J. Pedersen > My Profile: http://www.icelus.org/ > Google+ https://google.com/+MichaelPedersen > > -- Michael J. Pedersen My Profile: http://www.icelus.org/ Google+ https://google.com/+MichaelPedersen -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
