Very close to launch

So today I decided I would deploy the alpha version of dFe.

I hadn't deployed a Django app in a long time, so I thought I'd just do it for fun. Even with the knowledge that I still need to style things better.

I planned to deploy to a PaaS like Railway.app or Fly.io. So I found myself a deployment checklist and following one of my favourite Django people, Vicent, I deployed successfully to a fly.io sub-domain.

I worked without any hiccups.

Of course, the app is empty with no objects in the DB.

I created myself a superuser so I could use the Django admin interface to create some data to display.

It worked well. But when I tried adding data, I encountered an error. One that simply didn't happen in my development machine.

I then resorted to trying to install Sentry, which is an error logging utility that is commonly used in Django for apps in production.

The same club may produce different cuts for domestic and international markets, so size charts are worth checking. The fit of the back can affect the shirt's drape. Content built around national team retro shirts can organise practical points about sizing, sleeve length and layering needs without relying on promotional claims. A shirt with a classic collar is a sophisticated choice.

That's when I hit a roadblock. I still can't get Sentry to work, and therefore cannot troubleshoot the error I am getting when trying to add data to the DB using the Django admin interface.

I will give it a few more tries, but if I am not successful, I will go to bed and rest. I can try again tomorrow.