Neat_Structure8780

https://preview.redd.it/d7f60wzp87pg1.png?width=3004&format=png&auto=webp&s=1fc3d7c1ba9f54f3681380fa04fab1bb43502239

We've been building a marketplace from scratch… with a simple goal, get people to support great causes while reducing their fashion waste. Without jumping from a Vinted or Depop to a JustGiving.

What’s been wild is that it’s already picking up with students and other UK adults around Newcastle (where we've launched). People are listing clothes and other stuff — basically all the things you would like to re-home but still make a few pounds off them.

The idea is simple: you sell your stuff, keep the part of the money, and you put a portion towards a charity if you want.

Hone

Hello everyone, we've been build a marketplace from scratch… with a simple goal, get people to support great causes while reducing their fashion waste.

What’s been wild is that it’s already picking up with students around Newcastle. People are listing clothes, random tech, kitchen stuff — basically all the things you accumulate at uni and then don’t want to drag home.

The idea is simple: you sell your stuff, keep the part of the money, and you put a portion towards a charity if you want.

Honestly I expected tumbleweed for weeks, so Newcastle students signing up and

seeing actual listings that support local charities is a bit surreal.

If you’re a student in Newcastle and planning a cl

If Replit doesn't solve this production deployment issue rapidly, Lovable will eat their customers for Breakfast, lunch and dinner.

I'm battling again with the agent being absolutely incapable of handling a clean deployment without breaking something.

It either just wipe out my production admin credentials or default my admin account to a regular level access.

The worst, it keeps enthusiastically claiming that it has fixed the issue. Only to come back saying, " I apologise for wasting your time, I was making the changes to our dev environment."

I would have thought that a deployment protocol is a simple thing to put in place and that the Agent and Replit would handle it easily.

That's n

Today drama...Stripe integration.

I've been struggling to get the Agent to build a functioning checkout with Stripe.

I gave it every single info that it asked : Stripe publishable + secret keys + Webhooks etc.

Still.

Every time it tries to build it, it comes back with the checkout page missing the payment processing section fields.

I've ran out of imagination to solve this problem.

And I feel like it is the most crucial Knowledge Gap for this project.

Has anyone managed to fill that Knowledge Gap?

Let me know how you made it work.

Today drama...Stripe integration.

I've been struggling to get the Agent to build a functioning checkout with Stripe.

I gave it every single info that it asked : Stripe publishable + secret keys + Webhooks etc.

Still.

Every time it tries to build it, it comes back with the checkout page missing the payment processing section fields.

I've ran out of imagination to solve this problem.

And I feel like it is the most crucial Knowledge Gap for this project.

Has anyone managed to fill that Knowledge Gap?

Let me know how you made it work.

Today drama...Stripe integration.

I've been struggling to get the Agent to build a functioning checkout with Stripe.

I gave it every single info that it asked : Stripe publishable + secret keys + Webhooks etc.

Still.

Every time it tries to build it, it comes back with the checkout page missing the payment processing section fields.

I've ran out of imagination to solve this problem.

And I feel like it is the most crucial Knowledge Gap for this project.

Has anyone managed to fill that Knowledge Gap?

Let me know how you made it work.

He we go again.

Woke up this morning and it all fell apart again. After confirming with the Agent that we've successfully separated the databases and set up different URLs, it had a refresh overnight and undone everything.

Now my admin user account has lost it's credentials. Production users are wiped out and all passwords gone.

spent the day going back and forth to sort it out. Rollback after Rollback.

I suspect Replit has set things that way and that unless I migrate the code somewhere else and start using a different Agent, I'm stuck in that data destroying loop.

The worst thing is that the agent keep pushing checkpoints where they are not even needed. (Replit money making mac

A Tale of Two Databases. How to prevent Replit deployment from wiping your production data out.

Or when the Agent doesn't know what you don't Know.

Folks, I finally got a grip on my production data getting wiped out every time I deploy.

Remember my Agent Drama about data being wiped out.

Well it turns out every environment and database isolation we put in place was destined to fail.

Why?

Simple put. I was asking the agent to isolate things that weren't isolatable. (If that's even a word).

All this time, we had a single database. and it was used for prod. So when the agant needed something to run the code on, it didn't have any other choice but to assalt our single database. (A

Here to document my Vibe Coding journey using Replit AI Agent.

So today I had to Rollback from two days ago just to get the Agent out of a coding loop. That's two days worth of my non-dev vibe coding doing the drain.

But the good thing is that I feel like the Agent is learning a bit better how to behave.

I've establish a clear prompt routine where I systematically ask it to explain to me what he understand from my request.

And some times he didn't get it. Meaning " I " as a non-dev didn't use a language precise enough to get it to do what I intended.

But now it's done. This gives me a second shot at fine tuning my prompt depending on what the Agent says it understood from my reques

Has anyone managed to crack the Replit data and schema destruction nightmare? Also the Dev / Prod environment separation? I've been using Replit as a non-coder and so far it's been a real nightmare. You'd spend hours working on an aspect of the project and once you deployed, it either wipes out exisiting production data or breaks previously working functions even though you explicitly integrate Protection wrappers around those function.

The Agent also has a enraging habit of self validating its work. Claiming it fixed stuff when it actually didn't.

Anyone facing the same issues? How did you resolved them?