Re: [mezzanine-users] Nested Orderable classes
Hi Josh, thanks for getting back so soon! If I'm being fully honest, my django chops aren't good enough to understand how to implement your suggestion. I'm sure it's a much more streamlined approach than my actual solution, which was to relate sections to subsections through a many-to-one relationship (eg, create a section and add subsections kind of like adding tags to a blog post). Then, in pages/index.html I created a series of for and if statements to render each subsection depending on the context of the section (basically used the "section" attribute of each subsection to determine where it should be rendered). Although it took a bit of typing, at least it's dry (which is more than I can say for some of my projects). Thanks again! On Monday, 22 December 2014 10:43:03 UTC-8, Josh Cartmell wrote: > > Hey Avery, you do make sense and I've done something similar. In the > models of the first section (that has sub sections) I would add something > like: > > def edit_subsections(self):'''Returns a link to this > items change form'''if self.id:return ' onclick="return showAddAnotherPopup(this);" href="%s">Edit documents' % > admin_url(self.__class__, "change", self.id)return '' > edit_subsections.allow_tags = True > > > Then inside the admin class for that you can add edit_subsections to the > fields (or fieldsets). It also needs to be added to readonly_fields. That > will use Django's normal admin popups, but you could update the > edit_subsections method to work in any way you want. > > Hopefully that's a good start! > > On Sun, Dec 21, 2014 at 1:11 AM, Avery Laird > wrote: > >> Hi, >> >> I'm building one of those one page sites (that all the cool kids seem to >> have) and I have run into a bit of a problem. I have a custom Page class, >> with a few orderable classes that inherit from that, but I'm not sure what >> the best course of action to take is for the individual sections. I'm >> thinking about making another Orderable class, which inherits from the Page >> class, but has other orderable classes nested underneath it to form the >> sections of the site. For example, each "section" orderable has a heading >> and subheading, with other orderables nested within that can be added in >> the admin much like orderables can be added to pages. If there was a >> section with 3 icon blurbs, then there would be a "section" orderable, and >> an "icon blurb" orderable that inherits from that class. Then, in the >> admin, it can be added to every section class that is added to a page >> class. The only problem is, I have no idea where to start, whether this is >> even possible, or if I'm making any sense at all. I'd appreciate any >> insight anyone may have. >> >> Cheers, >> >> Avery >> >> -- >> 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.
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.
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? > > 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 goo
Re: [mezzanine-users] Having trouble deploying.
I second Josh with regard to reading the fabfile now and then. When someone has a problem deploying, I walk through their process and compare it to the fabfile. >From the Zen of Python: There should be one – and preferably only one – obvious way to do it. On Mon, Dec 22, 2014 at 1:49 PM, 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? > > 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 >
Re: [mezzanine-users] Having trouble deploying.
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? 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
Re: [mezzanine-users] Nested Orderable classes
Hey Avery, you do make sense and I've done something similar. In the models of the first section (that has sub sections) I would add something like: def edit_subsections(self):'''Returns a link to this items change form'''if self.id:return 'Edit documents' % admin_url(self.__class__, "change", self.id) return ''edit_subsections.allow_tags = True Then inside the admin class for that you can add edit_subsections to the fields (or fieldsets). It also needs to be added to readonly_fields. That will use Django's normal admin popups, but you could update the edit_subsections method to work in any way you want. Hopefully that's a good start! On Sun, Dec 21, 2014 at 1:11 AM, Avery Laird wrote: > Hi, > > I'm building one of those one page sites (that all the cool kids seem to > have) and I have run into a bit of a problem. I have a custom Page class, > with a few orderable classes that inherit from that, but I'm not sure what > the best course of action to take is for the individual sections. I'm > thinking about making another Orderable class, which inherits from the Page > class, but has other orderable classes nested underneath it to form the > sections of the site. For example, each "section" orderable has a heading > and subheading, with other orderables nested within that can be added in > the admin much like orderables can be added to pages. If there was a > section with 3 icon blurbs, then there would be a "section" orderable, and > an "icon blurb" orderable that inherits from that class. Then, in the > admin, it can be added to every section class that is added to a page > class. The only problem is, I have no idea where to start, whether this is > even possible, or if I'm making any sense at all. I'd appreciate any > insight anyone may have. > > Cheers, > > Avery > > -- > 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. > -- 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.
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? >>> >>> 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. > -- 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
Re: [mezzanine-users] Having trouble deploying.
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.
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 < jpaska...@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-users+unsubscr...@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] Having trouble deploying.
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.
