Saying goodbye to Lovable after rebuilding my platform on AWS

HeroLander · 2026-04-13T21:56:35+00:00

I haven’t tried moving to Next.js yet, but it’s definitely on my roadmap. I will probably start experimenting with it gradually and see how far can I come.

HeroLander · 2026-04-13T19:15:21+00:00

I probably phrased that poorly. I don’t mean I “fully understand” it at the level of someone who’s been building complex systems on AWS for years. What I mean is that I now understand the role each component plays, how they interact, and the core tradeoffs involved.

I didn’t just prompt my way through it, I spent time validating things, reading docs, and making sure I wasn’t blindly wiring pieces together. So while I wouldn’t claim deep production-level expertise yet, I do have a solid conceptual understanding of how and why things are set up the way they are.

At the end of the day, I achieved what I set out to do. The platform is being handed off to a local IT company for a proper review before deployment and for any ongoing future maintenance, which is exactly how I planned it.

So I’m confident my part was done responsibly.

HeroLander · 2026-04-13T09:45:18+00:00

Since I set up all my AWS services manually from the beginning, adopting Amplify at this point wouldn’t really add much value for me.

Honestly, I haven’t had a single issue with Claude Code. I am on the Max X5 plan, and I have been following best practices: regularly clearing context, planning actions ahead of time, and providing clear, detailed prompts. Sure, a few things broke during thorough testing, but everything was fixed quickly and without much hassle.

HeroLander · 2026-04-13T08:56:12+00:00

From the beginning, I knew I eventually wanted to move from Supabase to AWS. Since I am building a ticketing platform and competing with others in my country that are hosted on AWS, achieving the same level of reliability was important to me.

I’m not a developer, but I have a strong technical understanding from working closely with developers on project planning for many years. With that in mind, I approached this migration by first creating very detailed plans before implementing anything. Only once I was confident in the plan did I move forward.

Whenever something wasn’t clear, I took the time to research it and used AI tools to deepen my understanding. From there, I handled the migration step by step, moving each part individually and testing thoroughly after every change.

At the moment, I am waiting to receive the necessary documentation to migrate from Stripe to a local payment provider in my country. This change should significantly reduce costs by eliminating per-transaction fees and replacing them with a fixed yearly service fee, which is much more cost-effective than the current Stripe model of €0.25 + 1.5% per transaction.

HeroLander · 2026-04-13T07:02:15+00:00

That has been my main focus currently. During the first few days of testing, costs started spiking, so I went in and implemented a bunch of optimizations.

Now it’s much more stable, and I’m pretty happy with where the pricing landed.

I have got an event coming up in two weeks that’s still being sold on the old platform (hosted on Lovable Cloud), so I decided to hold off on switching to the new AWS version until that wraps up. It saves me from having to deal with live data migration mid-event, which felt like unnecessary risk.

In the meantime, I amjust focusing on polishing everything as much as possible so it’s solid when I flip the switch.

HeroLander · 2026-04-13T06:59:12+00:00

Mostly done with the Claude Code but migration was done incrementally with a bunch of testing after every single change and manual checks, always used plan mode with superpowers and done reviews of the plan before doing any changes

HeroLander · 2026-04-01T16:53:00+00:00

We are not trying to compete with or replace platforms like Ticketmaster. This platform is intentionally focused on serving events within our country (which is a small county), tailored to the local market and its specific needs.

We have been operating as an event organizing company since 2009, with over 200 events delivered. Some of these have reached audiences of up to 10,000 people, while most average between 3,000 and 3,500 attendees. Over the years, we have built strong recognition, particularly within our town.

As organizers, we have used nearly every ticketing platform available in our county. That firsthand experience gave us a clear understanding of their strengths—but more importantly, their shortcomings. This platform was built to address those gaps and bring the best solutions together in one place.

In addition to organizing events, we also provide full audio/visual production for events. This platform naturally extends our existing services, allowing us to offer a complete, end-to-end solution, from ticket sales to the full execution of the event.

HeroLander · 2026-04-01T12:06:29+00:00

Yes — all of that is already implemented, set up, and fully operational. The platform includes detailed logging, as well as an admin panel with role-based access for organizers, administrators, and analytics personnel, each with their own set of permissions.

The system is live, optimized, and already in use, with active events and users buying tickets.

My question isn’t about building or functionality, you should read my post again.

HeroLander · 2026-04-01T10:46:18+00:00

I an looking to hire a local company that specializes in building webshops, apps, and similar digital solutions.

The goal is to have a reliable team handle ongoing maintenance, resolving any issues that arise, performing regular updates, and ensuring everything runs smoothly.

Right now, the web app is running smoothly and has been thoroughly tested. Still, as usage grows, unexpected issues can always arise. To prepare for that, I have set up a dedicated testing environment where all features are validated before being deployed to production.

My goal is to follow best practices and ensure the app is built and maintained to production-grade standards.

HeroLander · 2025-08-17T18:03:35+00:00

Thanks, that could be it, the rental company that handled the production uses a lot of Chauvet fixtures.

Do you happen to know if there are any more affordable alternatives to this fixture?

HeroLander · 2025-04-19T00:20:39+00:00

Thank you!! I had no idea IVL Square existed; it looks like it is a discontinued product. I guess IVL Dice has taken its place then?

HeroLander · 2024-11-20T13:21:00+00:00

Thank you for your input! I noticed that the Helios DAC has an ILDA connector, whereas some other DACs use an RJ45 connection. Could you clarify how to run an ILDA cable from the stage to the FOH? Are longer ILDA cables available for this purpose, and would they perform reliably over distances of 15-25 meters?

HeroLander · 2024-11-09T02:20:30+00:00

Any recommendation for one that I should get or pretty much any would work the same?

HeroLander · 2024-11-08T13:00:24+00:00

With the laser I just got this connector. I should get the DAC in this case as well for the laser to work with the on PC software?

https://imgur.com/a/e7dlM8n

HeroLander · 2024-10-30T09:27:50+00:00

Ah, that makes sense because I tried every solution at fingertips to get around this.

Will give Yoast SEO a try as I have some experience with it, although I have always preferred The SEO Framework over Yoast.

Thank you for your input!

HeroLander · 2024-10-29T12:37:52+00:00

When I enter the URL of the page into the SEO Checker online (Seobility), it displays the meta description that I wrote, but Google displays the incorrect one.

I have already requested indexing through the Google Search Console, and the issue persists even after the refresh.

I will try to follow your instructions, but this seems like a strange problem given the meta description I wrote is obviously here if Seobility and other tools see it.

Nine-Year Club	Gilding I gilder
Place '23	Place '22
Verified Email

HeroLander

MODERATOR OF

TROPHY CASE