Upgrade Guide

Upgrading Ridy (and other BetterSuite products) is a safe and streamlined process when following the correct steps. This guide covers both Docker-based deployments and customized Flutter client upgrades, including precautions, version compatibility, and post-upgrade tasks.

---

📌 Before You Begin

✅ Backup First — Always

Before upgrading your system:

• Backup the database (e.g., using mysqldump):

  mysqldump -u root -p your_database_name > backup.sql

• Optionally, back up the .env file and uploaded assets

• Backup any modified Flutter app code in version control (e.g., Git)

---

🐳 Docker-Based Upgrade

This is the recommended approach for most production users.

1. Pull the Latest Images

Ensure Docker and docker-compose are available. Then run:

docker compose pull

2. Review .env File (if needed)

• The .env file is not overwritten, so your custom values remain
• However, new environment variables may be introduced in newer versions
  → Compare with the latest .env.example and copy over any missing keys

3. Rebuild and Restart Services

docker compose up -d --build

This will:

• Rebuild containers with the latest version
• Apply any automatic database migrations via the admin-api service

---

🧑‍💻 Flutter Client App Upgrade

For those who have customized or white-labeled the apps:

1. Get the Latest Zip

• Download the latest version of the app (e.g., rider-frontend) ZIP package
• Extract it into a clean branch or folder

2. Create a Rebase Flow (Git Recommended)

git checkout your-custom-branch
git rebase upstream/main  # assuming upstream is the clean version

Or use diff tools to manually apply changes from the official source.

3. Regenerate Assets

If your custom app uses branding:

dart run flutter_native_splash:create
dart run flutter_launcher_icons
flutter gen-l10n

4. Rebuild the App

flutter build apk   # for Android
flutter build ios   # for iOS

---

🧪 Post-Upgrade Checklist

Task	Applies To	Notes
Test trip/order creation	Server + Client	Validate dispatch, tracking, and completion flows
Check admin panel access	Server	Ensure all modules load and dashboard is responsive
Review .env for missing keys	Server	Compare with .env.example
Run Flutter app and test flows	Client	Test login, booking, notifications, payments
Validate Firebase push	Client	Ensure Firebase config is still valid
Check wallet and payment gateways	Server + Client	Make sure gateways work with updated APIs
View logs for any errors	Server (Docker logs)	Use docker logs or admin logs page

---

🔄 Compatibility Notes

Scenario	Supported?	Notes
Server upgraded, old client used	✅ Yes	If within same major version
New client used with older server	❌ No	May fail if API fields are missing/incompatible
Flutter app not updated after server	⚠️ Risky	May lose compatibility if backend fields changed

---

🧑‍🔧 Pro Plus Users

If you are a Pro Plus customer, Lume Agency manages upgrade flows for you.
Your custom changes will be rebased and merged with upstream by our engineering team, and deployments are handled internally.