I have a Ruby .deb package that I built from source using checkinstall. I'm using it with a Chef recipe to install Ruby on one of my nodes. Right now I'm storing it under files/default
in my recipe, where one would normally store config files or templates to upload to the server. This works well enough but I wonder what the "right" way to solve this problem would be. Where do people store local binaries or packages when they want to install them with Chef this way? Should I create a server to store these, then download them as needed through my recipes?
相关问题
- Error when installing TDA package on R
- installing packages for python 3
- How do I build a debian package whose sources incl
- Is there a way to recreate an ODI package using OD
- Command errored out with exit status 1: python set
相关文章
- unable to install packages(“caret”) completely in
- PHP friend/package visibility
- Ubuntu graphviz 'sfdp' not working
- Roxygen2 - how to @export reference class generato
- Change default package from com.example for Eclips
- Exclude data sets from R package build
- R: Having trouble installing rpanel
- Recipe for making Cocoa NSDocument packages play w
Ideally you would host a repository server like apt (or gem, etc. Whatever suits) and configure your repository sources on chef clients to include that server.