Laravel SaaS Setup & PixelPages Integration

Job ID: 39791054

Budget: $250 – $750 AUD

Job Post — Laravel Worksuite Setup with Multi-Domain + PixelPages

Project: Setup and configure a Laravel-based Worksuite SaaS platform on a dedicated server (NOCIX Ryzen 7). Integrate PixelPages (Laravel landing page builder) into a multi-tenant system with unique branding per domain.



Tasks
1. Server Setup

• Provision Ubuntu 22.04 on NOCIX Ryzen 7.
• Apply updates, firewall, SSH key security.
• Install HestiaCP (control panel for domains, DB, SSL).

2. Worksuite Deployment

• Install PHP 8.2, Composer, dependencies.
• Deploy Worksuite app under /public_html.
• Configure .env, run migrations/seeders, verify app.

3. Multi-Domain Tenancy

• Configure domains (doctorclinic.com, massageclinic.com, trainerclinic.com, etc.) → all served by single Worksuite install.
• Add per-tenant branding (logo, theme, colors).
• Each domain loads its own branding and data.

4. PixelPages Integration

• Convert PixelPages into a Worksuite module.
• Link PixelPages pages to tenants (tenant_id).
• Each domain’s root (/) loads its PixelPages landing page.
• Support multiple pages per tenant (about, services, contact).
• /app goes to Worksuite dashboard.

5. Branding & Admin

• Tenant admins can upload logos, pick themes.
• Admin panel to manage landing pages + select default page.

6. Extras

• Contact forms (per-tenant emails).
• SEO tags + sitemap per domain.
• Analytics script per tenant.
• Booking widget support (if scheduler plugin enabled).

7. Performance & Reliability

• Enable caching (Redis or fallback).
• Supervisor/systemd for Laravel queue + scheduler + Ollama.
• Configure nightly DB + storage backups (B2/S3).
• Test restore process.
• Uptime monitoring setup.

8. Documentation

• Provide INSTALL.md + TENANT_RUNBOOK.md.
• Show how to add new domains/tenants and landing pages.
• Smoke test all domains: SSL, branding, landing, contact form, backups.



Deliverables
• Fully working Worksuite SaaS with multi-domain + PixelPages.
• Branded landing pages per domain.
• Internal AI connector ready (Ollama installed, basic test run).
• Backups and monitoring configured.
• Clear documentation provided.



Timeline
• Estimated 1–2 weeks.
• Effort: ~18–22 hours.


Looking for: A Laravel + server admin developer with experience in SaaS, multi-tenancy, and control panels like HestiaCP.