Mobile site fix, infra improvements needed, bug fixes.

I have little time todays so I'll use it to do some light work.

Just ran across this post on LinkedIn: https://www.linkedin.com/posts/farzanmaghami_startuplife-buildinginpublic-saas-activity-7276833600627482624-4Xrn?utm_source=share&utm_medium=member_desktop

It got me thinking about my website's mobile experience. I will definitely need to get that sorted out because most people are probably going to open the site on mobile first, and only then decide if it's worth opening on their PC. Ideally, it should be able to sell them on the idea without them ever running the editor themselves.

I just tried going through the course in production, and it fails with 500 when i run step 3.3

I also noticed the run-cmd request is being made twice when submit is clicked.

I've figured out why the request was returning 500. It's because I've made errors return 200, but haven't yet pushed or redeployed that new container version. This shows a clear need for a better release process when it comes to user containers. I need to be able to push them automatically, as well as force container updates when a new version is released.

I also noticed the failed tests arent nicely displayed, but raw output is displayed instead.

So, just to keep in mind, once I have some time for more infra work:

• migrate to hetzner
• improve logging
  • make go logs structured
  • make nginx logs structured and in the same format as go logs
• add loki/grafana?
• set up alerting?

Not now though, as there are more important things to do.

I added the confetti on successful submit. Looks pretty nice, I think.

Today I worked for an hour in the morning, and 30 minutes before bed. More than I thought I would.

1h @ 13:15