RefractTrack Upgrading - Revision history

Nerdofepic: Created page with "== Upgrading == This page covers moving an existing, already-installed RefractTrack up to a newer version. If you're setting RefractTrack up for the very first time, you want Getting Started instead. Upgrading is a files-only operation — it never touches your database directly. Your projects, tasks, users, uploaded attachments, and settings are never copied over or replaced, since the new files simply sit down next to config/ 2026-09-11T22:33:54Z Created page with "== Upgrading == This page covers moving an existing, already-installed RefractTrack up to a newer version. If you're setting RefractTrack up for the very first time, you want Getting Started instead. Upgrading is a files-only operation — it never touches your database directly. Your projects, tasks, users, uploaded attachments, and settings are never copied over or replaced, since the new files simply sit down next to <code>config/</c..." New page == Upgrading == This page covers moving an existing, already-installed RefractTrack up to a newer version. If you're setting RefractTrack up for the very first time, you want [[RefractTrack_Getting_Started|Getting Started]] instead. Upgrading is a files-only operation — it never touches your database directly. Your projects, tasks, users, uploaded attachments, and settings are never copied over or replaced, since the new files simply sit down next to <code>config/</code> and <code>uploads/</code> without touching either. If the new version needs anything to change about the ''shape'' of the database (a new column, for example), that's handled separately, automatically, the next time an admin logs in — see [[#Database updates|Database updates]] below. === The upgrade script === Every RefractTrack download includes an <code>upgrade.sh</code> script for this, in two places: * <code>refracttrack/scripts/upgrade.sh</code> — a short, no-questions-asked version for people comfortable typing a path or two on the command line. * <code>refracttrack_server/upgrade.sh</code> — a guided, prompt-you-for-everything version of the same thing, better if you'd rather not have to remember exact paths. Both do exactly the same underlying copy, and it's safe to use either one — pick whichever fits how you like to work. This page walks through the guided version, since it explains itself as it goes. '''You'll need root (administrator) access on the server to run either one''' — the live install is normally owned by the web server's own account (commonly <code>www-data</code>), and only root can safely copy files into it while preserving that ownership. ==== Running it ==== # Download the new version and unzip it, the same way you did the first time — you should end up with a <code>refracttrack/</code> folder and a <code>refracttrack_server/</code> folder sitting next to each other. # From that location, run <code>refracttrack_server/upgrade.sh</code> as root. # It'll ask where the new code is (it defaults to the sibling <code>refracttrack/</code> folder it just found, so you can usually just press enter). # It'll ask where your ''live'' install is. It tries to find this for you automatically by scanning your Apache configuration for a site that already looks like a RefractTrack install — if it finds exactly one, it'll offer that as the default. If it finds none, or more than one, it'll just ask you to type or paste the path. # It shows you a preview of exactly what would change — every file that would be added, replaced, or removed — before it asks you to confirm anything. Nothing is copied yet at this point, so it's a safe point to stop and double-check if something looks off. # Once you confirm, it copies the new files over, '''deliberately skipping your <code>config/</code> folder and your <code>uploads/</code> folder entirely''' — your database credentials and every attachment your team has ever uploaded are untouched, by construction. # It offers to fix up file ownership on the newly-copied files to match whatever your live install was already using, so you don't end up with a permissions headache afterward. That's it — no database step, no restart to remember, no service to bounce. === Database updates === Some versions of RefractTrack add something new to the database itself, not just to the application code — a new column to support a new feature, for example. When that happens, upgrading the files alone isn't quite the whole story, but you don't need to do anything special for it either: * The moment an admin next logs in after the file upgrade, RefractTrack notices the database is a step behind the code and automatically walks them through a one-click "Apply Update" screen. It's quick, safe to run more than once if you're not sure whether it already ran, and doesn't require any command-line work. * Everyone else just sees a brief "please wait, an update is being applied" message for the short window before an admin gets to that screen — nobody is locked out, and nothing is lost. * If you'd rather trigger this from the command line as part of a deploy script instead of waiting for someone to click through a web page, there's a CLI equivalent: <code>php scripts/migrate.php</code>, run from inside the <code>refracttrack/</code> folder. It's safe to run this even if there's nothing pending (it just does nothing), and it's safe to run at the same time someone else happens to click through the web version — they won't step on each other. Because the file copy and the database update are two separate, independent steps, there's a brief window right after a file upgrade where the newly-copied code is running against an old-shaped database. RefractTrack is built to tolerate this gracefully rather than error out — but it's still worth getting an admin to log in (and click through the update screen, if one appears) soon after upgrading, rather than leaving it for days. === A quick note for older installs === If your install has been running for a long time without ever having the <code>php-zip</code> PHP extension (needed for the [[RefractTrack_Export_and_Import|zip backup system]]), an upgrade won't install it for you automatically — upgrading is deliberately files-only and never touches installed system packages. If project backups stop working after an upgrade, that's the first thing to check with your host (<code>apt-get install php-zip</code> on a Debian/Ubuntu server, then a reload of PHP/Apache, is normally all it takes). === Related pages === * [[RefractTrack_Getting_Started|Getting Started]] * [[RefractTrack_Automated_Server_Setup|Automated Server Setup]] * [[RefractTrack_Export_and_Import|Export and Import]] [[Category:RefractTrack]]