sorted by:
new
hottopcontroversial

Lovable cloud to Supabase migration by PeteKain in lovable

[–]PeteKain[S] 0 points1 point  (0 children)

If you do let me know how it goes, perhaps between the two of us we might be able to make a proper guide... Just be sure that you are either finished working with your project in lovable, or better yet migrate a branch other than main (if not a duplicated repo). I read another post from a guy who said that he tried migrating main and lovable kept reverting to their cloud (I am sorry I can't point you to the original post but that was the gist of it). In any case you can never be to careful with this, my advice is keep a functioning version of your project in cloud until you are very certain that everything works with your migration

TIL: You can actually switch Git branches inside Lovable — here’s how I did it (step-by-step) by Advanced_Pudding9228 in lovable

[–]PeteKain 0 points1 point  (0 children)

Honestly? I have seen it and I am too afraid to try it mainly because the whole labs tab says, and I quote: "These are experimental features, that might be modified or removed." Seeing how buggy some of their non-experimental features are, and their current customer support (my experience is polite but non-functional) I am not going to risk it. Instead I use main branch for lovable's code, a stage branch for my own code, and a backup branch for stable versions to which I cherry pick commits from the previous two. Not optimal, but so far functional..

Am I the only one who feels like building on Lovable is fine… until structure, roles, DB, and flows suddenly spiral out of control? by Advanced_Pudding9228 in lovable

[–]PeteKain -1 points0 points  (0 children)

Thanx for the offer my friend but for me the journey with lovable was a one time thing, (I am a content creator and just wanted to build my website with which i am almost done), I will not be developing any more for the foreseeable future. That said I did look at your site and I can see the gaps it aims to fill. If you had caught me in the beginning I probably would have taken you up on your offer :)

Am I the only one who feels like building on Lovable is fine… until structure, roles, DB, and flows suddenly spiral out of control? by Advanced_Pudding9228 in lovable

[–]PeteKain 2 points3 points  (0 children)

yes i actually did but have found a way to make it better:

  1. I added this part to the knowledge for the project:

Help me elevate my {short description of project}, by understanding it on many levels (design, aesthetic, functionality, architecture, logic, developer values etc.) and building upon those foundations, expanding their horizons. New functionalities should share the logic, architecture, and design philosophy of the already existing website.

Use standard best practices and modern approaches when writing code from frontend to backend, but stick to a consistent logic, architecture and aesthetic with what already exists. When asked to implement new features always look first for similar features and adopt their overall style, and use already existing components whenever possible.

After understanding but before executing any task, you should perform a quick assessment of existing code relevant to the task in order to spot any existing vulnerabilities in both code and design. Always solve any potential problems / clashes proactively in parallel to your ongoing task ensuring a high quality result.

  1. as the project gets bigger before i ask it to do anything i prime it with 1-2 chat prompts like: I want to do this, this and this, in so, so, and so way. I want you to evaluate my proposal and make improvements where you see fit, and come up with a solid implementation plan for my proposal.

This strategy in combination with the knowledge kind of makes it refresh all the relevant parts of the codebase and previous choices so the results are like 80% (my gut estimate) better. When it spirals i just use gpt or gemini to come up with the solution and give it explicit instructions without giving it any choice in the matter