Running Interactsh ephemerally / on demand #314
Closed
Bwvolleyball
started this conversation in
Ideas
Replies: 1 comment
-
Closing 1.5 year old issue. Feel free to reopen if needed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Please describe your feature request:
Add the ability / option to persist runtime state (certificates, DNS names, static IP addresses, hits) externally
Describe the use case of this feature:
In a situation where a user wants to run interactsh as an on demand or scale-to-0 application, having all runtime state persisted externally (to an external cache such, or to an external file system for certificates), would allow for running interactsh on Kubernetes / Knative and allow for quick and consistent reboots of interactsh, in the event the application is scaled down between runs, or a pod died and was rescheduled.
Beta Was this translation helpful? Give feedback.
All reactions