> 🚧 If you run into any issues upgrading... > > Please check the **[Common Issues > Installation/Upgrading Issues](/docs/installation-issues)** section which provides solutions for commonly encountered installation / upgrading problems. **Always backup your database and .env file before upgrading.** We try very hard to make sure that all database changes are non-destructive, but you should always backup beforehand anyway. You will never regret backing up your database. You may regret not doing so, so it’s just better to get into the habit. ## Upgrading via Git > ❗️ Caution > > For some reason, Github's built-in redirect from snipe/snipe-it to grokability/snipe-it has stopped working. If you're trying to upgrade or pull and you get a "not found" response or a login prompt from Github, do the following to set your origin to the correct Github URL: {` $ git remote remove origin $ git remote add origin https://github.com/grokability/snipe-it `} If you installed Snipe-IT via Git (which is our recommended method - seriously, we really, really recommend it), updating Snipe-IT should be pretty straightforward. Simply pull down the newest release (using `git pull`) and run whatever commands the release notes specify. Your configuration won’t be overwritten, since the `.env` file isn't checked into version control. Upgrading should be as simple as running: {` # Do a git pull to get the latest version of version.php $ git pull # run the upgrade $ php upgrade.php `} from your Snipe-IT project root. That will attempt to: * check your installed PHP libraries to confirm you have all of the required libraries installed * run a backup * put your Snipe-IT into maintenance mode * `git pull` * clear your application caches * run `composer install --no-dev` * run database migrations * checks for OAuth keys * checks your directory permissions * takes the database out of maintenance mode # Upgrading to a Specific Tag or Branch To upgrade to a specific tag or branch, pass it along using the `--branch` argument. (Yes, even for tags.) {` # run the upgrade to a specific tag $ php upgrade.php --branch tags/v8.3.0 `} or to a specific branch: {` # run the upgrade to a specific tag $ php upgrade.php --branch develop `} If you're not upgrading via git, you can still use the upgrade script, but it won't be able to download the new files, and will just try to run the backups, clear caches, etc. ## Upgrading Manually Upgrading manually is unfortunately much more labor intensive (which is why we strongly recommend installing via git instead.) The most straightforward way to do this is to rename your current Snipe-IT directory (for example, to `snipe-it-v3-bkup`) and download the new version into a parallel directory that you name whatever your old one was named. (Keeping the same name for the new version just means you don't have to mess with the web server path settings.) From there, copy over the old `.env` and your OAuth keys in `storage`, as well as any files or folders in your `public/uploads` directory and your `storage/private_uploads` directory. If you wish to switch to upgrading via Git, now is a good time to do that. For instructions on how to switch from a manual install to a Git install, [click here](doc:switching-to-a-git-install). ## After Pulling the New Version Files Whenever you pull down a new version from `master` or `develop`, or when you grab the latest official release, make sure to run the following commands via command line: {` # Get the latest files $ git pull # Get the latest vendor files via composer $ php composer.phar install --no-dev --prefer-source # Clear any composer caches $ php composer.phar dump-autoload # Run database migrations $ php artisan migrate # Clear previously cached app settings and files $ php artisan config:clear $ php artisan route:clear $ php artisan cache:clear $ php artisan view:clear `}
(Developers should remove the `--no-dev` flag, so they have unit test frameworks and debugging tools.) Forgetting to run these commands can mean your DB might end up out of sync with the new files you just pulled, or you may have some funky cached autoloader values. It’s a good idea to get into the habit of running these every time you pull anything new down. If there are no database changes to migrate, it won't hurt anything to run migrations anyway, you’ll just see "Nothing to migrate". If you have any issues upgrading, check the [Common Issues](doc:common-issues) page for a fix. If you don’t see your issue listed there, [open an issue on Github](https://github.com/snipe/snipe-it/issues) and we’ll try to get you sorted out. Be sure to provide the information outlined in the [Getting Help](doc:getting-help) section of this site so that we have the info we need to assist you.