flasky | minimalist pelican theme | Static Site Generator library

In my experience, a while ago I had a very similar issue that you you were having. After troubleshooting, I found out that my code worked when I would create a mail class, and call function like $mailclass.ehlo etc.

Based on the error its having an issue connecting or staying connected. Try calling the connect methods in the function itself and close of the connection after each email.

From your documentation article:

Added in version 3.4 file format

^{Source: https://docs.docker.com/compose/compose-file/#network}

But you are on version 3.0

See:

Note: When specifying the Compose file version to use, make sure to specify both the major and minor numbers. If no minor version is given, 0 is used by default and not the latest minor version. As a result, features added in later versions will not be supported. For example:

From the CLI you need to run your script as follows:

chmod +x boot.sh should solve your problem. I could reproduce the issue when chmod +x was not done-

In main you use app.run() so app is avaliable in main. It should be also avaliable all time in all functions so you can try to use

I think what you are really asking is "How to health check a uWSGI application". There are some example tools to do this. Particularly:

• https://github.com/andreif/uwsgi-tools
• https://github.com/che0/uwping
• https://github.com/m-messiah/uwget

The uwsgi-tools project seems to have the most complete example at https://github.com/andreif/uwsgi-tools/issues/2#issuecomment-345195583. In a Kubernetes Pod spec context this might end up looking like:

The same question is asked on Github, where Miguel answers it: https://github.com/miguelgrinberg/flasky/issues/154#issuecomment-395907521

To quote:

The config module is found because it is in the current directory. It does not matter from where it is imported, the fully qualified location for that module is just the module name. This is actually the same reason why you can say from app import .... The app package is found because it is in the current directory, same as config. Hope this clarifies it.

And further down:

You have a misunderstanding of what "current directory" means. The current directory is an operating system concept, each process has a directory that is marked as the current directory. By default, the current directory for a process is the directory from where the application was started (but the application itself can change this if it wants to). In this case, you start the application from the flasky directory, right? So that is your current directory. From any Python modules you can import config and app without problem, because the current directory is in the Python import path.

Hope that helps.

I finally fixed that bug with switching the python version. I found out that Python 3.7 does not support win32 in some ways. I installed the python 2.7 then it works. Of course, I changed the environment path variables and installed win32 for python 2.7 manually.

Networking is a big topic, but generally speaking

• big networks (like the Internet) are made up of smaller networks (like your local network)
• devices on smaller networks aren't usually accessible from outside of those networks¹
• the IP address you've partly shown starts with 192 and I bet the next octet is 168, which means it's a private network and therefore can't be accessed from the Internet (as an example, there are many machines out there with the address 192.168.1.10—this can exist on any private network)
• if you need to expose something on your local network, for example something with an IP address of 192.168.1.10, you must do some extra work²

Here are some options:

• Host your database in the cloud, e.g. using Heroku's PostgreSQL service
• Host your web service internally so it can connect to your database using its internal 192.168.x.y address
• Host internally as with the previous option and expose your local web application to the Internet so users can access it from outside your network
• Rent a VPS so you can host outside of your network but retain a measure of control about how your data is stored (and accept the administrative overhead and responsibility that comes with that)

I wouldn't suggest leaving the web application outside your network, your database inside your network, and exposing the database to the Internet. There's very little value in doing that, especially since Heroku's IP addresses change regularly so you can't easily lock access down to your application. Best case scenario you'll have a publicly available database only accessible over SSL (exactly what Heroku and other providers can offer) that you'll have to administer yourself.

Outgoing connections are relatively easy, e.g. if you wanted to connect a web service running on your local network to a database in the cloud, but I don't think that helps you.

¹This is a Good Thing™ since it provides a layer of protection against direct attacks on your personal devices. Wouldn't it be awful if your machine got hacked every time you waited a few days to install updates on Windows?

²An example would be to set up port forwarding on your network's public IP address, say 123.123.123.123, such that requests to 123.123.123.123:1234 are routed to a specific IP address and port on your internal network, for example 192.168.1.10:5432.