I read you migrated to an S3-based git backend — would love to hear more about that story and how you managed the migration. Did you migrate all repos at once or on demand?
Also chapeau for the quick turnaround, I logged into lovable and saw the incident and you didn't let GitHub slow you down :-)
regardless of scale there will most likely be code paths where performance is not prioritized, and unexpected use-cases can put the stability at risk. In this case that was creating new repos. I believe if we only made a crazy amount of commits there would have been no issue.
Founder here:
Not part of the report was that getting intro to people on Github significantly helped accelerate things.
Any questions about Lovable infra for those curious generally – happy to answer.
(also, we're hiring senior platform engineers in Europe to build the first European AI outlier success story:)
I read you migrated to an S3-based git backend — would love to hear more about that story and how you managed the migration. Did you migrate all repos at once or on demand?
Also chapeau for the quick turnaround, I logged into lovable and saw the incident and you didn't let GitHub slow you down :-)
regardless of scale there will most likely be code paths where performance is not prioritized, and unexpected use-cases can put the stability at risk. In this case that was creating new repos. I believe if we only made a crazy amount of commits there would have been no issue.
Very happy this was fixed, I was just about to ship an update to my Lovable app when this happened..
heard many that were just about to demo lovable apps when this happened..
Kudos to the dev team for being so quick
that's one way to wake up the team after New Year's eve
Kicking off 2025 with the Lovable Support Team