Update guide¶
Table of contents
Artifacts¶
KissLog.Backend-{version}-win-x64.zip
KissLog.Frontend-{version}-win-x64.zip
Artifacts can be downloaded from https://github.com/KissLog-net/KissLog-server.
Update steps¶
Stop both IIS applications:
KissLog.Backend
KissLog.Frontend
Create backup¶
Create a backup of the existing IIS application folders.
\Backups ├── KissLog.Frontend\ └── KissLog.Backend\
Copy new files¶
Delete from the KissLog.Backend folder everything but:
\KissLog.Backend ├── Configuration\ ├── appsettings.json └── web.config
Delete from the KissLog.Frontend folder everything but:
\KissLog.Frontend ├── _kisslogMedia\ ├── Configuration\ ├── appsettings.json └── web.config
Extract the contents of
KissLog.Backend.AspNetCore.zip
to KissLog.Backend folder.Choose not to override the existing files (keep the local files).
Extract the contents of
KissLog.Frontend.AspNetCore.zip
to KissLog.Frontend folder.Choose not to override the existing files (keep the local files).
Update KissLog.Backend configuration¶
Apply the configuration changes (if any) by updating KissLog.json file.
The configuration changes will be listed in the change log.
Update KissLog.Frontend configuration¶
Apply the configuration changes (if any) by updating KissLog.json file.
The configuration changes will be listed in the change log.
Change/increment the value of
"StaticResourcesVersion"
property fromKissLog.json
file.This will refresh the browser cache for static resources.
C:\inetpub\wwwroot\KissLog.Frontend\Configuration\KissLog.json¶{ "ApplicationName": "KissLog", "StaticResourcesVersion": "any-new-value" }
Start the applications¶
Restart the IIS applications:
KissLog.Backend
KissLog.Frontend
Make a single request to KissLog.Backend root URL (“http://kisslog-backend.your_domain.com”)
If everything went successful, you will see the KissLog.Backend home page.
Make a single request to the KissLog.Frontend root URL (“http://kisslog-frontend.your_domain.com”).
If the startup process went successful, you will see the home page.