Update guide¶
Table of contents
Prerequisites¶
Artifacts¶
KissLog.Backend-{version}-linux-x64.zip
KissLog.Frontend-{version}-linux-x64.zip
Artifacts can be downloaded from https://github.com/KissLog-net/KissLog-server.
Update the applications¶
Repeat the steps below for both of the App Services. Start with KissLog.Backend followed by KissLog.Frontend.
1. Download the existing configuration file¶
Navigate on the App Service overview page. On the left menu under “Development Tools”, click on the “Advanced Tools”, then click on the “Go” link. This will open the Azure Kudu service.
Once on the Kudu service, navigate to the application files by clicking on “Site wwwroot” link.
The configuration file is located under Configuration/KissLog.json
. Copy this file locally.


2. Update the configuration file¶
Apply the configuration changes (if any) by updating KissLog.json file.
The configuration changes will be listed in the change log.
3. Prepare the artifacts¶
Download the KissLog server package from here.
Extract the archive in a folder. Then, extract both of the resulting archives in two separate folders: KissLog.Backend and KissLog.Frontend.
Replace the KissLog.Backend\Configuration\KissLog.json
with the existing configuration file.
Create a zip
archive with the contents of the KissLog.Backend folder.
4. Upload the new code¶
Make sure the App Service is stopped before uploading the new code.
Navigate to KissLog.Backend App Service. On top right, click on “Download publish profile” button. Open the downloaded file and copy the userName
and the userPWD
.

https://<app_name>.scm.azurewebsites.net/api/zipdeploy
.curl -X POST -u $kisslog-backend-code:{password} --data-binary @"<zip_file_path>" https://kisslog-backend-code.scm.azurewebsites.net/api/zipdeploy
If the update was successful, you will receive a 200 OK
response status code.
The new code can also be deployed with Postman.


5. Run the KissLog.Backend App Service¶
After KissLog.Backend App Service has been updated, start the App Service then browse to the application URL.
If everything went successful, you will see the KissLog.Backend home page.
Note

6. Repeat the steps above for KissLog.Frontend¶
Repeat the steps above for the KissLog.Frontend App Service, starting with step 1.