Skip to Content
Updating Vortexus

Updating Vortexus

Use this guide when you already run Vortexus and receive a new package (for example 1.0.3). Always back up your database, Paymenter files, and .env before replacing anything.

Back up first

Take a full backup (database + project folder + .env). If a step fails, restore from backup or contact support with the full terminal error.

1. Replace module files

From your download, merge into your Paymenter project root (the folder that contains artisan):

Core/          → merge into Paymenter root (app/, routes/, lang/, etc.)
extensions/Others/VortexusMarketplace/
extensions/Servers/VortexusWeb/
  • Do not blindly overwrite your entire app/ tree if you have local customizations — use a diff tool and merge only what the release notes require.
  • Folder paths under extensions/ must stay exactly as Paymenter expects (Others/ and Servers/).

If the site is public, optional maintenance mode:

php artisan down

2. Composer autoload

Where: Paymenter project root.

composer install --no-dev --optimize-autoloader

Or, if the release notes say so:

composer dump-autoload

3. Database migrations

Where: Paymenter project root.

What it does: Adds or updates Vortexus tables (notifications, resource alerts, installation tracking, etc.).

php artisan migrate --force

Read the output. If migration fails, stop, restore from backup, and contact support with the full error text.

Recent updates may add migrations such as:

  • Notification log and resource alert state tables
  • action_type on marketplace installations (install vs reinstall vs provision)

4. Clear Laravel caches

Where: Paymenter project root.

After replacing PHP files, clear cached config, routes, views, and compiled services:

php artisan optimize:clear

This runs, in one command:

  • config:clear
  • cache:clear
  • route:clear
  • view:clear
  • and other optimize caches for your Laravel version

Production tip

After you confirm the site loads correctly, you may rebuild caches if your runbook uses them:

php artisan config:cache
php artisan route:cache
php artisan view:cache

Only do this after smoke tests — cached config can hide misconfiguration until cleared.

5. Frontend build (if assets changed)

If the release includes theme or Vite changes under Core/:

npm ci
npm run build

Deploy public/build (or your project’s build output) if the server does not build on deploy.

6. Re-enable extensions

In Paymenter Admin → Extensions:

  1. Vortexus Marketplace (Others) — should stay enabled; re-enable if you disabled it during maintenance.
  2. Vortexus Web (Servers).

Saving extension settings re-runs module migrations if the publisher hooks installed() — safe to open settings once after upgrade.

7. Post-update checklist (1.0.3+)

Cron / scheduler

Vortexus relies on Laravel’s scheduler. System cron must run every minute:

* * * * * cd /path-to-paymenter && php artisan schedule:run >> /dev/null 2>&1

Scheduled jobs include:

  • vortexus:resource-monitor — every 5 minutes (resource alert emails)
  • vortexus:payg-billing — every 5 minutes (PAYG deductions)
  • Invoice reminders — daily

Manual test:

php artisan vortexus:resource-monitor -v

Email templates

  1. Open Admin → Vortexus Marketplace → Email templates (/admin/marketplace-notification-templates).
  2. Choose language (e.g. English, Portuguese, Spanish).
  3. Click Import templates (replaces existing vortexus_* keys).
  4. Optionally edit templates via Edit or Open Notification Templates.

Resource limits (multi-server hosts)

If Enable Multi Servers is on:

  1. Open Admin → Vortexus Marketplace → Resource limits.
  2. Click Apply to existing servers once after upgrade if you want OOM protection on servers provisioned before the setting existed.

CLI equivalent:

php artisan vortexus-marketplace:apply-oom-killer

Notification log

Open Admin → Vortexus Marketplace → Notification log and confirm new events appear after a test provision or resource alert.

Marketplace installations

Open Admin → Vortexus Marketplace → Installations — entries should show Completed / Failed with action type (provision, marketplace reinstall, panel reinstall), not stuck on Pending.

8. Go live

php artisan up

Sanity checklist

  • Admin loads without errors (storage/logs/laravel-*.log).
  • Marketplace and client panel routes work.
  • A test email sends (provision or import templates + trigger an event).
  • Scheduler heartbeat is recent (Paymenter cron / schedule health, if you use it).

What changed?

See Changelog for details on Email templates, Resource limits, Notification log, resource monitor, and reinstall notifications.

Need help? Support & purchase.

InstallationChangelog