-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Create data directory to improve k8s convenience #123
Conversation
By the way, why setting loop to false in Docker file? |
The docker fork isn't mine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think having a subdir for each file is a bit excessive (for now), but having a data
folder seems indeed like a good idea.
I did it because the image is intended to be run only once a week, suitable for many services offering on-demand trigger or simply a crontab. For user who wants to trigger it once per week, to disable the loop we will need to implement a bit more to the code base. Maybe I will create a PR for a better way to disable/enable the loop via env var. If user wants to use via k8s, they can override the config file anyway so I think this is currently the best option. |
00d6f11
to
a1d1665
Compare
I see. Sorry I didn't understand the design here at first. So I can actually run this container directly in k8s using CronJob instead of Deployment. Thanks! |
Thanks for the PR! Accepted! Now, todo:
|
I have finished the wiki update. Could you please double check it now? |
https://github.com/Revadike/epicgames-freebies-claimer/wiki/Installation-(Prerequisites) is missing the device_auth.json should be moved to /data |
Added 😄 |
I will update wiki for Docker version in next version. For now we are still at 1.5.3, new file structure will be updated in 1.5.4. |
Yes |
Because k8s can only mount config map or secret as directory, it will override all files in the same directory of config file. So I move each config to it's own folder so anyone who want to run the docker image on k8s can simply mount the config folder without affect anything else.