Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

I'm definitely having connectivity problems here in Winnipeg. I wonder if 
it's fallout from the DDOS nuking that Anonymous is currently delivering to 
North Korea? I seem to have no problems reaching Google (which, as an Free 
Software ideologue who considers Stallman a personal hero, makes me uneasy 
in and of itself), though, so I can get at the cached versions of 
everything so far. 

Anyways, I didn't know about Fabric until just this second. I'll go read up 
on it. My usual method with this stuff is to bully my way through a 
tutorial and learn by osmosis. However, I'm not at all afraid of reading a 
friendly manual, and that's my usual approach when I hit a wall, to just 
find a manual or video or tutorial that is in some way related and just 
learn everything I can about that other thing, and generally when I come 
back, as long as I exercise patience, I find my way. Lazy, Hermann 
Hesse-type Buddhism helps a fair bit. :>

Anyways, as I said, I shall investigate this thing you call Fabric, and 
report back. I also just read about your deployed virtual server approach 
the other day, and I intend to adopt that... now. Thanks for the response, 
I feel less alone at least. 

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 <
> jpas...@gmail.com > 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

I'm a bit irritated at Google right now, that a page with the title of your 
page didn't show up in my google searches about this, while a whole bunch 
of crap, useless links did. I smell SEO and digital graft all over this.

On Monday, December 22, 2014 12:49:56 PM UTC-6, Josh Cartmell wrote:
>
> Hey James, everything Ken says is correct, Fabric and his other 
> suggestions will make your life much easier.
>
> As far as Digital Ocean goes, I wrote a tutorial about deploying Mezzanine 
> to Digital Ocean using Fabric, you can view it at 
> http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/
> If you know a bit about server admin and have Fabric figured out there is 
> nothing in there that is mind blowing or particularly difficult to figure 
> out, but I look back at it occasionally to refresh myself.
>
> On Mon, Dec 22, 2014 at 12:58 PM, Ken Bolton  > wrote:
>
>> You are in good company here among the automating Lazy. Let us know how 
>> it goes, and suggestions for improvements are welcome, as are pull requests.
>>
>> On Mon, Dec 22, 2014 at 12:27 PM, J. Paskaruk > > wrote:
>>
>>> I'm definitely having connectivity problems here in Winnipeg. I wonder 
>>> if it's fallout from the DDOS nuking that Anonymous is currently delivering 
>>> to North Korea? I seem to have no problems reaching Google (which, as an 
>>> Free Software ideologue who considers Stallman a personal hero, makes me 
>>> uneasy in and of itself), though, so I can get at the cached versions of 
>>> everything so far. 
>>>
>>> Anyways, I didn't know about Fabric until just this second. I'll go read 
>>> up on it. My usual method with this stuff is to bully my way through a 
>>> tutorial and learn by osmosis. However, I'm not at all afraid of reading a 
>>> friendly manual, and that's my usual approach when I hit a wall, to just 
>>> find a manual or video or tutorial that is in some way related and just 
>>> learn everything I can about that other thing, and generally when I come 
>>> back, as long as I exercise patience, I find my way. Lazy, Hermann 
>>> Hesse-type Buddhism helps a fair bit. :>
>>>
>>> Anyways, as I said, I shall investigate this thing you call Fabric, and 
>>> report back. I also just read about your deployed virtual server approach 
>>> the other day, and I intend to adopt that... now. Thanks for the response, 
>>> I feel less alone at least. 
>>>
>>> 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 <
>>>> jpas...@gmail.com> 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?
>>>&g

Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

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 <
> jpas...@gmail.com > 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

I'm just going through a Vagrant tutorial and HOLY CRAP VAGRANT IS AWESOME

On Tuesday, December 23, 2014 9:43:47 AM UTC-6, Kenneth Bolton wrote:
>
> 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  > 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 <
>>> jpas...@gmail.com> 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 
>>>&g

Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

Also, when I was talking about using that image I was doing it way wrong - 
I was executing your tutorial's commands inside an Ubu1404 machine running 
in Virtualbox in my host. I'm a fair bit more clear now than I was when I 
posted that question.

On Tuesday, December 23, 2014 9:43:47 AM UTC-6, Kenneth Bolton wrote:
>
> 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  > 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 <
>>> jpas...@gmail.com> 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 e

Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

Another thing you could update: The FABRIC section of settings.py has moved 
a few lines, so your specific line instructions don't make sense. Also, 
this must be an updated version of Mezzanine because the fields in there 
are somewhat different. there is no SSH_PASS anymore, for instance, and 
there's a NEVERCACHE key as well as SECRET. You have not mentioned these in 
this tutorial, and I'm still a relative newb here - should I go generate a 
secret and nevercache key here and fill them in? Set them in the ENV? Not 
sure what to do with that section.


On Tuesday, December 23, 2014 9:43:47 AM UTC-6, Kenneth Bolton wrote:
>
> 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  > 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 <
>>> jpas...@gmail.com> 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 be

Re: [mezzanine-users] Having trouble deploying.

[J. Paskaruk]

Yes, the fab all command is returning that SECRET_KEY is not defined, and I 
can see that while it is defined in local_settings, it is not in 
settings.py. I guess I'll try generating a couple and see what happens :>

On Wednesday, December 24, 2014 6:21:54 AM UTC-6, J. Paskaruk wrote:
>
> Another thing you could update: The FABRIC section of settings.py has 
> moved a few lines, so your specific line instructions don't make sense. 
> Also, this must be an updated version of Mezzanine because the fields in 
> there are somewhat different. there is no SSH_PASS anymore, for instance, 
> and there's a NEVERCACHE key as well as SECRET. You have not mentioned 
> these in this tutorial, and I'm still a relative newb here - should I go 
> generate a secret and nevercache key here and fill them in? Set them in the 
> ENV? Not sure what to do with that section.
>
>
> On Tuesday, December 23, 2014 9:43:47 AM UTC-6, Kenneth Bolton wrote:
>>
>> 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  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 Pask

[mezzanine-users] Re: Having trouble deploying.

[J. Paskaruk]

Getting a long string of "this is not defined, that is not defined," all 
relating to settings.py. Your tutorial only says something along the lines 
of "product settings need to be put in here" or something, but there is no 
instruction whatsoever about how you do that. I did a tutorial on vagrant 
yesterday, and I can see that there is a specific digitalocean box, so I 
think I'm gonna be ok figuring it out eventually, but your tutorial doesn't 
take the user anywhere near having a deployed site, just a different, and 
yes, better, dev environment.

On Monday, December 22, 2014 9:53:09 AM UTC-6, J. Paskaruk 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Having trouble deploying.

[J. Paskaruk]

Just babbling away, I'm now trying out this one:

http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/

Step 7 is a very murky "Fill in the fabric settings". Where are the fabric 
settings to be found, exactly?

On Monday, December 22, 2014 9:53:09 AM UTC-6, J. Paskaruk 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Having trouble deploying.

[J. Paskaruk]

I mean, does "fabric settings" refer to the configuration of fabric itself, 
or does it refer to the settings which you wish to have fabric set for you?

On Monday, December 22, 2014 9:53:09 AM UTC-6, J. Paskaruk 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

I've spent the last week attempting a manual deployment on an Ubuntu 
server, and at this point, I'm seriously considering going back to 
Wordpress. 

Is it feasible to create a One-click Django server, ssh into the server, 
install Mezzanine in the backend, and then add the various Mezzanine apps 
to the already-working settings.py, and then modify the site from there?

I've had my site finished and ready to go in the dev server for a week now. 
Deployment should be easier than this.

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Cheers, I'll give that a go. I wish I could figure out that Fabric thing, 
but Digitalocean's tutorial on Vagrant is from 2013, and refers to urls on 
their own site that don't exist anymore. I cannot find a from 
nothing-to-deployed tutorial that doesn't hit serious snags, with errors 
that don't have solutions in google. Perhaps you and I could go through 
your tutorial, step-by-step, and come up with an updated version that's 
more clear?

On Wednesday, December 24, 2014 7:20:58 AM UTC-6, Kenneth Bolton wrote:
>
> Hi James,
>
> You can usually get away with copying the entire directory structure at 
> https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/project_template
>  
> into the root of your project, taking care in particular to merge the 
> settings.py and urls.py files with the Mezzanine versions as taking 
> precedence.
>
> hth,
> ken
>
> On Wed, Dec 24, 2014 at 8:14 AM, J. Paskaruk  > wrote:
>
>> I've spent the last week attempting a manual deployment on an Ubuntu 
>> server, and at this point, I'm seriously considering going back to 
>> Wordpress. 
>>
>> Is it feasible to create a One-click Django server, ssh into the server, 
>> install Mezzanine in the backend, and then add the various Mezzanine apps 
>> to the already-working settings.py, and then modify the site from there?
>>
>> I've had my site finished and ready to go in the dev server for a week 
>> now. Deployment should be easier than this.
>>
>> -- 
>> 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

(Just suggesting because you're linked from Mezzanine's main page, which 
makes you closest thing to someone responsible for documenting this process 
as exists in the universe...)

On Wednesday, December 24, 2014 8:35:43 AM UTC-6, J. Paskaruk wrote:
>
> Cheers, I'll give that a go. I wish I could figure out that Fabric thing, 
> but Digitalocean's tutorial on Vagrant is from 2013, and refers to urls on 
> their own site that don't exist anymore. I cannot find a from 
> nothing-to-deployed tutorial that doesn't hit serious snags, with errors 
> that don't have solutions in google. Perhaps you and I could go through 
> your tutorial, step-by-step, and come up with an updated version that's 
> more clear?
>
> On Wednesday, December 24, 2014 7:20:58 AM UTC-6, Kenneth Bolton wrote:
>>
>> Hi James,
>>
>> You can usually get away with copying the entire directory structure at 
>> https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/project_template
>>  
>> into the root of your project, taking care in particular to merge the 
>> settings.py and urls.py files with the Mezzanine versions as taking 
>> precedence.
>>
>> hth,
>> ken
>>
>> On Wed, Dec 24, 2014 at 8:14 AM, J. Paskaruk  wrote:
>>
>>> I've spent the last week attempting a manual deployment on an Ubuntu 
>>> server, and at this point, I'm seriously considering going back to 
>>> Wordpress. 
>>>
>>> Is it feasible to create a One-click Django server, ssh into the server, 
>>> install Mezzanine in the backend, and then add the various Mezzanine apps 
>>> to the already-working settings.py, and then modify the site from there?
>>>
>>> I've had my site finished and ready to go in the dev server for a week 
>>> now. Deployment should be easier than this.
>>>
>>> -- 
>>> 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 mezzanine-use...@googlegroups.com.
>>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Cool, I'll just start from the top then.

On Wednesday, December 24, 2014 8:39:55 AM UTC-6, Kenneth Bolton wrote:
>
> James,
>
> Happy to help. Let me know where you hit snags or require clarification. 
> For me at this point, it is simply muscle-memory and the shifts in the 
> technology since writing are second nature.
>
> ken
>
> On Wed, Dec 24, 2014 at 9:36 AM, J. Paskaruk  > wrote:
>
>> (Just suggesting because you're linked from Mezzanine's main page, which 
>> makes you closest thing to someone responsible for documenting this process 
>> as exists in the universe...)
>>
>>
>> On Wednesday, December 24, 2014 8:35:43 AM UTC-6, J. Paskaruk wrote:
>>>
>>> Cheers, I'll give that a go. I wish I could figure out that Fabric 
>>> thing, but Digitalocean's tutorial on Vagrant is from 2013, and refers to 
>>> urls on their own site that don't exist anymore. I cannot find a from 
>>> nothing-to-deployed tutorial that doesn't hit serious snags, with errors 
>>> that don't have solutions in google. Perhaps you and I could go through 
>>> your tutorial, step-by-step, and come up with an updated version that's 
>>> more clear?
>>>
>>> On Wednesday, December 24, 2014 7:20:58 AM UTC-6, Kenneth Bolton wrote:
>>>>
>>>> Hi James,
>>>>
>>>> You can usually get away with copying the entire directory structure at 
>>>> https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/project_
>>>> template into the root of your project, taking care in particular to 
>>>> merge the settings.py and urls.py files with the Mezzanine versions as 
>>>> taking precedence.
>>>>
>>>> hth,
>>>> ken
>>>>
>>>> On Wed, Dec 24, 2014 at 8:14 AM, J. Paskaruk  wrote:
>>>>
>>>>> I've spent the last week attempting a manual deployment on an Ubuntu 
>>>>> server, and at this point, I'm seriously considering going back to 
>>>>> Wordpress. 
>>>>>
>>>>> Is it feasible to create a One-click Django server, ssh into the 
>>>>> server, install Mezzanine in the backend, and then add the various 
>>>>> Mezzanine apps to the already-working settings.py, and then modify the 
>>>>> site 
>>>>> from there?
>>>>>
>>>>> I've had my site finished and ready to go in the dev server for a week 
>>>>> now. Deployment should be easier than this.
>>>>>
>>>>> -- 
>>>>> 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 mezzanine-use...@googlegroups.com.
>>>>> 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

I can tell you now, though, that I can get all the way to Intermission with 
no problems. It's right there that it all goes south. :>

On Wednesday, December 24, 2014 8:52:04 AM UTC-6, J. Paskaruk wrote:
>
> Cool, I'll just start from the top then.
>
> On Wednesday, December 24, 2014 8:39:55 AM UTC-6, Kenneth Bolton wrote:
>>
>> James,
>>
>> Happy to help. Let me know where you hit snags or require clarification. 
>> For me at this point, it is simply muscle-memory and the shifts in the 
>> technology since writing are second nature.
>>
>> ken
>>
>> On Wed, Dec 24, 2014 at 9:36 AM, J. Paskaruk  wrote:
>>
>>> (Just suggesting because you're linked from Mezzanine's main page, which 
>>> makes you closest thing to someone responsible for documenting this process 
>>> as exists in the universe...)
>>>
>>>
>>> On Wednesday, December 24, 2014 8:35:43 AM UTC-6, J. Paskaruk wrote:
>>>>
>>>> Cheers, I'll give that a go. I wish I could figure out that Fabric 
>>>> thing, but Digitalocean's tutorial on Vagrant is from 2013, and refers to 
>>>> urls on their own site that don't exist anymore. I cannot find a from 
>>>> nothing-to-deployed tutorial that doesn't hit serious snags, with errors 
>>>> that don't have solutions in google. Perhaps you and I could go through 
>>>> your tutorial, step-by-step, and come up with an updated version that's 
>>>> more clear?
>>>>
>>>> On Wednesday, December 24, 2014 7:20:58 AM UTC-6, Kenneth Bolton wrote:
>>>>>
>>>>> Hi James,
>>>>>
>>>>> You can usually get away with copying the entire directory structure 
>>>>> at https://github.com/stephenmcd/mezzanine/tree/
>>>>> master/mezzanine/project_template into the root of your project, 
>>>>> taking care in particular to merge the settings.py and urls.py files with 
>>>>> the Mezzanine versions as taking precedence.
>>>>>
>>>>> hth,
>>>>> ken
>>>>>
>>>>> On Wed, Dec 24, 2014 at 8:14 AM, J. Paskaruk  
>>>>> wrote:
>>>>>
>>>>>> I've spent the last week attempting a manual deployment on an Ubuntu 
>>>>>> server, and at this point, I'm seriously considering going back to 
>>>>>> Wordpress. 
>>>>>>
>>>>>> Is it feasible to create a One-click Django server, ssh into the 
>>>>>> server, install Mezzanine in the backend, and then add the various 
>>>>>> Mezzanine apps to the already-working settings.py, and then modify the 
>>>>>> site 
>>>>>> from there?
>>>>>>
>>>>>> I've had my site finished and ready to go in the dev server for a 
>>>>>> week now. Deployment should be easier than this.
>>>>>>
>>>>>> -- 
>>>>>> 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 mezzanine-use...@googlegroups.com.
>>>>>> 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 mezzanine-use...@googlegroups.com.
>>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Minor: when I vagrant up, it gives me a warning that Guest Additions are 
version 4.2, whereas my virtualbox has 4.3.

On Wednesday, December 24, 2014 8:53:20 AM UTC-6, J. Paskaruk wrote:
>
> I can tell you now, though, that I can get all the way to Intermission 
> with no problems. It's right there that it all goes south. :>
>
> On Wednesday, December 24, 2014 8:52:04 AM UTC-6, J. Paskaruk wrote:
>>
>> Cool, I'll just start from the top then.
>>
>> On Wednesday, December 24, 2014 8:39:55 AM UTC-6, Kenneth Bolton wrote:
>>>
>>> James,
>>>
>>> Happy to help. Let me know where you hit snags or require clarification. 
>>> For me at this point, it is simply muscle-memory and the shifts in the 
>>> technology since writing are second nature.
>>>
>>> ken
>>>
>>> On Wed, Dec 24, 2014 at 9:36 AM, J. Paskaruk  wrote:
>>>
>>>> (Just suggesting because you're linked from Mezzanine's main page, 
>>>> which makes you closest thing to someone responsible for documenting this 
>>>> process as exists in the universe...)
>>>>
>>>>
>>>> On Wednesday, December 24, 2014 8:35:43 AM UTC-6, J. Paskaruk wrote:
>>>>>
>>>>> Cheers, I'll give that a go. I wish I could figure out that Fabric 
>>>>> thing, but Digitalocean's tutorial on Vagrant is from 2013, and refers to 
>>>>> urls on their own site that don't exist anymore. I cannot find a from 
>>>>> nothing-to-deployed tutorial that doesn't hit serious snags, with errors 
>>>>> that don't have solutions in google. Perhaps you and I could go through 
>>>>> your tutorial, step-by-step, and come up with an updated version that's 
>>>>> more clear?
>>>>>
>>>>> On Wednesday, December 24, 2014 7:20:58 AM UTC-6, Kenneth Bolton wrote:
>>>>>>
>>>>>> Hi James,
>>>>>>
>>>>>> You can usually get away with copying the entire directory structure 
>>>>>> at https://github.com/stephenmcd/mezzanine/tree/
>>>>>> master/mezzanine/project_template into the root of your project, 
>>>>>> taking care in particular to merge the settings.py and urls.py files 
>>>>>> with 
>>>>>> the Mezzanine versions as taking precedence.
>>>>>>
>>>>>> hth,
>>>>>> ken
>>>>>>
>>>>>> On Wed, Dec 24, 2014 at 8:14 AM, J. Paskaruk  
>>>>>> wrote:
>>>>>>
>>>>>>> I've spent the last week attempting a manual deployment on an Ubuntu 
>>>>>>> server, and at this point, I'm seriously considering going back to 
>>>>>>> Wordpress. 
>>>>>>>
>>>>>>> Is it feasible to create a One-click Django server, ssh into the 
>>>>>>> server, install Mezzanine in the backend, and then add the various 
>>>>>>> Mezzanine apps to the already-working settings.py, and then modify the 
>>>>>>> site 
>>>>>>> from there?
>>>>>>>
>>>>>>> I've had my site finished and ready to go in the dev server for a 
>>>>>>> week now. Deployment should be easier than this.
>>>>>>>
>>>>>>> -- 
>>>>>>> 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 mezzanine-use...@googlegroups.com.
>>>>>>> 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 mezzanine-use...@googlegroups.com.
>>>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

changes I'm making to settings.py:

TIME_ZONE = 'America/Winnipeg'
"ENGINE": "django.db.backends.sqlite3",  (this should be a better db, but 
one thing at a time...)

Uncommenting lines 319-333, which consist of the following (different from 
your tutorial):

319 FABRIC = {
320 "SSH_USER": "", # SSH username for host deploying to
321 "HOSTS": ALLOWED_HOSTS[:1], # List of hosts to deploy to (eg, first 
host)
322 "DOMAINS": ALLOWED_HOSTS, # Domains for public site
323 "REPO_URL": "ssh://h...@bitbucket.org/user/project", # Project's repo 
URL
324 "VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs
325 "PROJECT_NAME": "", # Unique identifier for project
326 "REQUIREMENTS_PATH": "requirements.txt", # Project's pip 
requirements
327 "GUNICORN_PORT": 8000, # Port gunicorn will listen on
328 "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
329 "DB_PASS": "", # Live database password
330 "ADMIN_PASS": "", # Live admin user password
331 "SECRET_KEY": SECRET_KEY,
332 "NEVERCACHE_KEY": NEVERCACHE_KEY,
333 }

I am not modifying these yet, but when I do fab all later, it will say that 
the keys have not been defined.

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Here are my changes so far to local_settings.py. The keys are defined right 
above this in this file, but the other file still needs the keys.

FABRIC = {
 26 "SSH_USER": "vagrant", # SSH username for host deploying to
 27 "HOSTS": ALLOWED_HOSTS[:1], # List of hosts to deploy to (eg, first 
host)
 28 "DOMAINS": ALLOWED_HOSTS, # Domains for public site
 29 "REPO_URL": "https://github.com/jimmyyeo/tenprint";, # Project's 
repo URL
 30 "VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs
 31 "PROJECT_NAME": "", # Unique identifier for project
 32 "REQUIREMENTS_PATH": "requirements.txt", # Project's pip 
requirements
 33 "GUNICORN_PORT": 8000, # Port gunicorn will listen on
 34 "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
 35 "DB_PASS": "", # Live database password
 36 "ADMIN_PASS": "", # Live admin user password
 37 "SECRET_KEY": SECRET_KEY,
 38 "NEVERCACHE_KEY": NEVERCACHE_KEY,
 39 }

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Ok, first official snag. The response to fab all is:

Traceback (most recent call last):
  File 
"/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
line 658, in main
docstring, callables, default = load_fabfile(fabfile)
  File 
"/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
line 165, in load_fabfile
imported = importer(os.path.splitext(fabfile)[0])
  File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
conf = __import__("settings", globals(), locals(), [], 0).FABRIC
  File "/home/jimmy/envs/TPH/tenprint/settings.py", line 331, in 
"SECRET_KEY": SECRET_KEY,
NameError: name 'SECRET_KEY' is not defined

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

(I actually asked about this in the other thread as well)

On Wednesday, December 24, 2014 9:10:02 AM UTC-6, J. Paskaruk wrote:
>
>
> Ok, first official snag. The response to fab all is:
>
> Traceback (most recent call last):
>   File 
> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
> line 658, in main
> docstring, callables, default = load_fabfile(fabfile)
>   File 
> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
> line 165, in load_fabfile
> imported = importer(os.path.splitext(fabfile)[0])
>   File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
> conf = __import__("settings", globals(), locals(), [], 0).FABRIC
>   File "/home/jimmy/envs/TPH/tenprint/settings.py", line 331, in 
> "SECRET_KEY": SECRET_KEY,
> NameError: name 'SECRET_KEY' is not defined
>
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

local_settings.py already existed, so I just copied it into the existing 
file. Copacetic?

Also, did you want me to add the SSH_PASS line to it? There is no such line 
in the existing settings files, and I can 'vagrant ssh' into the host just 
fine without that line in the config file.


On Wednesday, December 24, 2014 9:15:12 AM UTC-6, Kenneth Bolton wrote:
>
>
> On Wed, Dec 24, 2014 at 9:53 AM, J. Paskaruk  > wrote:
>
>> I can tell you now, though, that I can get all the way to Intermission 
>> with no problems. It's right there that it all goes south. :>
>>
>>
> Careful! "South" has meaning in this context.
>
> The next step is to copy the FABRIC dictionary from your settings.py into 
> a new file local_settings.py. I just modified the language in the "Code Up" 
> section.
>
> On Wed, Dec 24, 2014 at 9:58 AM, J. Paskaruk  > wrote:
>
>> Minor: when I vagrant up, it gives me a warning that Guest Additions are 
>> version 4.2, whereas my virtualbox has 4.3.
>>
>
> I use vagrant-vbguest <https://github.com/dotless-de/vagrant-vbguest> to 
> keep my VirtualBox Guest Additions current.
>
> hth.
>
> -ken
>
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Ok, and I should add lines defining these to settings.py? Note that 
local_settings.py already has them defined.

On Wednesday, December 24, 2014 9:28:04 AM UTC-6, Kenneth Bolton wrote:
>
> You need a SECRET_KEY and NEVERCACHE_KEY defined in your settings. There 
> are SECRET_KEY generators out there. Search the Django docs to come to 
> grips with these two settings.
>
> On Wed, Dec 24, 2014 at 10:16 AM, J. Paskaruk  > wrote:
>
>> (I actually asked about this in the other thread as well)
>>
>>
>> On Wednesday, December 24, 2014 9:10:02 AM UTC-6, J. Paskaruk wrote:
>>>
>>>
>>> Ok, first official snag. The response to fab all is:
>>>
>>> Traceback (most recent call last):
>>>   File 
>>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>>> line 658, in main
>>> docstring, callables, default = load_fabfile(fabfile)
>>>   File 
>>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>>> line 165, in load_fabfile
>>> imported = importer(os.path.splitext(fabfile)[0])
>>>   File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
>>> conf = __import__("settings", globals(), locals(), [], 0).FABRIC
>>>   File "/home/jimmy/envs/TPH/tenprint/settings.py", line 331, in 
>>> 
>>> "SECRET_KEY": SECRET_KEY,
>>> NameError: name 'SECRET_KEY' is not defined
>>>
>>>  -- 
>> 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Keys defined in settings.py. new error:

Traceback (most recent call last):
  File 
"/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
line 658, in main
docstring, callables, default = load_fabfile(fabfile)
  File 
"/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
line 165, in load_fabfile
imported = importer(os.path.splitext(fabfile)[0])
  File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
conf = __import__("settings", globals(), locals(), [], 0).FABRIC
  File "/home/jimmy/envs/TPH/tenprint/settings.py", line 347, in 
from local_settings import *
  File "/home/jimmy/envs/TPH/tenprint/local_settings.py", line 27, in 

"HOSTS": ALLOWED_HOSTS[:1], # List of hosts to deploy to (eg, first 
host)
NameError: name 'ALLOWED_HOSTS' is not defined

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Just realized I needed to define it in local_settings.py. I added

ALLOWED_HOSTS = []

?

/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:52:
 
UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
1.5 requires. Will fall back to the domains configured as sites.
  warn("You haven't defined the ALLOWED_HOSTS settings, which "
Traceback (most recent call last):
  File 
"/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
line 658, in main
docstring, callables, default = load_fabfile(fabfile)
  File 
"/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
line 165, in load_fabfile
imported = importer(os.path.splitext(fabfile)[0])
  File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 28, in 
conf["HOSTS"][0]
IndexError: list index out of range

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

I added my actual hostname to the ALLOWED_HOSTS, now it's trying to fab 
all, but asking for a login password for 'vagrant' - I added the SSH_PASS 
to the FABRIC dictionary, but it's still asking for the pass.

On Wednesday, December 24, 2014 9:36:44 AM UTC-6, J. Paskaruk wrote:
>
> Just realized I needed to define it in local_settings.py. I added
>
> ALLOWED_HOSTS = []
>
> ?
>
> /home/jimmy/envs/TPH/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:52:
>  
> UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
> 1.5 requires. Will fall back to the domains configured as sites.
>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
> Traceback (most recent call last):
>   File 
> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
> line 658, in main
> docstring, callables, default = load_fabfile(fabfile)
>   File 
> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
> line 165, in load_fabfile
> imported = importer(os.path.splitext(fabfile)[0])
>   File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 28, in 
> conf["HOSTS"][0]
> IndexError: list index out of range
>
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

I don't understand what you mean by my first path. Do you mean the first 
thing I do, or the variable should consist of my first path? Which path is 
my fist path?

On Wednesday, December 24, 2014 9:37:21 AM UTC-6, Kenneth Bolton wrote:
>
> ALLOWED_HOSTS is another one you should rely on the Django documentation 
> for. In fact, that should always be your first path.
>
> On Wed, Dec 24, 2014 at 10:32 AM, J. Paskaruk  > wrote:
>
>> Keys defined in settings.py. new error:
>>
>> Traceback (most recent call last):
>>   File 
>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>> line 658, in main
>> docstring, callables, default = load_fabfile(fabfile)
>>   File 
>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>> line 165, in load_fabfile
>> imported = importer(os.path.splitext(fabfile)[0])
>>   File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
>> conf = __import__("settings", globals(), locals(), [], 0).FABRIC
>>   File "/home/jimmy/envs/TPH/tenprint/settings.py", line 347, in 
>> from local_settings import *
>>   File "/home/jimmy/envs/TPH/tenprint/local_settings.py", line 27, in 
>> 
>> "HOSTS": ALLOWED_HOSTS[:1], # List of hosts to deploy to (eg, first 
>> host)
>> NameError: name 'ALLOWED_HOSTS' is not defined
>>
>>  -- 
>> 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

If setting this is a required step to making the tutorial work, you should 
probably make note of that somewhere in the tutorial.

On Wednesday, December 24, 2014 9:41:18 AM UTC-6, J. Paskaruk wrote:
>
> I don't understand what you mean by my first path. Do you mean the first 
> thing I do, or the variable should consist of my first path? Which path is 
> my fist path?
>
> On Wednesday, December 24, 2014 9:37:21 AM UTC-6, Kenneth Bolton wrote:
>>
>> ALLOWED_HOSTS is another one you should rely on the Django documentation 
>> for. In fact, that should always be your first path.
>>
>> On Wed, Dec 24, 2014 at 10:32 AM, J. Paskaruk  wrote:
>>
>>> Keys defined in settings.py. new error:
>>>
>>> Traceback (most recent call last):
>>>   File 
>>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>>> line 658, in main
>>> docstring, callables, default = load_fabfile(fabfile)
>>>   File 
>>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>>> line 165, in load_fabfile
>>> imported = importer(os.path.splitext(fabfile)[0])
>>>   File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
>>> conf = __import__("settings", globals(), locals(), [], 0).FABRIC
>>>   File "/home/jimmy/envs/TPH/tenprint/settings.py", line 347, in 
>>> from local_settings import *
>>>   File "/home/jimmy/envs/TPH/tenprint/local_settings.py", line 27, in 
>>> 
>>> "HOSTS": ALLOWED_HOSTS[:1], # List of hosts to deploy to (eg, first 
>>> host)
>>> NameError: name 'ALLOWED_HOSTS' is not defined
>>>
>>>  -- 
>>> 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 mezzanine-use...@googlegroups.com.
>>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Anyways, as I said, I added my actual domain to the variable, but it's 
still asking for a password. I tried just hitting enter, and I tried 
'vagrant' after adding the SSH_PASS variable, but no dice. I have no 
recollection of setting this password anywhere.

On Wednesday, December 24, 2014 9:42:00 AM UTC-6, J. Paskaruk wrote:
>
> If setting this is a required step to making the tutorial work, you should 
> probably make note of that somewhere in the tutorial.
>
> On Wednesday, December 24, 2014 9:41:18 AM UTC-6, J. Paskaruk wrote:
>>
>> I don't understand what you mean by my first path. Do you mean the first 
>> thing I do, or the variable should consist of my first path? Which path is 
>> my fist path?
>>
>> On Wednesday, December 24, 2014 9:37:21 AM UTC-6, Kenneth Bolton wrote:
>>>
>>> ALLOWED_HOSTS is another one you should rely on the Django documentation 
>>> for. In fact, that should always be your first path.
>>>
>>> On Wed, Dec 24, 2014 at 10:32 AM, J. Paskaruk  wrote:
>>>
>>>> Keys defined in settings.py. new error:
>>>>
>>>> Traceback (most recent call last):
>>>>   File 
>>>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>>>> line 658, in main
>>>> docstring, callables, default = load_fabfile(fabfile)
>>>>   File 
>>>> "/home/jimmy/envs/TPH/local/lib/python2.7/site-packages/fabric/main.py", 
>>>> line 165, in load_fabfile
>>>> imported = importer(os.path.splitext(fabfile)[0])
>>>>   File "/home/jimmy/envs/TPH/tenprint/fabfile.py", line 26, in 
>>>> conf = __import__("settings", globals(), locals(), [], 0).FABRIC
>>>>   File "/home/jimmy/envs/TPH/tenprint/settings.py", line 347, in 
>>>> 
>>>> from local_settings import *
>>>>   File "/home/jimmy/envs/TPH/tenprint/local_settings.py", line 27, in 
>>>> 
>>>> "HOSTS": ALLOWED_HOSTS[:1], # List of hosts to deploy to (eg, first 
>>>> host)
>>>> NameError: name 'ALLOWED_HOSTS' is not defined
>>>>
>>>>  -- 
>>>> 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 mezzanine-use...@googlegroups.com.
>>>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Time to upgrade jQuery?

[J. Paskaruk]

Hi, I'm a newb who literally wrote his first jquery last week - I coded a 
leet document ready thing to move a div from one spot to another. So you 
could say my jquery needs are pretty simple at this point.

Strictly for my benefit, and perhaps in order to bolster your case for a 
distributed upgrade, could you expand a bit on what the newer jquery would 
offer over the older one? My understanding is that jquery is kind of a 
"standard toolbox" for js operations, and the basic Mezzanine interface is 
fairly simple, so I guess I'm wondering whether this is a case where an 
upgrade has limited benefit, and a risk of destabilizing the overall 
infrastructure, maybe? But again, see first paragraph. I'm just trying to 
stir up conversation. :>

On Wednesday, December 24, 2014 5:37:52 PM UTC-6, Eduardo Rivas wrote:
>
> Hello everyone! I've started upgrading Mezzanine to the latest version of 
> Bootstrap (v3.3.1) and this would require at least jQuery 1.9.1 [source 
> ]. 
> I've encountered this problem before when using third party libraries that 
> don't play along with Mezzanine's three year old version of jQuery (1.7.1, 
> released 
> November 2011 ). 
> I would like to ask everybody (and Steve specifically) if you are open to 
> upgrading the version of jQuery to at least 1.9.1. Cheers.
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

It's good that you brought this up, because this is actually a problem I've 
had, as someone just starting out with web dev, and with coding, with how 
the CMS is distributed.

Django is the Framework, on top of which Mezzanine, the CMS, runs.

Why, then, is Mezzanine distributed with Django subsumed into its 
installer? This creates a falsely monolithic aspect to Mezzanine. I 
understand the convenience, but it muddies the view.

You quizzed me on irc as to whether I had done the Django tutorial. I told 
you that I had, and indeed, I did it multiple times, and supplemented that 
with other well-known tutorials, both Django and Rails, to solidify the MVC 
concept (it is my policy, whenever possible, to have every thing I learn, 
be it a practical system or an abstract concept, explained to me by three 
different people/documents/videos/tutorials/whatever). The source of my 
glaringly stupid errors is not that I haven't done my homework, however 
that may look.

This is the problem I have with how Mezzanine is distributed - the Django 
tutorial teaches you to think of things as having a certain type of file 
structure, with a models.py and a views.py, for instance, in your project's 
home dir. If you install Mezzanine, these files are not there. They 
obviously are *somewhere*, but they are most distinctly *not* where the 
Django tutorial told me to expect to find them. I did not, and I still do 
not, know exactly how to do deal with that, because it doesn't fit into the 
schema that I learned in the Django tutorial. My intention, when I learned 
about Mezzanine and decided to try it out, was to install it and examine 
the code, *specifically* in the context of having *just* done the Django 
tutorial. But because the files were not where I expected them to be, and 
because I was too new and too ignorant of about a thousand other things (at 
every level - Python, Django, Linux, Abstract Programming Concepts - every 
level), I was stymied. I'm working alone, with no peers, so whatever 
resources are on the net are all I've got. My goal is to be able to work 
straight from Django and develop complex apps of my own (and ultimately, 
recreate my rather simple Blog from my own models and views - not because 
it's better to do it that way, but because it's more instructive and 
useful, on a personal development level, to do it that way).

Mezzanine doesn't just run on top of Django, it *hides* Django, and itself 
for that matter, from the new user, and thus far, I haven't found a 
document on the web that explains why the views.py and models.py got 
hidden, and where I can find them and look them over and mess around with 
them - indeed, *all* of Mezzanine's infrastructure is hidden. If this is a 
structure that has been built on top of a Django framework, why can't I, 
having done the Django tutorial, easily examine that infrastructure, to see 
how it works? Why is the directory structure changed, and where is the 
Mezzanine tutorial that explains this to newbies who have *only* done the 
Django tutorial?

I realize that I can, that I only need to hunt down those views and models, 
which I know are in there somewhere, but the creators of Mezzanine have 
taken steps to make them hard to find for newbies. I'm sure that it makes 
things a million times easier for professionals, of course, in ways that I 
do not understand yet, but of which I acknowlege, and plead, my own 
ignorance.

So, when you admonish me to check the Django docs in cases where the 
problem is a Django problem rather than a Mezzanine problem, I would like 
*nothing* more than to do just that, I assure you, but I'm at the "drinking 
from the firehose" phase of my personal development into a developer, and I 
have a hard enough time sorting out which parts are Django and which parts 
are Mezzanine, *without* the fact that Mezzanine is not distributed 
separately from Django in spite of the fact that it *is* separate from 
Django, and indeed, is setup in such a way as to make the lines between the 
two *extremely* blurry for a beginner like me.

I noticed, as a suggestion, that there's an IDE, Aptana I think? That's 
distributed both as a monolithic app, and as a plugin to Eclipse - maybe 
Mezzanine could release an "explicit" version that "plugs into" a raw 
Django server, so that competent-but-ignorant folks like myself, fresh out 
of Django tutorial school, could more easily recognize that line between 
Django and Mezz? I've actually been trying to figure out how to find the 
actual Mezzanine code for a while now, cause the way I really learn is by 
messing around with stuff at that level, changing words or colour settings, 
so I can just see what affects what, and after a while (after breaking and 
restoring it a billion times) I get so I really know the thing. But 
reaching that point is touch and go, and unfortunately, the working dev's 
emphasis on "getting things done" stands in the way of actual learning, 
much of the time. While I recogniz

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

(To clarify, when I said "this community," I meant the FOSS community, not 
the Mezzanine community.)

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Thanks for the encouragement. I'm pretty good at expressing myself with 
words (no braggin', as Will Sonnett used to say at 3am, just facts), but 
sometimes that expressive ability makes me come off like an arsehole. Most 
cause I'm kind of an arsehole. But my intentions are very good, for 
whatever that's worth. I read the fab docs yesterday. Anyways, I see the 
value of all these things. Just continuing to hold my face squarely in 
front of this here firehose. 

The way I'm looking at the best practices thing is that there are best 
practices for working professionals, and there are best practices for 
students. I know that there are many more days ahead of me, reading docs, 
but at this point I'm flailing just to find the right docs to read (if you 
have any "everyone should read this" links or books, or hell, if someone's 
laid out a curriculum that you think I should follow, I'm all ears...). 
This whole experience has been very instructive, needless to say, and 
that's all I'm after for the moment - grand failures that reveal inner 
workings. In order to fail in a properly grand fashion, I need to have the 
ability to throw a wrench into the gears of the factory, which fortunately 
for us, is perfectly fine to do in circumstances where the entire factory 
can be restored by a keystroke. But the entire system is, of course, 
designed to stop people from doing such foolish things in daily life. Every 
tutorial contains at least a nod, and usually a speech that borders on 
sanctimony, about best security practices. Not that this is not valuable 
knowledge, of course, but security is not your priority if you're trying to 
learn how to code a given functionality.

Anyways, my site is currently laid out with "pure" css, right now I'm 
occupying myself by trying to recreate the same layout leaving bootstrap 
intact. Being that I've done a couple of respectable responsive designs on 
my own, I'm not a big fan of Bootstrap's complexity, but then, I want a 
job. Also, I'm told it's very good at automating form validation, which I'm 
all for avoiding if I can...:>

Anyways, again, I appreciate your help AND doubly appreciate your 
encouragement. Schools and teachers have never worked for me, so learning 
things is always a struggle, and finding people with the right sort of 
patience is a struggle of its own. 

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

(To clarify, though, I'm not proposing to make direct modifications to 
Mezzanine as a working thing. I just want to open it up and see what it 
looks like in there, maybe poke at its brain and make it smell burnt toast, 
you know?)

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

I'm divin', man, I'm divin'. Honestly, I'm actually very comfortable with 
what Django is and does, in the abstract, and I have a couple of things I 
plan to develop literally as soon as I have a live site deployed. 

First is, I'm planning to move in the next couple months, and among the 
things to do is sell off my book collection, so I'm gonna write a little 
app to list my books, with prices, genre, etc - I seem to vaguely recall 
that there is actually a Python library that enables you to scan barcodes 
and get book info, which (if that actually exists) will be a useful 
exercise in importing libraries, doing stuff in views, etc. I have a few 
other, weirder ideas too, and home automation was one of the main things 
that brought me here. Start off with little things like this, but I need to 
be able to share the durn thing with my friends, and I also need a working 
web page. I hate PHP. I put it up with Wordpress because Wordpress has a 
huge community, basically, and I figured (rightly) that I would have the 
easiest time with it, and my goal at the time was more to get my CSS-fu, 
which I largely have now done. I'm just about ready to start integrating 
jquery into my designs (as mentioned, I actually did my first little jq 
piece the other day, but now I need to add an on resize thing... lotsa 
fun.).

The actual programming is basically just some time I need to spend building 
increasingly complex things, but I didn't want to waste any time developing 
on Wordpress, hence my desire to just get *something* deployed, and start 
building from there. 

I'll peruse the repo for sure, and I will orient around the urls. That 
(indicating where I should start looking, in the abstract) is a very useful 
piece of advice for the way my brain works. :>

On Friday, December 26, 2014 9:02:46 PM UTC-6, Kenneth Bolton wrote:
>
> http://effectivedjango.com/  <== Very helpful!
>
> Just keep at it. For whatever it is worth, I am largely self taught. When 
> I started, documentation and "use the source, luke" was most of the help 
> available. It took me years to start diving into that good stuff. I can 
> tell you the reason I went with Django over RoR or a PHP framework was the 
> quality of the documentation and the readability of the Python code. 
>
> The place to start, I think, in reading the Mezzanine code is in the base 
> urls.py 
> <https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/urls.py>. 
> Work your way down the file and understand each line. Follow the patterns 
> into the apps that make up Mezzanine – e.g. core, generic, blog, and pages 
> – and read their respective urls.py.
>
> If it helps, think of Mezzanine as a Django app that has already been 
> built to eliminate the tedium of building yet another hierarchical page, 
> gallery, and blogging engine. The deeper your understanding of and comfort 
> with Django, the better the whole thing will click. An instructive analogy, 
> for me, is to reading and writing prose. The more prose you read, the 
> better you get at reading it. Once you have read enough prose, the quality 
> of your own prose will begin to improve (hopefully) and before long reading 
> and writing prose becomes second nature. Code – whether Python, Ruby, Java 
> – needs to be practiced, and reading code is the first step.
>
> Ultimately, just keep at it. If it interests you and you put in enough 
> time, things will click. Some people get that click quickly. It took me a 
> long time – almost 14 years – to transition from beginner reader of code 
> convinced I had no aptitude for it to the first steps down with writing 
> code on my own. The best part is that once the dots start to connect, the 
> world really opens up. Also, the learning NEVER ends!
>
> best,
> ken
>
>
> On Fri, Dec 26, 2014 at 8:09 PM, J. Paskaruk  > wrote:
>
>> Thanks for the encouragement. I'm pretty good at expressing myself with 
>> words (no braggin', as Will Sonnett used to say at 3am, just facts), but 
>> sometimes that expressive ability makes me come off like an arsehole. Most 
>> cause I'm kind of an arsehole. But my intentions are very good, for 
>> whatever that's worth. I read the fab docs yesterday. Anyways, I see the 
>> value of all these things. Just continuing to hold my face squarely in 
>> front of this here firehose. 
>>
>> The way I'm looking at the best practices thing is that there are best 
>> practices for working professionals, and there are best practices for 
>> students. I know that there are many more days ahead of me, reading docs, 
>> but at this point I'm flailing just to find the right docs to read (if you 
>> have any "everyone should read this" links or bo

[mezzanine-users] Re: Is there a way to add Mezzanine to the One-Click Django server on DigitalOcean?

[J. Paskaruk]

Speaking of jquery, do you have an opinion on the best way to customize 
design and presentation? this time around, I created an app and copied the 
base and index html files and bootstrap-theme.css, to which I'm adding 
custom styles at the bottom. I see a lot of talk about Bootswatch and about 
compiling your own Bootstrap, but I'm reluctant to start downloading and 
making my own, cause I'm sure there's a lot of integration behind the 
scenes with Mezz. Whatever the case, I'm trying to work with Bootstrap 
cause I know I pretty much have to if I expect to work, and there's all 
kinds of advice - that other fellow from the Mezz main page, I loved his 
Getting Started tutorial, we have similar philosophical views, for 
instance, but he actually recommends several approaches, and doesn't really 
offer a "this is the best" answer. What I'm doing works well enough, but it 
could actually be awful in ways I cannot perceive. Messing with Bootstrap 
at all is a nightmare, given the responsive aspects. Much easier to just 
write my own, from a strict design point of view...

On Wednesday, December 24, 2014 7:14:20 AM UTC-6, J. Paskaruk wrote:
>
> I've spent the last week attempting a manual deployment on an Ubuntu 
> server, and at this point, I'm seriously considering going back to 
> Wordpress. 
>
> Is it feasible to create a One-click Django server, ssh into the server, 
> install Mezzanine in the backend, and then add the various Mezzanine apps 
> to the already-working settings.py, and then modify the site from there?
>
> I've had my site finished and ready to go in the dev server for a week 
> now. Deployment should be easier than this.
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.