• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Flask subdomain separation

elenaflorence

New Pleskian
I need practical advice if my approach is correct.

What is the goal?

Having flask app that is separated between 3 subdomains: admin. | api. | user. There will be some shared data like models

What I did so far

I am new to Python, but this is how I made it and it works. I'm just not really sure it's the correct approach.

At the beginning I made it all with one vhost and ServerAlias but I had SSL issues

So I did this:

  1. I have created one flask app with blueprints for all those areas (subdomains)
  2. I'm using self-hosted Plesk server with mod_wsgi
  3. I have configured 4 separate vhosts - admin,api,user,static
  4. Each of the vhosts(except static) has it's own .wsgi config file that calls create_app factory with the appropriate parameter (ex. application = create_app("api"))
  5. Inside create_app I register only the blueprints which are related to the subdomain
 
Back
Top