#lovable — Public Fediverse posts

أطلقت منصة Lovable ميزة صفحات مركز الثقة التلقائية لكل تطبيق أعمال يتم نشره، مما يتيح للمستخدمين والمراجعين رؤية ضوابط الأمان الحية عبر رابط مخصص. تتضمن هذه الصفحات تقارير فورية مؤتمتة حول فرض بروتوكول HTTPS، وشهادات TLS، وفحص ثغرات التبعيات، وغيرها من ميزات الأمان المتقدمة. يتم إدارة محتوى مركز الثقة بالكامل بواسطة Lovable لضمان الدقة ومنع التعديل اليدوي، مما يعزز الموثوقية والشفافية التقنية لكافة التطبيقات المطورة عبر المنصة بشكل احترافي ومستمر.

#Lovable #Security

#Lovable, a #vibecoding #startup, confirmed a $13.3 billion valuation after raising $400 million in a Series C round led by Menlo Ventures and the Scaleup Europe Fund. The funding follows Lovable’s $500 million annualised run rate revenue and its growing backend needs, including its own AI model and a partnership with Google Cloud. https://techcrunch.com/2026/08/12/lovable-confirms-new-13-3b-valuation-raises-another-400m/?eicker.news #tech #news #ainews

#Lovable, a #vibecoding #startup, confirmed a $13.3 billion valuation after raising $400 million in a Series C round led by Menlo Ventures and the Scaleup Europe Fund. The funding follows Lovable’s $500 million annualised run rate revenue and its growing backend needs, including its own AI model and a partnership with Google Cloud. https://techcrunch.com/2026/08/12/lovable-confirms-new-13-3b-valuation-raises-another-400m/?eicker.news #tech #news #ainews

In zwei Tagen von der Startup-Idee zur KI-Implementierung? Mit Miro AI + Lovable geht’s sogar ohne Coding/Prompting. Wir zeigen eine App aus dem HWZ-Seminar „KI für Startup“: Value Story Builder für kundenspezifische Wertangebote. Neugierig? https://valuearticulation.lovable.app/ #KI #Startup #Miro #Lovable #NoCode #Prototyping
https://www.datentreiber.com/blog/ki-fur-startup/

In zwei Tagen von der Startup-Idee zur KI-Implementierung? Mit Miro AI + Lovable geht’s sogar ohne Coding/Prompting. Wir zeigen eine App aus dem HWZ-Seminar „KI für Startup“: Value Story Builder für kundenspezifische Wertangebote. Neugierig? https://valuearticulation.lovable.app/ #KI #Startup #Miro #Lovable #NoCode #Prototyping
https://www.datentreiber.com/blog/ki-fur-startup/

It's refreshing to do something non-Microsoft for a change. Instead of using big & often dysfunctional stack like the Power Platform, I'm now also leveraging technology that has UX at its very core.

In fact, it's right there in the name: Lovable. ♥️

https://niiranenadvisory.com/im-now-a-lovable-solution-partner/

#Lovable #citizendevelopment #lowcode #appbuilder

It's refreshing to do something non-Microsoft for a change. Instead of using big & often dysfunctional stack like the Power Platform, I'm now also leveraging technology that has UX at its very core.

In fact, it's right there in the name: Lovable. ♥️

https://niiranenadvisory.com/im-now-a-lovable-solution-partner/

#Lovable #citizendevelopment #lowcode #appbuilder

AI как новая поверхность атаки: реальные инциденты, мошенничество и уязвимости агентной эпохи

AI-агенты становятся полезными ровно в тот момент, когда получают доступ к данным, инструментам, браузеру, репозиториям, почте и рабочему контексту. Но именно там AI превращается в новую поверхность атаки. В этой статье я разбираю не абстрактный “AI-хайп”, а реальные кейсы: дипфейк-кражу $25 млн у Arup, открытую ClickHouse-базу DeepSeek, отзыв токенов Hugging Face Spaces, фишинг через легитимные AI-workspace invites, сбой Replit-агента и исследования вроде EchoLeak и BioShocking. Главный вопрос не в том, “может ли модель взломать компанию”, а в том, какие права мы уже выдали AI-инструментам и что произойдёт, если недоверенный контент станет инструкцией для агента.

https://habr.com/ru/articles/1054618/

#ai #ai_agent #кибербезопасность #агент #llm #gpt #claude #lovable

"Copilot is the AI for work, period. For the optimists turning ideas into reality, there are better options."

That LI post from one AI director at Microsoft aligns well with how I see the role of of tools like Lovable that focus on doing one thing really well. Instead of trying to replace every experience with Copilot.

https://www.perspectives.plus/p/making-app-building-experience-lovable

#Copilot #Lovable

"Copilot is the AI for work, period. For the optimists turning ideas into reality, there are better options."

That LI post from one AI director at Microsoft aligns well with how I see the role of of tools like Lovable that focus on doing one thing really well. Instead of trying to replace every experience with Copilot.

https://www.perspectives.plus/p/making-app-building-experience-lovable

#Copilot #Lovable

Even if your docs are stored in SharePoint, the UX for browsing them doesn't have to be terrible. In fact, it can even be Lovable.💓

https://www.youtube.com/watch?v=q2MP8BIhMuc

I tested the #SharePoint connector in #Lovable and had pretty amazing app ready in 15 minutes. Something I could not have achieved with Microsoft's own AI app generator tools or Power Apps.

#vibecoding #Microsoft365

Even if your docs are stored in SharePoint, the UX for browsing them doesn't have to be terrible. In fact, it can even be Lovable.💓

https://www.youtube.com/watch?v=q2MP8BIhMuc

I tested the #SharePoint connector in #Lovable and had pretty amazing app ready in 15 minutes. Something I could not have achieved with Microsoft's own AI app generator tools or Power Apps.

#vibecoding #Microsoft365

#Design #Analyses
Did Lovable’s AI build a 100% accessible site? · When AI sites improve with human accessibility expertise https://ilo.im/16cwfe

_____
#Lovable #AI #Website #Accessibility #ScreenReader #UiDesign #WebDesign #Development #WebDev #Frontend

#Design #Analyses
Did Lovable’s AI build a 100% accessible site? · When AI sites improve with human accessibility expertise https://ilo.im/16cwfe

_____
#Lovable #AI #Website #Accessibility #ScreenReader #UiDesign #WebDesign #Development #WebDev #Frontend

Migrating from Lovable: Steps to Self-Host Your App

Lovable is a remarkable product.
You describe what you want. It builds it. You ship in hours instead of weeks.
That’s genuinely impressive, and I’ve used it to launch things I would have otherwise shelved for “when I have more time.”

But “when I have more time” eventually arrives.

And when it does, you start asking different questions:

“What happens if they change pricing?”
“Can I run this on my own infrastructure?”
“Where exactly does my data live?”

Those aren’t paranoid questions. They’re the right questions.
This post is about answering them — practically, with actual steps you can follow.

Why Leave Lovable?

Before anything else: you might not need to.

Lovable is a solid platform. If your app is a side project, an internal tool, or an early-stage product with low traffic, staying there is probably the right call. The cost of self-hosting is real — you own the ops now.

But there are situations where moving makes clear sense:

Cost at scale
Lovable’s pricing is per-project and per-usage.
Once you’re past early stage, running your own stack on a VPS or cloud provider is often ~3–5x (or more) cheaper.

Data residency
Some industries (healthcare, finance, defense) require you to control where data lives.
“It’s on Lovable’s servers” isn’t an acceptable answer in those conversations.

Customization ceiling
Lovable generates clean React/Supabase apps, but it has opinions. When you need a specific architecture, edge functions, a custom auth flow, or native mobile builds outside their defaults — you hit the wall.

Ownership
At some point, the code is yours.
You should be able to run it. Anywhere.

What You’re Actually Working With

Lovable generates a specific stack.
Understanding it before you touch anything is important.

A typical Lovable export looks like this:

• Frontend: React (Vite), TypeScript, Tailwind CSS, shadcn/ui components
• Backend/DB: Supabase (Postgres, Auth, Storage, Edge Functions)
• Routing: React Router
• State/Fetching: TanStack Query, sometimes Zustand
• Deployment: Previously Lovable’s own hosting; they now push to GitHub and can connect to Netlify/Vercel

The code is real – It’s readable. There’s no magic proprietary runtime you need to reverse-engineer.
That’s the good news.

The less-good news:
Supabase is tightly integrated.
The app talks to a Supabase project by project URL and anon key. If you want to move away from Supabase (or self-host Supabase), that’s a bigger migration than just moving the frontend.

For most people: keep Supabase, move the frontend.
That’s the path of least resistance.

Step 1: Export Your Code

First things first.

Go to your Lovable project → click the GitHub button → connect your GitHub account → push the project.

You now have a real repository with real code. Clone it locally:

 git clone https://github.com/your-username/your-lovable-project.git  cd your-lovable-project  npm install 

Before you do anything else, make sure it runs locally:

 npm run dev 

If it opens in your browser and works: great. If it doesn’t: check your .env file (more on that in a moment).

Step 2: Understand Your Environment Variables

This is where most people get stuck.
Lovable injects environment variables automatically. When you run this yourself, you’re responsible for them.

Create a .env file in your project root:

 VITE_SUPABASE_URL=https://your-project-ref.supabase.co  VITE_SUPABASE_ANON_KEY=your-anon-key-here 

Find these in your Supabase dashboard → Project Settings → API.

One important thing: never commit your .env to git. Add it to .gitignore immediately if it isn’t already there.

 echo ".env" >> .gitignore 

For production deployments, you’ll set these as environment variables in your hosting provider’s dashboard — not as files checked into the repo.

Step 3: Build for Production

 npm run build 

This generates a dist/ folder. Everything in there is static — HTML, CSS, JavaScript bundles. No Node.js server required to serve it.

You can host this on:

• Vercel (easiest, free tier is generous)
• Netlify (similar to Vercel, excellent DX)
• Cloudflare Pages (fastest globally, very generous free tier)
• A plain VPS with Nginx (most control, most work)

My default recommendation:
1. Cloudflare Pages for public-facing apps
2. VPS + Nginx if you want full control and have ops comfort.

Step 4: Deploy to Cloudflare Pages (Recommended)

If you just want it running fast with zero infrastructure overhead:

1. Push your repo to GitHub (done in Step 1)
2. Go to Cloudflare Pages → Create Project → Connect GitHub
3. Select your repo
4. Set build settings:

• Build command: npm run build
• Build output directory: dist

1. Add your environment variables (VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY)
2. Deploy

Done.

Your app is live on a Cloudflare CDN edge network in ~2 minutes, with automatic deployments on every push to main.

Step 5: Deploy to a VPS (The “Real Self-Hosting” Path)

For maximum control, run it on your own server.
I recommend fly.io (so you don’t need to install/maintain anything – just build your webapp in docker) or Hetzner — the value is absurd compared to AWS or GCP for basic hosting needs.

Provision your server, then SSH in:

 ssh root@your-server-ip 

Install Nginx:

 apt update && apt install nginx -y 

Create your site directory and copy the build:

 mkdir -p /var/www/myapp  # From your local machine:  scp -r dist/* root@your-server-ip:/var/www/myapp/ 

Or better: set up a CI/CD pipeline that does this automatically on push.

Configure Nginx:

 server {      listen 80;      server_name yourdomain.com;      root /var/www/myapp;      index index.html;       # This is critical for React Router — all paths serve index.html      location / {          try_files $uri $uri/ /index.html;      }       # Cache static assets aggressively      location ~* \.(js|css|png|jpg|jpeg|gif|ico|svg|woff2)$ {          expires 1y;          add_header Cache-Control "public, immutable";      }  } 

Save to /etc/nginx/sites-available/myapp, symlink it:

 ln -s /etc/nginx/sites-available/myapp /etc/nginx/sites-enabled/  nginx -t && systemctl reload nginx 

Add HTTPS with Let’s Encrypt:

 apt install certbot python3-certbot-nginx -y  certbot --nginx -d yourdomain.com 

Certbot auto-renews.
You’re done.

Step 6: The Native App Situation

If your Lovable app has a native mobile wrapper — this is where things get interesting.

Lovable has been expanding into native capabilities using Capacitor under the hood. If your project has native bindings, you’ll find a capacitor.config.ts in the project root.

The good news:
Capacitor is open-source and you own the workflow entirely.

For iOS:

 npm run build  npx cap sync ios  npx cap open ios 

This opens Xcode with your project. From there, you archive and submit to the App Store exactly like any other iOS app. You need an Apple Developer account ($99/year).

For Android:

 npm run build  npx cap sync android  npx cap open android 

This opens Android Studio. Build → Generate Signed Bundle/APK → distribute via Play Store or sideload directly.

The webview URL matters.

In development, Capacitor talks to localhost. In production, you need to point it at your live web app. Edit capacitor.config.ts:

 import { CapacitorConfig } from '@capacitor/cli';   const config: CapacitorConfig = {    appId: 'com.yourcompany.yourapp',    appName: 'Your App',    webDir: 'dist',    server: {      // Remove this for production — use bundled assets instead      // url: 'http://localhost:5173',      androidScheme: 'https'    }  };   export default config; 

For most native apps, you want the webDir approach — the built assets are bundled directly into the native app binary. This means offline support works and you don’t depend on your web server being up for the app to function.

Run npx cap sync after every build to keep the native project in sync with your web build.

Step 7: Handling Supabase at Scale

You moved the frontend. Supabase is still doing the backend work.

For most apps: that’s fine. Supabase is genuinely good infrastructure.

But if you want to self-host Supabase too (for compliance, cost, or curiosity), they publish an official Docker Compose setup:

 git clone --depth 1 https://github.com/supabase/supabase  cd supabase/docker  cp .env.example .env  # Edit .env with your secrets  docker compose up -d 

This runs the full Supabase stack — Postgres, GoTrue (auth), PostgREST, Realtime, Storage, and Studio — on your own hardware.

It’s more maintenance burden. But it’s also complete ownership.

My honest take: use Supabase managed unless you have a specific reason not to.
Their managed infrastructure is well-run and the pricing is reasonable until you’re at serious scale.

Step 8: Setting Up CI/CD So You Don’t Do This Manually Again

Manually copying files to a server is how you get paged at 2am because you forgot a step.

Here’s a minimal GitHub Actions workflow that builds and deploys on every push to main:

 # .github/workflows/deploy.yml  name: Deploy   on:    push:      branches: [main]   jobs:    deploy:      runs-on: ubuntu-latest      steps:        - uses: actions/checkout@v6         - name: Setup Node          uses: actions/setup-node@v6          with:            node-version: '24'            cache: 'npm'         - name: Install & Build          run: |            npm ci            npm run build          env:            VITE_SUPABASE_URL: ${{ secrets.VITE_SUPABASE_URL }}            VITE_SUPABASE_ANON_KEY: ${{ secrets.VITE_SUPABASE_ANON_KEY }}         - name: Deploy to Server          uses: appleboy/[email protected]          with:            host: ${{ secrets.SERVER_HOST }}            username: ${{ secrets.SERVER_USER }}            key: ${{ secrets.SSH_PRIVATE_KEY }}            source: "dist/*"            target: "/var/www/myapp"            strip_components: 1 

Add your secrets in GitHub → Settings → Secrets and variables → Actions.

Push to main. It deploys automatically.
That’s the whole loop.

The Checklist Before You Pull the Plug on Lovable

Don’t cancel your Lovable plan until you’ve verified all of this:

• [ ] App runs locally with npm run dev
• [ ] Production build succeeds with npm run build
• [ ] All environment variables are set correctly in production
• [ ] Supabase Row Level Security policies are configured (don’t rely on Lovable having set these correctly)
• [ ] Auth flows work end-to-end (sign up, sign in, sign out, password reset)
• [ ] Any storage/file uploads work against your Supabase bucket policies
• [ ] Edge functions (if any) are deployed to Supabase
• [ ] Custom domain is pointing to your new hosting
• [ ] HTTPS is working
• [ ] Native builds open and run correctly (iOS Simulator + Android Emulator at minimum)
• [ ] CI/CD pipeline deploys successfully from a test push

Run through this list twice.
Yep… On the second time you’ll catch something you missed.

What I’ve Learned From Doing This

Lovable is excellent for getting to a working product quickly.
Self-hosting is excellent for owning what you built.

These aren’t in conflict — they’re a sequence.

Build fast on Lovable.
Validate the idea.
Get real users.
Then, when the infrastructure costs start mattering or the compliance questions start arriving, migrate.

The migration is maybe 4–6 hours of focused work for a typical app.
That’s worth doing on a quiet Sunday, not during a crisis.

Do it before you need to.

Questions? Find me on GitHub

Rate this:

Migrating from Lovable: Steps to Self-Host Your App

Lovable is a remarkable product.
You describe what you want. It builds it. You ship in hours instead of weeks.
That’s genuinely impressive, and I’ve used it to launch things I would have otherwise shelved for “when I have more time.”

But “when I have more time” eventually arrives.

And when it does, you start asking different questions:

“What happens if they change pricing?”
“Can I run this on my own infrastructure?”
“Where exactly does my data live?”

Those aren’t paranoid questions. They’re the right questions.
This post is about answering them — practically, with actual steps you can follow.

Why Leave Lovable?

Before anything else: you might not need to.

Lovable is a solid platform. If your app is a side project, an internal tool, or an early-stage product with low traffic, staying there is probably the right call. The cost of self-hosting is real — you own the ops now.

But there are situations where moving makes clear sense:

Cost at scale
Lovable’s pricing is per-project and per-usage.
Once you’re past early stage, running your own stack on a VPS or cloud provider is often ~3–5x (or more) cheaper.

Data residency
Some industries (healthcare, finance, defense) require you to control where data lives.
“It’s on Lovable’s servers” isn’t an acceptable answer in those conversations.

Customization ceiling
Lovable generates clean React/Supabase apps, but it has opinions. When you need a specific architecture, edge functions, a custom auth flow, or native mobile builds outside their defaults — you hit the wall.

Ownership
At some point, the code is yours.
You should be able to run it. Anywhere.

What You’re Actually Working With

Lovable generates a specific stack.
Understanding it before you touch anything is important.

A typical Lovable export looks like this:

• Frontend: React (Vite), TypeScript, Tailwind CSS, shadcn/ui components
• Backend/DB: Supabase (Postgres, Auth, Storage, Edge Functions)
• Routing: React Router
• State/Fetching: TanStack Query, sometimes Zustand
• Deployment: Previously Lovable’s own hosting; they now push to GitHub and can connect to Netlify/Vercel

The code is real – It’s readable. There’s no magic proprietary runtime you need to reverse-engineer.
That’s the good news.

The less-good news:
Supabase is tightly integrated.
The app talks to a Supabase project by project URL and anon key. If you want to move away from Supabase (or self-host Supabase), that’s a bigger migration than just moving the frontend.

For most people: keep Supabase, move the frontend.
That’s the path of least resistance.

Step 1: Export Your Code

First things first.

Go to your Lovable project → click the GitHub button → connect your GitHub account → push the project.

You now have a real repository with real code. Clone it locally:

 git clone https://github.com/your-username/your-lovable-project.git  cd your-lovable-project  npm install 

Before you do anything else, make sure it runs locally:

 npm run dev 

If it opens in your browser and works: great. If it doesn’t: check your .env file (more on that in a moment).

Step 2: Understand Your Environment Variables

This is where most people get stuck.
Lovable injects environment variables automatically. When you run this yourself, you’re responsible for them.

Create a .env file in your project root:

 VITE_SUPABASE_URL=https://your-project-ref.supabase.co  VITE_SUPABASE_ANON_KEY=your-anon-key-here 

Find these in your Supabase dashboard → Project Settings → API.

One important thing: never commit your .env to git. Add it to .gitignore immediately if it isn’t already there.

 echo ".env" >> .gitignore 

For production deployments, you’ll set these as environment variables in your hosting provider’s dashboard — not as files checked into the repo.

Step 3: Build for Production

 npm run build 

This generates a dist/ folder. Everything in there is static — HTML, CSS, JavaScript bundles. No Node.js server required to serve it.

You can host this on:

• Vercel (easiest, free tier is generous)
• Netlify (similar to Vercel, excellent DX)
• Cloudflare Pages (fastest globally, very generous free tier)
• A plain VPS with Nginx (most control, most work)

My default recommendation:
1. Cloudflare Pages for public-facing apps
2. VPS + Nginx if you want full control and have ops comfort.

Step 4: Deploy to Cloudflare Pages (Recommended)

If you just want it running fast with zero infrastructure overhead:

1. Push your repo to GitHub (done in Step 1)
2. Go to Cloudflare Pages → Create Project → Connect GitHub
3. Select your repo
4. Set build settings:

• Build command: npm run build
• Build output directory: dist

1. Add your environment variables (VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY)
2. Deploy

Done.

Your app is live on a Cloudflare CDN edge network in ~2 minutes, with automatic deployments on every push to main.

Step 5: Deploy to a VPS (The “Real Self-Hosting” Path)

For maximum control, run it on your own server.
I recommend fly.io (so you don’t need to install/maintain anything – just build your webapp in docker) or Hetzner — the value is absurd compared to AWS or GCP for basic hosting needs.

Provision your server, then SSH in:

 ssh root@your-server-ip 

Install Nginx:

 apt update && apt install nginx -y 

Create your site directory and copy the build:

 mkdir -p /var/www/myapp  # From your local machine:  scp -r dist/* root@your-server-ip:/var/www/myapp/ 

Or better: set up a CI/CD pipeline that does this automatically on push.

Configure Nginx:

 server {      listen 80;      server_name yourdomain.com;      root /var/www/myapp;      index index.html;       # This is critical for React Router — all paths serve index.html      location / {          try_files $uri $uri/ /index.html;      }       # Cache static assets aggressively      location ~* \.(js|css|png|jpg|jpeg|gif|ico|svg|woff2)$ {          expires 1y;          add_header Cache-Control "public, immutable";      }  } 

Save to /etc/nginx/sites-available/myapp, symlink it:

 ln -s /etc/nginx/sites-available/myapp /etc/nginx/sites-enabled/  nginx -t && systemctl reload nginx 

Add HTTPS with Let’s Encrypt:

 apt install certbot python3-certbot-nginx -y  certbot --nginx -d yourdomain.com 

Certbot auto-renews.
You’re done.

Step 6: The Native App Situation

If your Lovable app has a native mobile wrapper — this is where things get interesting.

Lovable has been expanding into native capabilities using Capacitor under the hood. If your project has native bindings, you’ll find a capacitor.config.ts in the project root.

The good news:
Capacitor is open-source and you own the workflow entirely.

For iOS:

 npm run build  npx cap sync ios  npx cap open ios 

This opens Xcode with your project. From there, you archive and submit to the App Store exactly like any other iOS app. You need an Apple Developer account ($99/year).

For Android:

 npm run build  npx cap sync android  npx cap open android 

This opens Android Studio. Build → Generate Signed Bundle/APK → distribute via Play Store or sideload directly.

The webview URL matters.

In development, Capacitor talks to localhost. In production, you need to point it at your live web app. Edit capacitor.config.ts:

 import { CapacitorConfig } from '@capacitor/cli';   const config: CapacitorConfig = {    appId: 'com.yourcompany.yourapp',    appName: 'Your App',    webDir: 'dist',    server: {      // Remove this for production — use bundled assets instead      // url: 'http://localhost:5173',      androidScheme: 'https'    }  };   export default config; 

For most native apps, you want the webDir approach — the built assets are bundled directly into the native app binary. This means offline support works and you don’t depend on your web server being up for the app to function.

Run npx cap sync after every build to keep the native project in sync with your web build.

Step 7: Handling Supabase at Scale

You moved the frontend. Supabase is still doing the backend work.

For most apps: that’s fine. Supabase is genuinely good infrastructure.

But if you want to self-host Supabase too (for compliance, cost, or curiosity), they publish an official Docker Compose setup:

 git clone --depth 1 https://github.com/supabase/supabase  cd supabase/docker  cp .env.example .env  # Edit .env with your secrets  docker compose up -d 

This runs the full Supabase stack — Postgres, GoTrue (auth), PostgREST, Realtime, Storage, and Studio — on your own hardware.

It’s more maintenance burden. But it’s also complete ownership.

My honest take: use Supabase managed unless you have a specific reason not to.
Their managed infrastructure is well-run and the pricing is reasonable until you’re at serious scale.

Step 8: Setting Up CI/CD So You Don’t Do This Manually Again

Manually copying files to a server is how you get paged at 2am because you forgot a step.

Here’s a minimal GitHub Actions workflow that builds and deploys on every push to main:

 # .github/workflows/deploy.yml  name: Deploy   on:    push:      branches: [main]   jobs:    deploy:      runs-on: ubuntu-latest      steps:        - uses: actions/checkout@v6         - name: Setup Node          uses: actions/setup-node@v6          with:            node-version: '24'            cache: 'npm'         - name: Install & Build          run: |            npm ci            npm run build          env:            VITE_SUPABASE_URL: ${{ secrets.VITE_SUPABASE_URL }}            VITE_SUPABASE_ANON_KEY: ${{ secrets.VITE_SUPABASE_ANON_KEY }}         - name: Deploy to Server          uses: appleboy/[email protected]          with:            host: ${{ secrets.SERVER_HOST }}            username: ${{ secrets.SERVER_USER }}            key: ${{ secrets.SSH_PRIVATE_KEY }}            source: "dist/*"            target: "/var/www/myapp"            strip_components: 1 

Add your secrets in GitHub → Settings → Secrets and variables → Actions.

Push to main. It deploys automatically.
That’s the whole loop.

The Checklist Before You Pull the Plug on Lovable

Don’t cancel your Lovable plan until you’ve verified all of this:

• [ ] App runs locally with npm run dev
• [ ] Production build succeeds with npm run build
• [ ] All environment variables are set correctly in production
• [ ] Supabase Row Level Security policies are configured (don’t rely on Lovable having set these correctly)
• [ ] Auth flows work end-to-end (sign up, sign in, sign out, password reset)
• [ ] Any storage/file uploads work against your Supabase bucket policies
• [ ] Edge functions (if any) are deployed to Supabase
• [ ] Custom domain is pointing to your new hosting
• [ ] HTTPS is working
• [ ] Native builds open and run correctly (iOS Simulator + Android Emulator at minimum)
• [ ] CI/CD pipeline deploys successfully from a test push

Run through this list twice.
Yep… On the second time you’ll catch something you missed.

What I’ve Learned From Doing This

Lovable is excellent for getting to a working product quickly.
Self-hosting is excellent for owning what you built.

These aren’t in conflict — they’re a sequence.

Build fast on Lovable.
Validate the idea.
Get real users.
Then, when the infrastructure costs start mattering or the compliance questions start arriving, migrate.

The migration is maybe 4–6 hours of focused work for a typical app.
That’s worth doing on a quiet Sunday, not during a crisis.

Do it before you need to.

Questions? Find me on GitHub

Rate this:

Lovable dice que ha escaso los 500 millones de dólares en ingresos anualizados, con 1 millón de nuevos proyectos por semana #alcanzado #Amable #anualizados #codificación_de_vibraciones #con #dice #dólares #ingresos #los #Lovable #millón #millones #nuevos #por #Proyectos #semana #ButterWord #Spanish_News Coment...
https://butterword.com/lovable-dice-que-ha-escaso-los-500-millones-de-dolares-en-ingresos-anualizados-con-1-millon-de-nuevos-proyectos-por-semana/?feed_id=84372&_unique_id=6a2819cb3293a

يقوم Lovable بإجراء فحص أمني تلقائي وشامل قبل نشر المحتوى، يتحقق خلاله من المشكلات الشائعة، أخطاء إعدادات قواعد البيانات، وثغرات التفويض في غضون 10-15 ثانية. ولضمان تغطية أمنية متكاملة، يوفر النظام أيضاً مراجعة عميقة بالذكاء الاصطناعي وخيارات إصلاح تلقائي اختيارية. هذه الميزة تعالج النتائج مباشرة ضمن سير عمل البرمجة المعتاد، مما يضمن بيئة تطوير آمنة وموثوقة للمستخدمين.

#Lovable #Security #AI

أعلنت منصة Lovable عن إطلاق وكلاء فرعيين متوازيين للعمل في الخلفية لإجراء مهام البحث والمراجعة وضمان الجودة، مما يساهم في تسريع عمليات البناء وزيادة الدقة في المشاريع البرمجية الكبيرة. ويمكن للمستخدمين الآن تتبع أنشطة هؤلاء الوكلاء بدقة عبر سجل النشاط ومعرفة مصادر القرارات المتخذة. والجدير بالذكر أن هؤلاء الوكلاء يعملون في وضع القراءة فقط لحماية سلامة الكود البرمجي مع السماح باستكشاف عميق للمشروع وتطويره بكفاءة وأمان.

#Lovable

Has any puppy ever been more adorable than Baby Vira? #dog #dogs #doglife #dogslife #doglover #doglovers #canine #canines #family #familymember #furbaby #furbabies #puppy #puppies #puppylove #puppylover #puppylovers #dogpack #dogpackfamily #shitzu #shitzus #jackrussell #jackrussells #lovable #daughter #daughters

Has any puppy ever been more adorable than Baby Vira? #dog #dogs #doglife #dogslife #doglover #doglovers #canine #canines #family #familymember #furbaby #furbabies #puppy #puppies #puppylove #puppylover #puppylovers #dogpack #dogpackfamily #shitzu #shitzus #jackrussell #jackrussells #lovable #daughter #daughters

> After we were told about the problem and then denied it and then realized we are wrong, we deployed a fix in hours.

*cringe*

https://xcancel.com/zackkorman/status/2048767688411959573

#Vercel #Lovable

Cousin Razzy, Franklin, Vira, and Zack. Our Dog Pack Family. #family #families #dogfamily #dogfamilies #dogpack #dogpacks #dog #dogs #canine #canines #furbaby #furbabies #children #kiddies #couchsitting #playtime #petting #pets #pet #fur #brushing #love #lovable

Cousin Razzy, Franklin, Vira, and Zack. Our Dog Pack Family. #family #families #dogfamily #dogfamilies #dogpack #dogpacks #dog #dogs #canine #canines #furbaby #furbabies #children #kiddies #couchsitting #playtime #petting #pets #pet #fur #brushing #love #lovable

Thousands of Vibe-Coded Apps Expose Corporate and Personal Data on the Open Web

Companies like #Lovable , #Base44 , #Replit , and #Netlify use #AI to let anyone build a web app in seconds—and in thousands of cases, spill highly sensitive data onto the public internet.
#privacy #security #development #vibecoding

https://www.wired.com/story/thousands-of-vibe-coded-apps-expose-corporate-and-personal-data-on-the-open-web/

Thousands of Vibe-Coded Apps Expose Corporate and Personal Data on the Open Web

Companies like #Lovable , #Base44 , #Replit , and #Netlify use #AI to let anyone build a web app in seconds—and in thousands of cases, spill highly sensitive data onto the public internet.
#privacy #security #development #vibecoding

https://www.wired.com/story/thousands-of-vibe-coded-apps-expose-corporate-and-personal-data-on-the-open-web/

Was ist Agentic Coding?
Für Kids, Jugendliche & Eltern

Stell dir vor, du hast eine geniale Idee für ein neues Game. Bisher musstest du dafür wochenlang jede einzelne Zeile Code (die Sprache, die Computer verstehen) selbst tippen. Wenn du einen Fehler gemacht hast, lief das Spiel nicht. Beim Agentic Coding ändert sich das komplett!

https://bit.ly/42gotXz

#vibecoding, #kicomic, #kiagent, #cursor, #replit, #bolt.new, #devin, #aider, # GitHubCopilot, #windsurf, #v0.dev, #Lovable

What if your strategy could become working software in just a few steps? Datentreiber is demoing “Strategy-as-Software” at Miro Canvas 26 in London—built with Miro Flows, MCP & Lovable to create a custom data & AI management app that adapts to you. Curious? https://canvas.miro.com/london #Miro #Canvas26 #StrategyAsSoftware #DataAI #MCP #Lovable #NoCode
https://www.datentreiber.com/blog/strategy-as-software-miro-canvas-26-london/

#Lovable launched its #nocode #AIappbuilder as a #mobile #app on #iOS and #Android. The app allows users to code on the go via voice or text AI prompts and switch between devices seamlessly. https://techcrunch.com/2026/04/28/lovable-launches-its-vibe-coding-app-on-ios-and-android/?eicker.news #tech #media #news

Programowanie głosem na iPhonie. Lovable trafia do App Store i sprytnie omija restrykcje Apple

„Vibe coding”, czyli tworzenie oprogramowania za pomocą języka naturalnego i sztucznej inteligencji, właśnie staje się w pełni mobilne.

Do App Store trafiła aplikacja Lovable – jednego z najpopularniejszych narzędzi w tej kategorii. Twórcy znaleźli też sprytny sposób, by nie narazić się na gniew weryfikatorów Apple, którzy w ostatnich tygodniach bezlitośnie usuwali podobne programy ze sklepu.

Apple blokuje aktualizacje popularnych aplikacji „vibe coding”

W ciągu ostatnich kilku tygodni Apple rozpoczęło ostre czystki w App Store, celując w aplikacje oparte na AI, które potrafiły pisać i modyfikować własny kod bezpośrednio na urządzeniu. Argumentowano to naruszeniem regulaminu, który kategorycznie zabrania aplikacjom zmiany swojego zachowania i kodu po przejściu procesu weryfikacji.

Lovable ominęło tę blokadę w bardzo elegancki sposób. Aplikacja nie modyfikuje samej siebie, ani nie tworzy natywnych apletów na iOS. Zamiast tego, narzędzie generuje w pełni funkcjonalne aplikacje webowe (web apps).

Tworzenie kodu z poziomu kanapy

Zasada działania Lovable na iPhonie jest banalnie prosta. Użytkownik nie musi znać ani jednej linijki kodu – wystarczy, że opisze swój pomysł za pomocą naturalnego języka lub – co w wersji mobilnej jest największym atutem – za pomocą komend głosowych. Sztuczna inteligencja zajmuje się całą resztą, pozwalając jednocześnie na podgląd i ewentualną ręczną edycję wygenerowanego kodu.

Dzięki temu, że Lovable opiera się na technologiach webowych, oferuje pełną ciągłość pracy (cross-platform). Jak chwalą się twórcy, użytkownik może rozpocząć prototypowanie nowej aplikacji za pomocą głosu podczas spaceru z iPhonem, a następnie usiąść do komputera i płynnie kontynuować iteracje w przeglądarce na Macu.

Sama aplikacja Lovable jest darmowa do pobrania, jednak pełne wykorzystanie jej możliwości wymaga wykupienia subskrypcji. Plany abonamentowe, w zależności od potrzeb i limitów zapytań do sztucznej inteligencji, wahają się od 9,99 do 79,99 dolarów miesięcznie.

Lovable, una delle piattaforme di coding più usate, ha lanciato un'app iOS che crea app web basate su prompt in linguaggio naturale e interazioni vocali.

#lovable #ios
https://kiro.it/njZkY

Ich glaube, ich habe mir ein #lovable - light gebaut.
Für meine Anwendungsfälle jedenfalls reicht es und ich brauche keinen Bezahl-account.

📝 New post: I Let an AI Build My App. Two Years Later, I Asked Another AI to Fix It.
In 2024 I used Lovable (then GPT Engineer) to build a hobby weather app in an afternoon. In 2026 I finally looked at what it had actually generated. The findings were instructive.
https://radomski.co.nz/blog/refactoring-can-you-beat-wellington
#AI #Projects #Lovable #WebDev #Learning

Ich habe die letzten Wochen mit lovable.dev herumgespielt – ziemlich spannend, wie schnell man damit Ideen in funktionierende #Prototypen übersetzen kann. :)

Gerade für #UX, schnelle Experimente oder #MVP echt ein gutes #Tool.

Falls ihr es ausprobieren wollt, hier ein Invite-Link (gibt ein paar gratis Credits zum Start):
https://lovable.dev/invite/JCTT6FD

Bin gespannt, was ihr damit baut 👀

#vibecoding #app #lovable

https://www.tkhunt.com/2277373/ 【全員オススメ】今欲しい全てが詰まったAIエディター「Superset」を徹底解説！ #AgenticAi #AI #AIAgent #AI活用 #ai開発 #ArtificialIntelligence #bolt #Canva #ChatGPT #Claude #CSS #cursor #CursorComposer #DeepSeek #DX #expo #figma #firebase #GEMINI #llm #LOVABLE #LP #NextJs #notion #openai #pc #Python #react #reactnative #supabase #tailwindCSS #typescript #v0 #WEBデザイン #Web開発 #アプリ開発 #エージェント型AI #エンジニア #ガジェット #コーティング #コードエディター #バックエンド #フルスタック #プログラミング #フロントエンド #プロンプト #まさお #人工知能 #副業 #動画生成 #技術 #機械学習 #独学 #生成AI #画像生成

https://winbuzzer.com/2026/03/24/lovable-hunts-acquisitions-vibe-coding-land-grab-xcxwbn/

Lovable Hunts for Acquisitions in Vibe-Coding Land Grab

#AI #Lovable #VibeCoding #Cursor #Replit #AIAgents #AICoding #CodingTools #GenerativeAI

5分で収益化サイト生成　AI開発ツール「Atoms」、Lovableの“2割コスト”

https://web.brid.gy/r/https://36kr.jp/460364/