-
Notifications
You must be signed in to change notification settings - Fork 9
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
Overwriting my homebrew index.json on container start. #11
Comments
Yeah, this is an issue I've been dealing with in my personal instance as well. I'm not sure what the best approach is to dealing with it, since we're essentially introducing a "patch" to the main 5eT code when we add homebrew. I can think of two approaches, but there is probably an optimal solution I just don't know about.
If you've worked out a solution in the last three months, I'd love to hear it. Otherwise, I'll see what I can do. |
Not really, since iam not that familiar with git. My solution is kinda dumb. I made a script that restarts the container once a week to update and then replace the index.json with a saved one. |
I think the simplest solution would be to list all The problem would be if the user renames/deletes a file or something similar and does not restart the server. Manipulating |
I am attempting to do the same but I don't seem to be able get any homebrew to load at all. I restart the container, copy back my index.json, correct the permissions and I get nothing showing up in 5eTools. Is there another step necessary here? I am seeing an error here, not sure if it's the source of my issue:
It would be great if we could load homebrew from URLs instead of files, so that restarting the container also re-pulls homebrew and generates an index.json file instead of managing these files locally. |
@oakbrad I like that idea. If you open a feature request for that, I'll get around to building it out. |
Hi since i think the last update, every time i restart the container it "updates" my homebrew index.json file back to the original empty one from the repository.
The text was updated successfully, but these errors were encountered: