u/DrChhabra26

Every tutorial of OpenClaw is saw, mentioned that, use a VPS to run OpenClaw, this is advised so OpenClaw cannot access your sensitive files present in your local system.
So while watching tutorial, it was more sounding like ad for VPS tools like Hostinger rather than a tutorial video.

So instead, just to get hands dirty on OpenClaw, I tried it on a virtual machine (ubuntu on my mac).. i know this won't work if the system is shut down... but i did this just to get started with OpenClaw for free as I don't want to pay for any VPS that time...
Now if I want to try running OpenClaw with Ollama this time, but on my actual local host machine, will that also be a safe option.

I have been using lovable, for like a month now, and created a full-fledged application from this.
I used lovable cloud as a backend service for my dev environment... but wanted to have a dedicated supabase projects for stage and prod environment... for this i decided to migrate the schema from lovable cloud to stage and prod supabase environment, via github actions (ci/cd)...
For CD workflow to gets executed (where entire database schema is migrated to stage and prod), first a CI workflow needs to be successful. In this CI workflow, I added basic migration validation, that validates the migration file created by lovable cloud, before it gets pushed to prod.

Below are the challenges that I faced and the problem that, I observed, have with Lovable:

1. Migration Issue:
   1.1 - In normal development, we create the table once and keep updating the schema according to requirements, and migration files that are created, builds on previous one i.e. CREATE DDL command will only be in first initial migration file and later migration file will have ALTER, DROP etc. commands (no CREATE). But what lovable does is, it always creates a migration file with CREATE DDL command, and sometime these are not guarded by 'IF NOT EXISTS', because of which the CD workflow keeps getting failed when validation migration step is getting executed.
   1.2 - Lovable also mixes migration files with seed files.. because of which some cases arrive which causes foreign key constraint error like for e.g. there are two tables TableA and TableB, there is a column in TableB, which is a foreign key and maps to one of the column of TableA... now lovable create the seed file in such order that it INSERT the data in TableB but on it TableA.. which causes foreign key constraints error.
2. Environment Variable Challenges: Lovable dashboard doesn't also support the adding of environment variables (unlike Vercel). Lovable only has feature to add secret values (that is used by backend service) and no environment variables (like starting with VITE_* or NEXT_*) can be added to those secret section. Because of which lovable dev tool rely on .env file for these values and these are even getting pushed to github. Though they are the public values.. but still it is not a good practice to keep pushing .env to github.

Does do you keep facing these challenges while working with lovable?
Is there a workaround for this in lovable itself? Or to overcome this.. we need to move out of lovable only?

Happy to have a discussion on this !!