-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About hoverfly configuration persistence #1163
Comments
I don't think hoverfly supports config persistence. You may want to try out https://hoverfly.io/hoverfly-cloud |
If I want hoverfly to restart without losing my previously configured request config, is it not supported? |
oh you meant the simulation data? You can export it into a json file before you shut down hoverfly, and import it in again after a restart. |
Yes, it is simulated data. Doesn't the -db parameter mean writing the configuration to disk? I specify the db path when I restart, and then read the previous configuration. It seems that it is not supported at present. |
Does hoverfly support configuration persistence? If we need to make hoverfly into multiple copies, if there is no data persistence, it seems that we need to create the configuration of each copy
The text was updated successfully, but these errors were encountered: