You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using the jsoncrack the last few days and it is really helpful, as I want to add it to multiple colleagues in my team, I wondered if the image can be pushed in a docker registry to be accessed each time for a more easy and quick installation to multiple enviroments etc. If this request doesn't align or in any way doesn't comply with your workflow please feel free to close it.
Alternative solutions or implementations
No response
Other context
Found that link in docker hub, but it doesn't seem to load or work. Also I have searched in docker hub via the app and found this: shokohsc/jsoncrack, if this is the correct up to date container please include it if possible in README.md
The text was updated successfully, but these errors were encountered:
I don't have trouble running it locally and the commands given in README.md for container they do work (and this is how now i deploy it). But it would be a good feature to be in a universal registry up to date in order to use it more easily in multiple envs.
Uh oh!
There was an error while loading. Please reload this page.
Feature
Hello everyone,
I have been using the jsoncrack the last few days and it is really helpful, as I want to add it to multiple colleagues in my team, I wondered if the image can be pushed in a docker registry to be accessed each time for a more easy and quick installation to multiple enviroments etc. If this request doesn't align or in any way doesn't comply with your workflow please feel free to close it.
Alternative solutions or implementations
No response
Other context
Found that link in docker hub, but it doesn't seem to load or work. Also I have searched in docker hub via the app and found this: shokohsc/jsoncrack, if this is the correct up to date container please include it if possible in README.md
The text was updated successfully, but these errors were encountered: