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
Instead of importing homebrew from local files, the container should pull homebrew from a list of URLs at start up and generate it's own index.json.
All homebrew I'm aware of is available on Github. This would make updating homebrew files automatic, and would solve issues with permissions / overwriting local files.
The text was updated successfully, but these errors were encountered:
This is a great idea and I have finally gotten around to an overhaul of this project.
A comma-separated list of URLs in an ENV var would be great. Shouldn't be too hard to implement either.
Fixing the permissions / overwriting issue will come down to switching from cloning/updating the git repo to grabbing tagged releases and throwing homebrew files in after.
I don't think there's a built-in way to automatically pull homebrew via URL. Of course you can do it on the site. If you know of a way to handle that without any local files, I'm happy to implement it.
Otherwise, I think I'll be deploying the site, then grabbing homebrew content from local files (via host volume maps) and remote (via list of URLs in ENV var).
Instead of importing homebrew from local files, the container should pull homebrew from a list of URLs at start up and generate it's own index.json.
All homebrew I'm aware of is available on Github. This would make updating homebrew files automatic, and would solve issues with permissions / overwriting local files.
The text was updated successfully, but these errors were encountered: