XFile Ultra
Log inSign up

Update XFile Ultra safely

Use buyer-update.sh so .env and data/ stay put. The script backs up the database and rebuilds.

Update XFile Ultra safely

When you download a newer xfileultra.zip, do not unzip it on top of the live site by hand. Use buyer-update.sh so configuration and uploaded data stay intact.

What the update keeps

  • .env (secrets, database URL, site URL)
  • data/ (app data; uploads stay where your storage layout put them)
  • A database dump under /root/xfileultra-backups/<timestamp>/ (plus a copy of .env) — not a full copy of every uploaded file

Steps

1. Upload the new zip to the server (not unpacked over /var/www/xfileultra):

scp ~/Desktop/xfileultra.zip root@YOUR-SERVER-IP:/root/

2. Unpack beside the live install (or pass the zip path directly):

cd /root
sudo apt install -y unzip
sudo unzip -o xfileultra.zip -d /root/xfileultra-update

3. Run the update from the live site directory:

cd /var/www/xfileultra
sudo chmod +x scripts/buyer-update.sh
sudo ./scripts/buyer-update.sh /root/xfileultra-update/xfileultra

Or:

sudo ./scripts/buyer-update.sh /root/xfileultra.zip

The script stops the service briefly, backs up .env and a DB dump, applies the new code, runs migrations, rebuilds, and restarts.

Dry run (no changes)

sudo ./scripts/buyer-update.sh --dry-run /root/xfileultra.zip

Common problems

Site errors after update

Check journalctl -u xfileultra. Often a migration failed or Node is too old. Fix the error, then restart.

“I lost my settings”

Settings live in the database and .env. If someone replaced .env or restored an old DB dump over a new one, config looks gone. Restore from /root/xfileultra-backups/.

Unpacked over the live folder manually

You may have wiped .env or data/. Stop, restore from backup, use buyer-update.sh next time.

Related