Docs / License & updates

License & updates

Tokify validates your purchase against Medel Platforms and can install new releases with one click — backing up your files and database first, and rolling back automatically if anything goes wrong.

License activation

Enter your key in Admin → License & updates. Tokify verifies it and caches the result. Verification is designed to never take your site offline:

A successful check is trusted for 12 hours before re-verifying.
If medel.es is unreachable, the last known-good verdict is honoured indefinitely — your site keeps working. The moment the API answers again, a real revocation propagates within the 12-hour window.
An explicit “invalid key” answer blocks the app immediately, but the recovery routes (/admin/license, login) always stay reachable so you can fix it.

One-click updates

In Admin → License & updates, press Check for updates. If a newer release exists, an Install update button appears. Pressing it runs this pipeline, streaming a step-by-step log:

Maintenance mode ON — visitors see a 503 notice; admins keep working.
Backup the database (mysqldump, with a PHP fallback) and the file tree into /backups/*.zip.
Download the release ZIP from Medel Platforms (verified by SHA-256).
Extract it to a temporary folder.
Copy the new files over the live tree, skipping your config and runtime data.
Run the bundled update/update.sql (the per-release schema script).
Bump the version in settings.app_version.
Maintenance mode OFF.

Safe by design: if any step fails, Tokify restores the file tree from the pre-update backup, turns maintenance back off and shows you the log. Your backups/ folder keeps the DB dump and ZIP either way.

What is never overwritten

Your configuration and user data survive every update. The updater skips:

config.php          your DB credentials + encryption key
.env                optional environment overrides
storage/            all media, thumbnails, logs, jobs, uploads
public/uploads/     publicly served buyer uploads
backups/            pre-update backups
install/            never overwrites a live wizard
.git/

Version source

The live version lives in settings.app_version (the updater bumps it). config.php only holds the install-time seed, so the version keeps rising across updates without ever touching your config file.

Publishing a release (for developers)

Each release is a ZIP carrying the full app plus an update/update.sql schema script. Build it from the project root on Windows:

Bump the VERSION file (e.g. 1.1.0).
Write the schema changes for this release into update/update.sql (leave only comments if there are none).
Run build-dist.bat. It stages a clean copy, ships a fresh config.php (from config.sample.php, version-stamped, TOKIFY_INSTALLED=false), empties runtime folders, and writes _dist\tokify-vX.Y.Z.zip with forward-slash paths (Linux-safe).
Upload the ZIP to Medel Platforms and publish it for the product. The license API then serves it to buyers as { version, download_url, sha256 }, and their one-click updater installs it.

update/update.sql rules: include only the SQL needed to go from the previous release to this one; make it idempotent (IF NOT EXISTS, etc.) so a re-run is harmless. Statements are separated by ; + a newline.

Third-party credits

Tokify bundles fonts in public/assets/fonts/, used both to burn video subtitles and as webfonts for the subtitle previews, so the editor and the final video share the same typography on any server:

Noto Emoji (Google) — emojis in subtitles — SIL Open Font License 1.1.
Nunito, Poppins, Inter, Montserrat, Oswald, Anton, Bebas Neue (Google Fonts) — caption families — SIL Open Font License 1.1.
Roboto (Google Fonts) — caption family — Apache License 2.0.