Lovable Front-End Hostinger Integration Setup
Budget / Salary$10–30
TypeFreelance project
LocationRemote
Posted2 hours ago
My SaaS platform is currently living entirely on Lovable, but I now have a Hostinger VPS with cPanel tied to my own domain. I need the whole back-end—files, database, APIs, cron jobs—moved to the VPS, while every visual element (pages, layouts, log-in screens, theme assets) continues to be edited inside Lovable. Any change I press “publish” for in Lovable must appear on the live site automatically, without manual uploads.
Here is the practical flow I want:
• Lovable stays the single source of truth for everything users see.
• When I hit save/publish in Lovable, it pushes to GitHub.
• A CI/CD routine (GitHub Actions or similar) immediately deploys the new front-end bundle over SSH to my Hostinger server, leaving the database and back-end code untouched.
• Rollbacks and branch testing should be possible from GitHub.
Current environment
– Hostinger VPS/cloud with cPanel, full SSH access, and an empty MySQL database ready for import.
– A private GitHub repo holding the existing Lovable export.
– Node.js and PHP are both available on the server; you can decide which stack is cleaner for the deployment script.
Deliverables
1. Migrated back-end, database and environment running on Hostinger with no broken routes or 500 errors.
2. Automated pipeline that detects Lovable commits and deploys front-end files to the correct directory, clearing cache if needed.
3. Short README in the repo explaining how to trigger manual deploys or roll back.
4. One live demo showing a design tweak made in Lovable appearing instantly on the production site.
Acceptance criteria
• Page load and API calls from Hostinger match current Lovable speed and functionality.
• At least three successful automatic deploys demonstrated during hand-over.
• No hard-coded Lovable URLs remain in the code base.
If you have experience wiring builders like Lovable to external hosting via GitHub and CI/CD, this should be straightforward. I am ready to provide repository access and SSH keys as soon as we agree on the task.
Here is the practical flow I want:
• Lovable stays the single source of truth for everything users see.
• When I hit save/publish in Lovable, it pushes to GitHub.
• A CI/CD routine (GitHub Actions or similar) immediately deploys the new front-end bundle over SSH to my Hostinger server, leaving the database and back-end code untouched.
• Rollbacks and branch testing should be possible from GitHub.
Current environment
– Hostinger VPS/cloud with cPanel, full SSH access, and an empty MySQL database ready for import.
– A private GitHub repo holding the existing Lovable export.
– Node.js and PHP are both available on the server; you can decide which stack is cleaner for the deployment script.
Deliverables
1. Migrated back-end, database and environment running on Hostinger with no broken routes or 500 errors.
2. Automated pipeline that detects Lovable commits and deploys front-end files to the correct directory, clearing cache if needed.
3. Short README in the repo explaining how to trigger manual deploys or roll back.
4. One live demo showing a design tweak made in Lovable appearing instantly on the production site.
Acceptance criteria
• Page load and API calls from Hostinger match current Lovable speed and functionality.
• At least three successful automatic deploys demonstrated during hand-over.
• No hard-coded Lovable URLs remain in the code base.
If you have experience wiring builders like Lovable to external hosting via GitHub and CI/CD, this should be straightforward. I am ready to provide repository access and SSH keys as soon as we agree on the task.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.