interesting, so what you're saying is that once i deploy to python anywhere ill no longer have any problems with setting up Nginx. Great! Will the payment part of my website still be accessible, just not trusted, without an ssl certificate?
On Wednesday, October 26, 2016 at 1:56:04 AM UTC-5, Anthony wrote: > > > scripts/setup-web2py-nginx-uwsgi-on-centos.sh >> scripts/setup-web2py-nginx-uwsgi-ubuntu.sh''' >> >> Does this mean that once I complete these steps then I'll have >> successfully deployed to nginx and that I'm able to access the website from >> online? >> > > Yes, though you will need to take additional steps for access via a domain > name rather than just the IP address of your server (i.e., you need to > register a domain name and configure the nameservers so it points to your > domain). Also, the web2py scripts set up a self-signed certificate, which > is fine for development use or your personal access to admin, but it will > generate browser warnings for regular users, so you will want a certificate > from a certificate authority for production purposes. > > >> Here is some information that I found online just now: >> ''' >> PythonAnywhere is an online Integrated Development Environment (IDE) and >> Web hosting service based on the Python programming language. ''' >> >> '''Nginx can be deployed to serve dynamic HTTP content on the network >> using FastCGI, SCGI handlers for scripts, WSGI application servers or >> Phusion Passenger modules, and it can serve as a software load >> balancer.[9]''' >> >> Based off of the links you sent on nginx, I'm assuming that i'll need to >> switch from developing my site on my localhost to the nginx software. Why? >> > > localhost refers to the location of the server (your local machine), not > the software you use to serve HTTP requests. You can run Nginx on your > localhost if you want. > > In development, you might be using the web2py built-in Rocket server. This > server is a fairly basic web server written in Python -- it is not > recommended for production, as there are much faster (and likely more > reliable/stable) options, such as Nginx+uWSGI. > > >> I get a feeling that nginx provides some sort of encryption. An >> encryption that pythonanywhere doesn't. Am I wrong? Am I comparing apples >> and oranges because they aren't similar? >> > > No, nothing to do with encryption. > > >> Ultimately, I plan on releasing my website when it's almost finished and >> tampering with it while it's live kind of like Kanye wests album release. >> Python anywhere seems to provide me with that ability. Will I need to >> switch my app from localhost to nginx an then deploy to pythonanywhere? >> > > If you deploy to Pythonanywhere, they actually take care of setting up the > web server for you (that's part of the value of their service -- they make > deployment simple by handling the server administration). In fact, > Pythonanywhere will serve your app via Nginx+uWSGI (but you don't have to > bother with it at all). > > Anthony > -- 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.
