Quick Start
Travelio SaaS — from download to a working platform
Developed By: BugBuild Labs
Quick Start
The shortest path from the ZIP you downloaded to a working Travelio SaaS platform: your landing page and signup on yourplatform.com, your platform panel, and every agency on its own agency.yourplatform.com. Each step is covered in more depth in SaaS Platform.
| Step | What you do | Roughly |
|---|---|---|
| 1 | Create the database | 2 min |
| 2 | Upload the files and point the domain at /public | 5 min |
| 3 | Fill in .env and add the wildcard DNS record | 5 min |
| 4 | Run the web installer | 3 min |
| 5 | Sign in to the platform panel and set it up | 10 min |
| 6 | Build the mobile app for your agencies | 5 min |
This package runs as a SaaS platform out of the box; there is no mode to switch. Every agency workspace runs the full Travelio ERP described in Web (Admin).
1. Create the Database
In cPanel → MySQL Databases: create a database, create a user with a strong
password, then add the user to the database with ALL PRIVILEGES. Use
utf8mb4_unicode_ci collation.
cPanel prefixes names with your account, so travelio_db becomes something like myaccount_travelio_db. Use the full prefixed name in .env.
The platform creates one database per agency. Its MySQL user therefore needs the CREATE and DROP privileges on new databases, which most shared cPanel accounts do not allow. Use a VPS or a host that grants them, for example:
CREATE USER 'travelio'@'localhost' IDENTIFIED BY 'a-strong-password';
GRANT ALL PRIVILEGES ON *.* TO 'travelio'@'localhost';
FLUSH PRIVILEGES;
To limit it, grant on the platform database plus the agency name pattern instead (agency databases are named tenant followed by the agency ID, e.g. GRANT ALL PRIVILEGES ON `tenant%`.* TO ...).
2. Upload the Files
Extract Main_Files.zip and upload the contents of WebSourceCode/ to
your server. Point the domain's document root at the public/ folder.
Install the PHP packages. The vendor/ folder is not shipped. In the project folder (cPanel → Terminal, or SSH) run:
composer install --no-dev --optimize-autoloader
No terminal on your host? Run the same command on your own computer and upload the resulting vendor/ folder with the rest of the files.
Make these writable (755, or 775 if PHP runs as another user):
storage/
bootstrap/cache/
Requirements: PHP 8.3+ with the pdo_mysql, mbstring, openssl, tokenizer, xml, curl, fileinfo, bcmath, json extensions (and zip if you will use System Update), MySQL 8 / MariaDB 10.6+, Composer 2. Node.js is only needed to rebuild the CSS (npm run build).
3. Configure .env & DNS
The web installer (step 4) writes .env for you; set it by hand only for a command-line install. Copy .env.example to .env and set at least these:
APP_NAME="Travelio"
APP_ENV=production
APP_DEBUG=false
APP_URL=https://yourplatform.com
APP_TIMEZONE=UTC
DB_DATABASE=myaccount_travelio_db
DB_USERNAME=myaccount_dbuser
DB_PASSWORD=your_password
SAAS_DOMAIN= # base for agency addresses; empty = the host of APP_URL
SAAS_CENTRAL_DOMAINS= # extra platform hosts, e.g. www.yourplatform.com; usually empty
With APP_URL=https://yourplatform.com and SAAS_DOMAIN empty, agency skyline gets skyline.yourplatform.com. Set SAAS_DOMAIN only when agencies should live under another domain. Everything else (brand, logo, currency, mail, payment gateways) is set later in the panel.
DNS: point both the domain and a wildcard at your server, and serve both with a wildcard SSL certificate:
| Type | Name | Value |
|---|---|---|
| A | @ (yourplatform.com) | your server IP |
| A | * | your server IP |
Set SAAS_DOMAIN before the first agency signs up. Each agency's address is saved when it is created and does not move if the value changes later. Web server and SSL details: Wildcard DNS, Server & SSL.
4. Install
Open https://yourplatform.com/install. The installer checks the PHP version, extensions and writable folders, tests the database connection, writes .env, builds the platform tables (plans, team roles, payment-gateway rows) and creates your owner account, the SaaS Super Admin. Use an empty database: the installer refuses one that already has tables and never modifies or deletes existing data. When it finishes it locks itself (storage/app/installed.lock), so /install cannot be reopened on the live site. Then run once:
php artisan storage:link
Add the scheduler cron entry; it runs the daily billing run (renewal invoices, reminders, expiry and suspension):
* * * * * cd /path/to/project && php artisan schedule:run >> /dev/null 2>&1
Command-line install, for a demo or a local copy:
composer install --no-dev --optimize-autoloader
php artisan key:generate
php artisan config:clear
php artisan migrate --seed
php artisan storage:link
php artisan optimize
It creates no login of its own: with APP_DEMO=true it adds the demo platform and agencies (step 5); with APP_DEMO=false use the web installer instead, which creates your owner account.
No SSH access? Ask your host to run these, or use a host with a terminal in the control panel. Composer and Artisan cannot be replaced by uploading files.
5. Log In & Set Up the Platform
Open https://yourplatform.com/admin/login and sign in with the owner account you created in the installer. (/login leads there too; customers and agents never sign in on the platform domain, only on an agency's address.)
Demo install (APP_DEMO=true): all passwords are 12345678.
| Where | Address | |
|---|---|---|
| Platform panel | yourplatform.com/admin/login | [email protected] |
| Skyline Travels (full sample data) | skyline.yourplatform.com/admin/login | [email protected], [email protected] |
| Skyline customer / agent portals | skyline.yourplatform.com/login | [email protected], [email protected] |
| Globe Tours (empty agency) | globe.yourplatform.com/admin/login | [email protected] |
Never leave demo logins on a live platform. Their passwords are printed in this documentation. Install a real platform with APP_DEMO=false.
Then, in the platform panel:
- Settings → General Settings: your platform name, contact email, currency, logo and favicon.
- Settings → Payment Gateways: credentials for the gateways you will take payments with.
- Settings → Mail Setting: your SMTP details. Signup, invoice and reminder emails are skipped until mail works.
- Billing → Plans: your prices (shipped as $19 / $49 / $99 a month), trials, limits, modules and custom domains.
- Settings → Platform Settings: reminder and grace days, custom-domain settings and the landing page texts.
6. Build the Mobile App
You publish one app for every agency. On first launch the user enters their agency's address — with WORKSPACE_DOMAIN set, just skyline — and the app remembers it. The app talks to that agency's address, never to the platform domain (which answers its API with 404). Build it from AppSourceCode/:
cp env/saas.example.json env/saas.json # set WORKSPACE_DOMAIN, API_HOST and APP_API_KEY
flutter pub get
flutter run --dart-define-from-file=env/saas.json
APP_API_KEY is the one key for all agencies, set on the platform's Settings → API Security page; agencies cannot change it. Full detail: One Mobile App for All Agencies, Travelio App.
What Next
- Team — give your staff their own platform logins with View / Manage permissions per area.
- Landing page — edit the hero, features, testimonials and FAQ in Platform Settings.
- Automatic HTTPS for custom domains — let agencies connect their own domains; see also the Custom Domain DNS Guide to send them.
- Reports — revenue, dues, subscriptions, agency growth and plan performance.
- Updating every agency — one System Update reaches the platform and every workspace.
- Common Setup — mail, push, backups and the go-live checklist.