Hi James, I will modify my tutorial to bring it in line with more modern Vagrant practices. Thank you and keep the criticisms coming.
The fabfile is specific to Ubuntu 12. I use Official Ubuntu 12.04 daily Cloud Image amd64 from http://www.vagrantbox.es/ in my write-up and everywhere else unless there is a *very* compelling reason to use something else. The Ninety Percent Rule – which may or may not be real – says to examine, understand, and adopt the best practices nine of ten developers in your community use. If nine people in your shop use Eclipse and one uses Emacs, new developers should start with Eclipse. It should not be confused with the Ninety-Ninety Rule, which also applies to our case: the second "Ninety" would be deployment. Deployment is hard. Scalable repeatable deployment is harder still. Some would respond to this by saying they got Mezzanine working under Ubuntu 14 or running under uWSGI or behind Apache. That is great and pride in that accomplishment is valid. They value challenge and will push the field forward. Individuals are strongly encouraged to package their deployment into a Fabric script for inclusion in Mezzanine. I would be delighted to provide assistance in the task. hth, ken On Mon, Dec 22, 2014 at 5:23 PM, J. Paskaruk <[email protected]> wrote: > > Kenneth, I'm following your tutorial, and I'm at the vagrant thing. I'm > fairly clear on what it is and what it does. I'm running 14 rather than 12 > cause I had the image on hand on a virtualbox. I just used apt-get to > install vagrant, rather than the Ruby gem (which it specifically poopooed > when I tried it). I looked at the website, though, and it doesn't mention > installing from distro, just offers a download. If I use the distro's > version, should that work alright, or is Vagrant something you want to be > at the bleeding edge for? > > > On Monday, December 22, 2014 10:12:17 AM UTC-6, Kenneth Bolton wrote: >> >> Docs are working for me from here in downstate New York (not to be >> confused with New York City or its environs). >> >> Have you tried the Fabric script that ships with Mezzanine? That is the >> canonical way to deploy, as described in the documentation at >> http://mezzanine.jupo.org/docs/deployment.html (assuming connectivity >> comes back for you.) >> >> I practice a strict deploy-first methodology by deploying to a virtual >> machine before any other development happens. That means I have my >> deployment sorted and no longer occupying mindshare. Back when I first >> played with Python web frameworks (anybody remember ZopeCMF?) deploying was >> so brutally painful that projects could progress with velocity, then die on >> the vine for lack of deployment process. >> >> You can try my now-long-in-the-tooth description of how I deal with this >> problem. It is specific to Ubuntu 12.04 and Mezzanine, but I have done the >> same with vanilla Django projects. http://bscientific. >> org/blog/mezzanine-fabric-git-vagrant-joy/. >> >> Let us know how it goes. >> >> best, >> ken >> >> On Mon, Dec 22, 2014 at 10:53 AM, James Michael Yeo Paskaruk < >> [email protected]> wrote: >> >>> I have a site put together on the dev server, I'm happy with it as a >>> preliminary design/skeleton. >>> >>> I'm attempting to deploy the page on digitalocean.com. >>> >>> They have a one-click Django server, but I do not know how to take that >>> and transplant Mezzanine into it. Is there a step-by-step set of >>> instructions to do this? >>> >>> In the absence of that, I've been attempting to just setup an Ubuntu >>> droplet. I've gotten as far as being able to run gunicorn_django -b >>> 0.0.0.0:8000, and it serves pages at that address, but there's a big >>> warning that the command is deprecated, and there's still the matter of >>> nginx and the static files. >>> >>> I've read everything that comes up in google searches for stuff like >>> "deploy a mezzanine site on ubuntu" and "deploy mezzanine on one-click >>> django server" and a million other permutations, and I get the same two or >>> three DO links that do not contain a complete set of instructions. >>> >>> To compound this, I'm not sure if this is true for everyone else, but >>> the docs for Django and Mezzanine appear to be offline as I type this. the >>> cached google version is still there, of course, but it means searching for >>> each page, rather than clicking on links. Makes the process the opposite of >>> pleasurable. >>> >>> The most frustrating aspect, of course, is that this is something really >>> simple I'm trying to do. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Mezzanine Users" 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 > "Mezzanine Users" 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 "Mezzanine Users" 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.
