Export

Your application belongs to you, with its data. Two commands hand you a copy at any time: the code alone, or the whole application, ready to run somewhere other than Kedalia.

On this page

Where to find them

In the application's “Settings” tab, “Code” section, or in the “…” menu of its line on the “Applications” page: in the settings, “Download the code only” and “Export everything”; in the menu, “Download the code only” and “Export everything (code, history, data, guide)”. While the application is not running, the export is greyed out, with “Available while the application runs: its data is read from it”. The same export is offered before you delete an application: “Export first”. An application paused by your tier is exported whole too: see A paused application.

Download the code only

“Download the code only” saves, within a few seconds, a ZIP file named after the application. It holds the application's code as it is today, in a folder with its name. It holds neither the data nor the history of the changes: for those, export.

Export everything

“Export everything” hands it to you whole, in a ZIP file:

  • the full history of the code;
  • the database, that is everything your users have entered;
  • a redeployment guide, which restarts the whole thing elsewhere with a single command; sending e-mails resumes as soon as you configure your own server there.

The export reads the data where the application runs: it is only available while the application is running. While it downloads, the card says so under its dates: “Downloading the code…” or “Exporting: the database is being read, this can take a minute…”. If it fails, the card gives the reason there, in red, when Kedalia knows it, for example “The application is stopped: export its data once it has restarted. Its code can still be downloaded.” Otherwise it says “The export failed. Try again.”.

A paused application

An application paused because your tier no longer counts it (a change of tier, a cancellation) no longer runs: instead of “Export everything”, it offers “Prepare the full export”. Kedalia restarts it for a few minutes, the time to read its database and its documents, then pauses it again: it does not count in your tier meanwhile. The card says “Export being prepared…”; one application at a time is restarted per organisation.

Once the export is ready, “Download the export” saves the same ZIP file as “Export everything”, as many times as you like, until the date “Available until” gives: 7 days, after which it is erased from our servers, as it is as soon as the application is restarted or deleted. If the preparation fails, the application is paused again and the card says “The export did not complete: start it again.”.

Only a version of the application that passed its checks is restarted. Otherwise Kedalia answers “This application’s latest version did not pass its checks: it cannot be restarted, not even to export it. Its code can still be downloaded.”

An application whose code stays on GitHub is never restarted by Kedalia: paused, it only has its code. Write to us for its data.

Signing in to the copy

The exported copy does not depend on Kedalia: signing in with Kedalia does not work there, you sign in with a password. So choose a password of the application's own, on its account page, before you need it: that is the one that works if you export it. The redeployment guide explains how to sign in.

Before deleting an application

Deleting an application cannot be undone. The delete window lists what goes: its code and its history, its data, its address and its custom domains, its test versions, its conversations with the assistant, its Kanban and its cards. An application whose code stays on GitHub keeps it there: only its test versions' work there is deleted. The window reminds you, “Export the application first to keep a copy.”, and offers “Export first”. Then type the application's name to confirm: the “Delete” button is red.

If you leave, or if Kedalia stops

You export your applications whenever you like, up to 30 days after you leave: they then run elsewhere, without Kedalia, on any server. If Kedalia stopped being operated, every customer would be warned by e-mail and invited to export their applications: the delay is given in the legal notice.

After a cancellation, your applications are all stopped and your organisation is locked, but the “Subscription” page lists your applications until the 30th day: “Download the code only” and “Prepare the full export” (code and history, database, documents) for each one (A paused application). Only the organisation's administrators have access.