[web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

I'm working on revamping the scripts ... latest version (which one day or the other will be finalized) is ATM here https://gist.github.com/niphlod/8a13025001363657f0201b2a15dad41c On Wednesday, June 29, 2016 at 7:07:18 AM UTC+2, Ben Lawrence wrote: > > They changed upstart for Ubuntu 16 so this

[web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

They changed upstart for Ubuntu 16 so this script will work for ubuntu 14 and lower, not 16 ... as I experienced a few months ago (maybe things changed since then?) On Saturday, June 18, 2016 at 4:36:58 PM UTC-7, Anthony wrote: > > Oops. It is now recommended that you use nginx+uwsgi instead of

Re: [web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

Hello Horridohobbyist, You can also read the book on how to deploy Apache : http://www.web2py.com/books/default/chapter/29/13/deployment-recipes#Apache-setup We make a clean up in deployment scripts sometimes ago because many were outdated. We wand to avoid get to the same point (outdated stuff)

Re: [web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

Hi, On 19/06/16 00:49, horridohobbyist wrote: I don't have any experience with nginx. *Do I have learn nginx*, or will the setup-web2py-nginx-uwsgi-ubuntu.sh script *do everything for me* (I presume that's what one-step deployment means)? You can still use Apache - I'm wary of the one-step stu

[web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

You can use any of the scripts here that start with "setup" (some may be outdated -- we recommend nginx+uwsgi). I think they generally assume a fresh server and are not necessarily idempotent. Feel free to simply look through the scripts (wh

[web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

But what if my Ubuntu server is already setup for Apache. Do I have to abandon or *uninstall* Apache? I don't have any experience with nginx. *Do I have learn nginx*, or will the setup-web2py-nginx-uwsgi-ubuntu.sh script *do everything for me* (I presume that's what one-step deployment means)?

[web2py] Re: One-Step Production Deployment: Who Moved the Cheese?

Oops. It is now recommended that you use nginx+uwsgi instead of Apache+mod_wsgi, so, you could change the URL to: https://raw.githubusercontent.com/web2py/web2py/master/scripts/setup-web2py-nginx-uwsgi-ubuntu.sh Anthony On Saturday, June 18, 2016 at 4:35:37 PM UTC-4, horridohobbyist wrote: > >

[web2py] Re: One Step Production Deployment

I downloaded the zip file for the source. I unzipped it in my home directory, went into the scripts folder and executed setup-web2py-ubuntu.sh. For some reason, this gave me a working installation, whereas going the wget route did not. On Saturday, 15 March 2014 17:11:42 UTC-4, Anthony wrote:

[web2py] Re: One Step Production Deployment

On Saturday, March 15, 2014 4:10:32 PM UTC-4, horridohobbyist wrote: > > Well, I solved the problem by installing manually from source (ie, wget, > ./setup-web2py-ubuntu.sh). > Can you explain what you mean by "manually from source"? Aren't those the exact instructions for the one-step productio

[web2py] Re: One Step Production Deployment

Well, I solved the problem by installing manually from source (ie, wget, ./setup-web2py-ubuntu.sh). Strange that this works and the "One step production deployment" doesn't. Someone really ought to look into this. On Saturday, 15 March 2014 15:15:52 UTC-4, LightDot wrote: > > As I just wrote in

[web2py] Re: One Step Production Deployment

As I just wrote in another thread: the _2.9.4 comes from *virtual* static asset management. This number will change now and then, as static files get updated, so please don't go creating actual folders for this. This feature is defined with response.static_version, it's in the book and the trou

[web2py] Re: One Step Production Deployment

Sorry, I spoke too soon. While the visual rendering is okay, the menus don't work. So I can't create the _2.9.4 folder. Damn. On Saturday, 15 March 2014 13:08:36 UTC-4, horridohobbyist wrote: > > Okay, I solved the other piece of the mystery. The Administrative > Interface view is now referenci

[web2py] Re: One Step Production Deployment

Okay, I solved the other piece of the mystery. The Administrative Interface view is now referencing its CSS, JS, and plugins in a folder one level deeper called "_2.9.4". So I simply created a _2.9.4 folder and moved css, js, plugin_multiselect and plugin_statebutton into it. Everything is now

[web2py] Re: One Step Production Deployment

Okay, I figured out what happened. During the "One step production deployment", *for some reason*, the wsgihandler.py file did NOT get copied to the web2py parent folder. Don't ask me why. (In my test VM, the wsgihandler.py file did get copied, in fact, moved. Go figure.) Now, I'm finding that

[web2py] Re: One Step Production Deployment

hm, not sure about the web2py process running, because it's just a framework that access by webserver. not just web2py, i think the other web framework too. at least for ensure that your web server is running, perhaps you can do in terminal something like : netstat -tnlp or top | grep apache an

[web2py] Re: One Step Production Deployment

Well, it's not the welcome app. I also can't access the administrative interface: https://67.213.70.250/admin It's almost as if web2py isn't running. How can I verify that the process is running? On Saturday, 15 March 2014 08:09:37 UTC-4, 黄祥 wrote: > > had you remove the welcome apps? please

[web2py] Re: One Step Production Deployment

had you remove the welcome apps? please describe your steps that reproduce the error. ref: http://www.web2pyslices.com/slice/show/1957/install-web2py-on-lubuntu-with-apache-and-mod-wsgi best regards, stifan -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://git