Forums

I am using Flask and created a second web app for a new site. I have an older Flask site on the other web app which has been running fine.

It has been a while since I have done this and it seems like I am missing a step...

I created the new web app, set up a new virtual env, installed Flask in the venv, pulled the code from Github and reloaded the web app. The URL is http://webapp-885409.pythonanywhere.com/

I can not get it to recognize my own app.py. Maybe something to do with the wsgi file?

Thanks!

Your site with that CNAME identifier looks like it's up and running now -- did you work out what the problem was?

I was not sure if I needed to have a CNAME in my DNS pointed to it first so I updated that last night. Same problem though. I can't get it to not display the Python Anywhere coming soon page...

Neither of your web apps is returning a "Coming soon" page. We do not serve the site from the webapp- address, that's just a pointer for the DNS system to use.

I do see the DNS change has taken place but if I go to http://webapp-885409.pythonanywhere.com/ I still see the coming soon page. I thought that would be reading from my app.py file for the routes. No?

I don't remember having to use my own web URL for my other site until my dev work was completed.

We do not serve the site from the webapp- address, that's just a pointer for the DNS system to use.

So for future reference, this means I always have to have a domain name pointed to my Pythonanywhere app even while developing? I can't use the internal name?

Sorry to be dense but I don't remember having to do this before.

Yes, that is true. We may rethink it in future, but right now, that is what is necessary.