InfyHMS - SAAS

# Upgrade Guide

Before starting upgrade we recommenced to backup your files and export your current database.

NOTE : If you are non-technical person then please use dist.zip to replace files and if you are technical person then use src.zip

# Upgrade to latest version

# Prerequisite


Before starting upgrade we recommend to back up your all files and export your current database.
so in case if anything goes wrong, you can restore the previous version.

  • Backup your whole folder
  • Backup & Export your database via phpymadmin

# Backup Sensitive Files and Folders


Backup the following folders and files.
  • File - .env
  • Folder - Any new languages that you added in - resources/lang/
  • Folder - public/uploads/

# Replace the latest code


  • Delete all your existing code (you can also rename the current folder or move all content to some other folder, if possible)
  • Upload the latest dist.zip to the server
  • Extract the zip
  • Put old .env file back
  • Put resources/lang/ and public/uploads folder back (or you can merge)
  • Edit .env and change UPGRADE_MODE=true
  • Run a database upgrade script https://{YOUR_URL}/upgrade/database
  • Edit .env and change UPGRADE_MODE=false
  • Verify that latest version is visible in footer
Check everything is working fine.

# Upgrade to oldest version

# Upgrading from v3.2.1 to v3.3.1

# For Technical Users:

  • Download v3.3.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v3.3.1 files into your existing version v3.2.1
  • That's it!, you are ready to go with new version v3.3.1

# For Non Technical Users:

  • Download v3.3.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v3.3.1 files/directories into your existing version v3.2.1
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade/database to update your database
  • That's it!, you are ready to go with new version v3.3.1

# Upgrading from v3.2.0 to v3.2.1

# For Technical Users:

  • Download v3.2.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v3.2.1 files into your existing version v3.2.0
  • That's it!, you are ready to go with new version v3.2.1

# For Non Technical Users:

  • Download v3.2.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v3.2.1 files/directories into your existing version v3.2.0
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade-to-v3-2-1 to update your database
  • That's it!, you are ready to go with new version v3.2.1

# Upgrading from v3.1.0 to v3.2.0

# For Technical Users:

  • Download v3.2.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v3.2.0 files into your existing version v3.1.0
  • That's it!, you are ready to go with new version v3.2.0

# For Non Technical Users:

  • Download v3.2.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v3.2.0 files/directories into your existing version v3.1.0
  • That's it!, you are ready to go with new version v3.2.0

# Upgrading from v3.0.0 to v3.1.0

# For Technical Users:

  • Download v3.1.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v3.1.0 files into your existing version v3.0.0
  • That's it!, you are ready to go with new version v3.1.0

# For Non Technical Users:

  • Download v3.1.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v3.1.0 files/directories into your existing version v3.0.0
  • That's it!, you are ready to go with new version v3.1.0

# Upgrading from v2.1.0 to v3.0.0

# For Technical Users:

  • Download v3.0.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v3.0.0 files into your existing version v2.1.0
  • That's it!, you are ready to go with new version v3.0.0

# For Non Technical Users:

  • Download v3.0.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v3.0.0 files/directories into your existing version v2.1.0
  • That's it!, you are ready to go with new version v3.0.0

# Upgrading from v2.0.1 to v2.1.0

# For Technical Users:

  • Download v2.1.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v2.1.0 files into your existing version v2.0.1
  • That's it!, you are ready to go with new version v2.1.0

# For Non Technical Users:

  • Download v2.1.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v2.1.0 files/directories into your existing version v2.0.1
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade-to-v2-1-0 to update your database
  • That's it!, you are ready to go with new version v2.1.0

# Upgrading from v2.0.0 to v2.0.1

# For Technical Users:

  • Download v2.0.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v2.0.1 files into your existing version v2.0.0
  • That's it!, you are ready to go with new version v2.0.1

# For Non Technical Users:

  • Download v2.0.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v2.0.1 files/directories into your existing version v2.0.0
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade-to-v2-0-1 to update your database
  • That's it!, you are ready to go with new version v2.0.1

# Upgrading from v1.2.0 to v2.0.0

# For Technical Users:

  • Download v2.0.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v2.0.0 files into your existing version v1.2.0
  • That's it!, you are ready to go with new version v2.0.0

# For Non Technical Users:

  • Download v2.0.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v2.0.0 files/directories into your existing version v1.2.0
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade-to-v2-0-0 to update your database
  • That's it!, you are ready to go with new version v2.0.0

# Upgrading from v1.1.1 to v1.2.0

# For Technical Users:

  • Download v1.2.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • Run php artisan migrate to run migrations
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v1.2.0 files into your existing version v1.1.1
  • That's it!, you are ready to go with new version v1.2.0

# For Non Technical Users:

  • Download v1.2.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v1.2.0 files/directories into your existing version v1.1.1
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade-to-v1-2-0 to update your database
  • That's it!, you are ready to go with new version v1.2.0

# Upgrading from v1.1.0 to v1.1.1

# For Technical Users:

  • Download v1.1.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Run composer install to update composer dependencies
  • And Run php artisan db:seed --class=AddFieldSubscriptionPlanFeaturesTableSeeder to make new build
  • And Run npm install to make new build
  • And at last Run npm run dev to make new build
  • Replace v1.1.1 files into your existing version v1.1.0
  • That's it!, you are ready to go with new version v1.1.1

# For Non Technical Users:

  • Download v1.1.1
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v1.1.1 files/directories into your existing version v1.1.0
  • NOW PLEASE CALL THIS URL ONCE YOUR APPURL/upgrade-to-v1-1-1 to update your database
  • That's it!, you are ready to go with new version v1.1.1

# Upgrading from v1.0.0 to v1.1.0

# For Technical Users:

  • Download v1.1.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v1.1.0 files into your existing version v1.0.0
  • That's it!, you are ready to go with new version v1.1.0

# For Non Technical Users:

  • Download v1.1.0
  • Backup your current version files and DB
  • If you have manually changed any files then please take a backup of them. After replacing files, you can again get that portion of code into some particular files.
  • Replace v1.1.0 files/directories into your existing version v1.0.0
  • That's it!, you are ready to go with new version v1.1.0

As its version v1.1.0, there is no upgrade guide provided.