DocumentationChapter 09 of 14
09Updating to a new version
When a new version comes out, download it from CodeCanyon. Read CHANGELOG.md to see what changed. Then follow these steps.
- Back up the database and the
App_Datafolder. With SQLite, the database is in theApp_Datafolder. See Backups. - Stop the app. IIS: stop the MaintDock site and its application pool. Linux:
sudo systemctl stop maintdock. Docker:docker compose down. - Copy the new binaries over the old ones. Do not delete the
App_Datafolder: it holds your setup, files, and keys, and the SQLite database. Keep your own translation files. If you changedappsettings.jsonby hand, make the same change in the new file.Windows (Command Prompt)robocopy "C:\path\to\new\binaries" "C:\inetpub\maintdock" /E /XD App_DataLinuxDocker: replace the files in yoursudo rsync -a --exclude App_Data binaries/ /var/www/maintdock/ sudo chown -R www-data:www-data /var/www/maintdocksourcefolder with the new ones, but keep your changeddocker-compose.yml. Then rundocker compose build. - Start the app. IIS: start the application pool and the site. Linux:
sudo systemctl start maintdock. Docker:docker compose up -d. MaintDock updates the database tables by itself when it starts. - Open MaintDock and sign in. If you use your own language file, compare it with the new
template.json(see Translate the app).
If you changed the code
Put your changes into the new source code before you publish. A version control system such as Git makes this much easier: keep the original code in one branch and your changes in another.
If the setup wizard shows after an update, the App_Data folder was deleted or moved. Stop the app, put the folder back from your backup, and start the app again.