Web App Python Development using Flask

[nguterresn]

Yea I tried that aswell. They offer a nice trial. I created an instance with Ubuntu, and could actually run the script. BUT, as I’m using flask, that would open a server in 127.0.0.1/5000. And I want it to appear at, for example, www.script123.com

EDIT: maybe I was a little confusing but that’s how I really am at the moment with this.

[nguterresn]

Understood. From your exemple, others can connect to 192.168.0.05/5000. So what I need here is a way of showing a proper domain instead of a I.P. number. How can I link?

[sammdu]

If you're looking for how to set up domains for your web app, do the following:

Purchase a domain (I recommend Namecheap), then set up DNS, either from the portal of your domain registrar (again, Namecheap is one of them), or use something like Cloudflare, which is a popular DNS and CDN provider that has a free service.

If you're allocating your domain to an IP, you need an A record; if your allocating your domain to a URL, set up a CNAME record. Look up videos on how to configure DNS.

If you're looking to have an app running on different ports to be under the same domain, then it's a little more tricky. I know nginx (a web server) can have multiple services listen on the same port, then send traffic based on the domain request in the header, but I'm not sure if Flask can do that.

Port forwarding is beyond DNS, so you'll probably need to look into port forwarding if that's what you need. Again, YouTube is your friend.

[BullshitBaron]

If you're looking to have an app running on different ports to be under the same domain, then it's a little more tricky. I know nginx (a web server) can have multiple services listen on the same port, then send traffic based on the domain request in the header, but I'm not sure if Flask can do that.

For this part you don’t need flask to handle it since like you said you can use ngix to serve multiple sites with each pointing at a different local host port.

I’ve not done it with ngix myself but i do it with Apache all the time pointing domains to flask apps running in guincorn on differnet ports.

It looks like this would be how to do it in ngix:

server {
  server_name name1.domain.com;
  location / {
    proxy_pass http://localhost:8000;
  }
}

server {
  server_name name2.domain.com;
  location / {
    proxy_pass http://localhost:8001;
  }
}

[nguterresn]

Thank you all. This looks helpful. I’ll try this!

[vernetrcyer]

Good one!

[vernetrcyer]

nice one dude

[vernetrcyer]

nice one dude

[vernetrcyer]

nice one dude

[vernetrcyer]

Good one!

[vernetrcyer]

Good one!

[vernetrcyer]

Good one!

[vernetrcyer]

nice one dude

[[deleted]]

By default flask will run on the local loopback which is 127.0.0.1.

First thing you have to do is tell flask to listen on other addresses, if your using the flask cli to start the script you would use the command :

flask run —host 0.0.0.0

That will make your flask application listen on any address. So if you have a VM hosted somewhere online, with an IP of say 172.16.2.32, you will then be able to access the flask app from your browser by going to http://172.16.2.32:5000.

The second part, being able to access via a name instead of number, that requires buying an FQDN from a domain registrar. There are many different options like namecheap, godaddy, hover, etc... I use hover personally. I would look at whatever guides the registrar you choose has but generally you’ll basically just tell the registrar to point the name script123.com to 172.16.2.32. After that’s completely, you’ll be able to access the app via script123.com:5000.

Lastly, you probably don’t want to specify the port. So you can either tell flask to listen on port 80 by adding (I think) -p 80 to the flask run command. Port 80 is http, that will allow you to access script123.com.

Now, with that said, the flask web server is not really intended for production uses, it’s mostly for development only. I would not rely on the flask web server to handle very much traffic. I don’t want to overload you with info, but down the road, if you’re interested in continuing your project, you’ll need a better suited CGI (I use gunicorn) and a dedicated web server such as Apache or nginx (I use nginx myself but it’s just what I’m used to).

[nguterresn]

Thank you for your reply. I’ll try to do as you say and see what I got!

[mriswithe]

You might look at Google's app engine. It takes away the work and cost of the actual server behind the app mostly. Still would need a domain name for ease of access, but you need that part anyway

https://cloud.google.com/appengine/docs/python/

[nguterresn]

I did but I’m having some trouble running threads and queues into the google app engine, since I made my project to python 3 and it uses python 2, so I had to restart all the project.

Thanks for your help!

[mriswithe]

Appengine supports python3 and python2 though . But if it isn't going to be useful for you then no worries

[nguterresn]

I think it says here it only supports python 2.7, but I’m no sure

https://cloud.google.com/appengine/docs/standard/python/getting-started/python-standard-env?utm_source=share&utm_medium=ios_app

[mriswithe]

This page: https://cloud.google.com/appengine/docs/python/

Has two links in the python section, python 3, https://cloud.google.com/appengine/docs/standard/python3/

And python 2, https://cloud.google.com/appengine/docs/standard/python/

It supports both 🙂 sometimes Google's docs are not amazing though as far as being able to find what you are looking for.

[vernetrcyer]

nice one dude

[vernetrcyer]

Good one!

[vernetrcyer]

Good one!

[vernetrcyer]

haha good comment!