flaskapp | Python Flask starter application complete | Frontend Framework library

Turns out I was just starting the existing images of the containers by running

docker-compose up

So all I had to do was to build new images and then run those images.

docker-compose up --build

I set the AIRFLOW_HOME and AIRFLOW__CORE__SQL_ALCHEMY_CONN environment before run airflow db init.

Playbook version

In your return statement, you are using "{{}}", just remove those and it will work fine. It should be like this

Ok, I was focused on a big problem, but the problem is so simple that I did not realize it: Replace all [] with (). See below.

If you [] it assumes as dict and you are returting a list or set.

Put this in your dockerfile:
RUN pip install pandas

You should consider using a requirements.txt file for dependencies.
Copy the requirements.txt to your container and install the requirements:
RUN pip install -r requirements.txt

The if block inside the certbot managed server block will just capture the www.example.com server name and redirect that to the https server block.

To do the same for non-www

configuration file /etc/nginx/sites-enabled/flaskblog:

For me, this came down to a permissions issue. My first speculation was that the environment was not registering correctly, however in fact it was that IIS did not have permission to access all the dependencies of the environment.

How I resolved this was to navigate to my Anaconda3 folder, right click and select properties. In the properties window, I navigated to the security tab and clicked Edit

I then clicked 'Add' to add users and bring up the following window

Under Object Type, I selected all the options, and Locations I selected the top level location.

Under Object names I wrote iis apppool for example, for an IIS site named app, it would be iis apppool\app

I then clicked check names to ensure the app could be found, and then proceeded to click ok and apply.

Once the permissions were added, the IIS site could access all the required dlls and such and the app functioned correctly

0.0.0.0 is not a valid IP Address. Try 127.0.0.1 which refers to the local host. like this:

It appears that the python interpreter is compiled into the mod_wsgi.so file. An old version, that included python2, was being pointed to by Apache. To fix it I did the following:

1. Removed the old version of mod_wsgi by doing sudo apt-get remove libapache2-mod-wsgi
2. modified /etc/apache2/mods-available/mod_wsgi.load to point to the library (.so) file in my virtual environment. The contents of mod_wsgi looked like this: