Updating Konkat

Install a new Konkat release on the server: replace the app folder, migrate, clear the cache and restart — and what users see afterwards.

ForSystem administrator

On this page

Before you update
Update steps
What users see
Checking the update
If something goes wrong
Common questions

Updating Konkat means putting the new release’s files on the server and letting Frappe apply any database changes. It takes a few minutes and users don’t need to reinstall anything on their phones.

Before you update#

Back up — bench --site <site> backup --with-files. Keep a copy of the current apps/konkat folder too, so you can go back if needed.
Pick a quiet time — after site hours or at lunch. Saving is interrupted for a minute or two during the restart.
Read the release notes if the release comes with them.

Update steps#

Run these from the bench folder as the bench user. They are examples; replace <site> with your site name.

Replace the app files — if you installed from Git: cd apps/konkat && git pull && cd ../... If you use release zips: move the old apps/konkat folder aside (for example to ~/konkat-old) and unzip the new release so that apps/konkat is the new version.
Migrate — bench --site <site> migrate. This applies new or changed data structures and any one-time fixes in the release. It is only strictly needed when the release changed doctypes, but it is always safe to run, so run it every time.
Clear the cache — bench --site <site> clear-cache
Restart — bench restart

No bench build is needed. The Konkat page reads its screen files directly from apps/konkat/konkat/spa/, so new screens are live as soon as the files are in place and the cache is cleared.

If you installed several sites with Konkat on the same bench, run migrate and clear-cache for each site (or use bench --site all migrate).

What users see#

The build number changes with every release. You can see it at the bottom of the left menu (under the user’s name) and at the bottom of the More sheet on a phone.

On https:// addresses — the app checks for a new version when it opens and every 30 minutes. When it finds one, a bar says “A new version of Konkat is ready.” with a Reload button. Pressing Reload switches to the new version straight away.
On http:// addresses — there is no bar. The new version loads the next time the person reloads the page or reopens the browser.

After an update, send your team a one-line message: “Konkat was updated — if you see a Reload bar, tap it.” Ask them to finish and save any open form first.

Checking the update#

Open /konkat — the build number at the bottom of the left menu should be new.
Open a few screens — dashboard, plan, a task, the daily log.
Save something small — for example a test snapshot on a test task, then delete it.
Open a report as PDF.

If something goes wrong#

Screens look old — run clear-cache again and ask the person to reload (or tap Reload on the bar). See Troubleshooting.
migrate fails — read the error, fix it (often a full disk or a stopped database) and run migrate again. It is safe to repeat.
You need to go back — put the old apps/konkat folder back, restore the backup taken before the update (bench --site <site> restore <backup-file>), clear the cache and restart. Anything recorded after the backup is lost, so only do this if the new version can’t be fixed.

Common questions#

Do people need to reinstall the phone app?#

No. The installed app always loads from your server, so it updates itself.

Will data be lost?#

No. Updates add and change structures but keep your records. That’s why the backup is a precaution, not a step you expect to need.

Does updating Frappe or ERPNext affect Konkat?#

Konkat needs Frappe v15. Minor v15 updates (bench update) are fine. Don’t move the bench to a different major Frappe version unless the Konkat release says it supports it.