Zum Hauptinhalt springen

Upgrading FeedbackPulse SaaS

How to safely upgrade to a new version of FeedbackPulse SaaS.


Before You Upgradeโ€‹

  1. Create a database backup โ€” Admin โ†’ Backups โ†’ Create Backup
  2. Back up your .env file โ€” cp .env .env.backup
  3. Back up uploaded files โ€” cp -r storage/app/public storage/app/public.backup
  4. Note your current version โ€” check config/app.php for the version number
  5. Read the changelog โ€” check what's new and if there are breaking changes

Upgrade Stepsโ€‹

Step 1: Download the New Versionโ€‹

Download the latest release from CodeCanyon.

Step 2: Upload New Filesโ€‹

Replace application files (but preserve your configuration):

cd /var/www/feedbackpulse-saas

# Back up critical files
cp .env .env.backup
cp -r storage/app/public storage/app/public.backup

# Upload and extract new files
# (overwrite existing files, but NOT .env or storage/app/public/)

Do NOT overwrite:

  • .env (your configuration)
  • storage/app/public/ (uploaded files)
  • storage/installed.lock (installation lock)
  1. Melden Sie sich an as Super Admin
  2. Visit https://yourdomain.com/update
  3. Click Run Update

This automatically:

  • Runs any pending database migrations
  • Clears configuration, route, and view caches
  • Re-creates the storage symlink (or confirms the PHP fallback is active)
  • Updates the stored version number

Shared hosting users: This is all you need. No terminal, no SSH, no php artisan commands.

Step 3 (Alternative): CLI Update (VPS/Dedicated Only)โ€‹

If you prefer the command line:

composer install --no-dev --optimize-autoloader
php artisan migrate --force
php artisan optimize:clear
php artisan optimize

Step 4: Restart Services (VPS Only)โ€‹

Skip this step on Shared Hosting.

# Restart queue workers (if using)
sudo supervisorctl restart feedbackpulse-worker:*

# Restart PHP-FPM
sudo systemctl restart php8.2-fpm

Step 5: Verifyโ€‹

  1. Visit your site โ€” check the Landingpage loads
  2. Melden Sie sich an as superadmin โ€” verify the dashboard
  3. Check Admin โ†’ Einstellungen โ€” look for any new configuration options
  4. Check the version number in the Admin-Panel

Rolling Backโ€‹

If something goes wrong:

# Restore .env
cp .env.backup .env

# Restore uploaded files
cp -r storage/app/public.backup/* storage/app/public/

# Restore database from backup
mysql -u username -p feedbackpulse < backup.sql

# Clear caches
php artisan optimize:clear

Naechste Schritteโ€‹