Skip to content
Blixt

Upgrading

Blixt ships as release zips you replace in your resources/ tree, plus SQL files under sql/ that you apply by hand. Your config and your database are both your responsibility — Blixt never alters them automatically.

Before upgrading

Section titled “Before upgrading”
  1. Back up your database. Schema upgrades are forward-only; rollbacks require a restore.
  2. Back up your config.json. The new release zip will overwrite it. Save a copy somewhere outside the resource folder.
  3. Read the release notes. Posted in the Blixt Discord and linked from each new release on Tebex. The notes name the upgrade-*.sql file(s) you need to apply.

Upgrade steps

Section titled “Upgrade steps”

  1. Stop the FXServer (or at least the Blixt resources). Don’t try to hot-reload across versions — config or schema changes can leave the resource in a half-loaded state.

  2. Extract the new release zip over the existing folders:

    resources/[blixt]/blixt/
    resources/[blixt]/blixt-tablet/
    resources/[blixt]/blixt-business/

  3. Apply the schema upgrade. Each release ships sql/upgrade-vX-to-vY.sql files inside resources/[blixt]/blixt/. Apply the deltas between your current version and the target, in order:

    Terminal window
    cd resources/[blixt]/blixt
    mysql -u<user> -p<pass> <database> < sql/upgrade-1.0.4-to-1.1.0.sql

    If you skip versions, run each upgrade-*.sql in sequence. The files end with INSERT INTO blixt_migrations rows that move the version pointer forward, so on the next boot the schema-version check passes.

  4. Diff your config. Compare the new config.example.json against your saved config.json. New fields show up in the example first; port the ones you want into your config and put it back at resources/[blixt]/blixt/config.json.

  5. Start the FXServer. Watch the boot log:

    • [@blixt/database] Schema up to date (...) confirms the SQL upgrade landed cleanly.
    • [blixt] Loaded config.json confirms your config parsed.

    If you see [@blixt/database] Schema is behind. Latest applied: X, expected: Y, the upgrade file did not run. Apply the named file and restart.

  6. Smoke-test in-game. Open the phone, send a message to yourself, take a photo. If anything fails, the Troubleshooting page is the next stop.

Downgrading

Section titled “Downgrading”

There is no supported downgrade path. Schema changes are forward-only. To downgrade, restore the database backup you took before the upgrade and replace the resource folders with the previous release.

What about config.json overwrites?

Section titled “What about config.json overwrites?”

The current release process overwrites config.json on extract. Until we ship a separate config.user.json overlay file, the safest pattern is:

  • Keep your edits documented in a config.user.json you maintain yourself outside the resource (just for your own reference — Blixt doesn’t read it).
  • Diff against config.example.json after each upgrade to catch new fields.
  • Restart the resource after putting your config back.

We’re tracking the overlay-file pattern as planned work.