Skip to content
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

Open
navy1997 opened this issue Dec 20, 2024 · 5 comments
Open

About hoverfly configuration persistence #1163

navy1997 opened this issue Dec 20, 2024 · 5 comments

Comments

@navy1997
Copy link

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

@navy1997
Copy link
Author

I tried to start boltdb. But after restarting, I found that the configuration I wrote was empty again.
1734682543261

@tommysitu
Copy link
Member

I don't think hoverfly supports config persistence. You may want to try out https://hoverfly.io/hoverfly-cloud

@navy1997
Copy link
Author

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?

@tommysitu
Copy link
Member

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.

@navy1997
Copy link
Author

simulation data

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants