As part of your code, you may be inclined to call a command to do something. But is it always a good idea? How to do it safely? What happens behind the scenes?
You’ve just written a great Python web application. Now, you want to share it with the world. In order to do that, you need a server, and some software to do that for you.
The following is a comprehensive guide on how to accomplish that, on multiple Linux-based operating systems, using nginx and uWSGI Emperor. It doesn’t force you to use any specific web framework — Flask, Django, Pyramid, Bottle will all work. Written for Ubuntu, Debian, Fedora, CentOS 7 and Arch Linux (should be helpful for other systems, too). Now with an Ansible Playbook.
Revision 7c (2020-05-01): works with Ubuntu 20.04 and Fedora 32; previous Revision 7a (2020-02-03): Move virtual environment to separate venv folder to improve Python upgrades (venvs should be ephemeral); add Docker section
pass is the standard Unix password manager. And I just wrote a slightly friendlier, clickier interface with urwid and Python.
Are you executing a process that takes a long time? Do you want to know that it’s still working while you are in another terminal/making coffee? Do you have a favorite game show tune to play while doing something?
think is just for you. For more details, read on or hop onto the GitHub page.
I recently switched distros on my server, from Debian to Fedora, to use
systemd and keep it in line with my home Arch Linux system (which was
not reinstalled since 2010, by the way!) Why is systemd so awesome? Read
on to find out.
What’s the most important non-kernel piece of software in UNIX-like OSes? The shell. A good shell.