DocumentationReferenceUsing the CLIStoring data permanently

Storing data permanently

By default, any data that have been created by your application will be destroyed once you run wolkenkit stop. This is great for development, but not for production. In production, you will want to store data permanently.

To enable permanent data storage, provide the --persist flag when starting the application using wolkenkit start. Please note that you also have to set a shared key. Now all of your application's data will be permanently stored and hence survive a restart of your application:

$ wolkenkit start --shared-key <secret> --persist

Beware of environment variables

If you use a shared key with special characters, it might contain the $ sign. Since this character is used by the command line to access environment variables, unexpected things could happen. To avoid this, enclose the shared key in single quotes.

Restarting an application

When you restart an application, the CLI takes care of preserving the shared key between restarts. Hence you can simply run:

$ wolkenkit restart

This is not true when stopping and then starting your application. In this case you explicitly need to provide the very same shared key again, otherwise you won't be able to access your previously stored data:

$ wolkenkit stop
$ wolkenkit start --shared-key <secret> --persist

Destroying stored data

In case you need to destroy your stored data, provide the --dangerously-destroy-data flag to the start, stop, or restart command:

$ wolkenkit stop --dangerously-destroy-data