Not such an easy check - how do I do that? Also, what is the 'uswgi daemon'?
Perhaps I'm asking the wrong question. I've developed a Web2py application for Home Heating Control and a suite of radio linked hardware to make it work. I'm a hardware/embedded software engineer by profession with no previous knowledge of Linux, but I've managed to pick up enough knowledge to navigate around, run commands, edit files, start processes automatically at start up etc,, but only if I'm given the actual command to run or the exact lines to add to a configuration file. I would like to make my Heating application available to others, so wanted to start with a new Raspberry Pi, go through the steps to get it running for myself but also documenting the steps to pass on to potential users. Obviously this has gone off the rails at a very early stage and I don't know how to fix it. The people who would potentially be wanting to use my application will be hobbyists, buying their first Pi, installing Web2py to run from a browser on remote PC, downloading my application and using it. They will not have, and should not need have to have any in-depth knowledge of Linux to do this. If the 'one step' script doesn't work, where do I find a bulletproof procedure that works? I also tried the procedure given in: https://www.digitalocean.com/community/tutorials/how-to-deploy-web2py-python-applications-with-uwsgi-and-nginx-on-ubuntu-14-04 ...although it still assumes that I know what 'server_domain_or_IP' and 'myapp' should be, which I don't. Anyway I guessed and everything worked apart from the last step 'sudo service uwsgi start' which failed with the message: Failed to start uwsgi.service: Unit uwsgi.service failed to load: No such file or directory. Probably points to the same issue, but still offers me no clue how to resolve it. On Wednesday, November 23, 2016 at 8:54:43 AM UTC, Niphlod wrote: > one step deployment imho is not "assured to be working" on raspberry. > easy check: do you have an uwsgi process running ? > > On Tuesday, November 22, 2016 at 11:19:32 PM UTC+1, Richard Brown wrote: >> >> Thanks for the reply. The key word here is obviously 'should' - but is it >> something that should have happened or something I should have done, and >> how do I resolve it? I used the 'one step deployment' script as thought it >> would do everything I need to get Web2py working. >> >> Richard >> >> On Tuesday, November 22, 2016 at 7:19:25 PM UTC, Niphlod wrote: >> >>> that should be generated by the uwsgi daemon >>> >>> On Tuesday, November 22, 2016 at 6:34:40 PM UTC+1, Richard Brown wrote: >>>> >>>> I've just tried to do a new install of Web2py on a Raspberry Pi 3 >>>> having been using it under Apache on a Model B for a few years now. I used >>>> the script "setup-web2py-nginx-uwsgi-ubuntu.sh" which seems to have done >>>> most things correctly, but when I try to access the site I get a '502 Bad >>>> Gateway' error in my browser and the following error in >>>> /var/log/nginx/error.log: >>>> >>>> 2016/11/22 16:41:30 [crit] 648#0: *1 connect() to >>>> unix:///tmp/web2py.socket failed (2: No such file or directory) while >>>> connecting to upstream, client: 192.168.1.65, server: raspberrypi, >>>> request: >>>> "GET / HTTP/1.1", upstream: "uwsgi://unix:///tmp/web2py.socket:", host: >>>> "192.168.1.60" >>>> >>>> There is no web2py.socket file in the /tmp directory or anywhere else >>>> that I can find. I can see where the script sets up the path to this file >>>> but nothing about how the file itself should get there. Where do I find >>>> this file, or should the configuration point to a different file? >>>> >>>> Thanks, >>>> >>>> Richard >>>> >>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
