Setting your static and media urls for your django project on a shared server is simple. Make it habit to be one of the first things you do as you start a new project. All the examples in this project are for django version 2.x.
So you have built a Django site, the client is happy and you put it in production mode in the wild. But what if there are errors in cases that you could not even have imagined? How do you make sure you know what errors that users are experiencing? At the very least you should enable logging, with email alerts being sent for any ERROR or CRITICAL level errors. This is probably acceptable for a low traffic site. I would however reccomend using Sentry with thier powerful Djando intergration. In this tutorial, we will look at how easy it is to intergrate a free Sentry account with our project, and as a bonus, set up some custom error pages that also send logs to Sentry and even have an optional feedback form.
Getting the static files to display correctly when hosting your django site on a shared server is quick and easy in a few steps.
I will start by stating, this is probably not the best practice, but it is really convenient to be able to connect to and edit you live site using Atom on your machine. It certainly beats shelling in and editing with an editor like Vim or trying to use the cPanel file manager to find and edit files.
In a previous article, I showed how to easily deploy django on a shared server. Shared servers also provide a options of database servers that you can use for your project.