Code server failure, PostHog issues, fix needed, demo prep.

Very low on time, I'll make it short.

Yesterday I reached out to the interested user to see if they had a chance to try it and liked it. I was today informed the code-server is showing 502. I'm horrified as I realize it hasn't worked for days!!! This is why nobody has started a tutorial, because it didn't work!! I missed this because my container was already running, and PostHog sessions don't capture iframes!

The reason was probably in the way I track available ports for the containers. When I restarted the orchestrator, the available ports also restarted, but the docker containers were still running. So when it tried to create new containers for new users, it was trying to use existing ports. I don't see the full error because my logging is terrible. For a temporary measure, I have destroyed the existing containers, but I will need to figure out a smarter way to handle this.

The takeaway from this is that I need to fix my logging. make it structured, add an automated test to make sure this shit doesn't happen again, and maybe set up an alert system, so I can fix these issues much earlier. I will probably try and do that over the weekend when I have more time.

I got feedback from my coworker that I should set up a usable demo that doesn't require logging in. My previous observations confirm this, most people bounce when presented with a login screen.

Data wise, 7 new sessions, 1 new user, nothing interesting.

PostHog just stopped working on the diary 3 days ago when I deployed it and I can't figure out. I tried recreating the key and redeploying, but no luck.

I figured it out. I added a next.config.js, which I guess invalidated everything inside next.config.mjs (icnluding the posthog rewrites). However, while trying to figure it out, I tried updating to NextJS 15, and now everything is fucked and I can't even build the project.

Okay, I've finally got it to work. I can now track the diary as well. I hope I can spend time more meaningfully in the following days.

Next steps:

• set up the weekly and daily posting to X and LinkedIn
• set up the PostHog funnel so I can track my progress more easily
• fix the port assignment
• allow a non authorized demo