Comments (8)
I haven't tested the master branch yet on 2.8, There should be no reason it doesnt.
Try giving the 2.0.0_wip branch a try. It's stabilized pretty well, I just wanted to add features before I released it.
from redisio.
I will test out 2.8 on master branch as soon as I can.
from redisio.
Wow you are quick, thanks :) I ran the two recipes separately, that is what was causing redisio::enable to fail
chef-solo -c /etc/chef/solo.rb -o "recipe[redisio::install],recipe[redisio::enable]"
I * service[redis6379] action start
- start service service[redis6379]
- service[redis6379] action enable
- enable service service[redis6379]
it look like it is working!
from redisio.
Which branch is this? So generally if enable fails with the .each error, it means that the redisio['servers'] option is nil (as it can't call .each on NilClass). The servers attribute shoudl be set in the configure recipe (in the 2.0.0 wip branch). In the master branch I believe it gets set in the install recipe.
from redisio.
master branch. I just did a "git clone https://github.com/brianbianco/redisio.git" a few minutes ago.
So to be clear.. If I run recipes seperately like this;
chef-solo -c /etc/chef/solo.rb -o "recipe[redisio::install]"
chef-solo -c /etc/chef/solo.rb -o "recipe[redisio::enable]"
Install will succeed and enable will fail with above mentioned error. This works -> chef-solo -c /etc/chef/solo.rb -o "recipe[redisio::install],recipe[redisio::enable]"
Just have to edit the mirror url and version.
#Tarball and download related defaults
default['redisio']['mirror'] = "http://download.redis.io/releases"
default['redisio']['base_name'] = 'redis-'
default['redisio']['artifact_type'] = 'tar.gz'
default['redisio']['version'] = '2.8.0-rc6'
default['redisio']['base_piddir'] = '/var/run/redis'
from redisio.
Is 2.00 WIP stable enough to use? I didnt see it at first. Thanks
from redisio.
Yeah sorry, so to be more clear what I was trying to say was:
In any given Chef run, the install recipe must be in the run list before enable.
I haven't updated the download mirror, because unfortunately, only the newer versions are available on redis.io. All old versions still reside on google code. (including the version that it currently defaults to).
I personally have been using the 2.0.0_wip branch without any issue. I know there are a couple other people out there using it as well. You should certainly test it first, I would also lock yourself into a particular commit version and not into HEAD (as if I update head things COULD potentially break although I take care to try not to do this).
The recipes are moved around a bit as well. You should be able to do a run list like the following:
chef-solo -c /etc/chef/solo.rb -o "recipe[redisio],recipe[redisio::enable]"
from redisio.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
from redisio.
Related Issues (20)
- Add protected-mode in sentinel.conf HOT 2
- issue with changing config because attributes saved as node.normal HOT 2
- undefined method `selinux_policy_install' HOT 2
- Dangerfile should use failure instead of fail HOT 1
- Remove .rubocop.yml with Dangerfile HOT 1
- Update Changelog HOT 2
- Run latest cookstyle HOT 2
- Update builds to be parallel HOT 2
- redis.conf.erb version checks incorrectly on some sections
- Chef 16+ user_ulimit warning message HOT 1
- Fix all checks so they pass
- rename_commands not populating rename-command
- SELinux: Redis server running unconfined when installed from sources HOT 1
- After OS restart, redis listens only on loopback HOT 1
- Redis service should be restarted when installing a new version
- Missing required sentinel parameter master_ip
- WARNING: Sentinel was not able to save the new configuration on disk!!!: Permission denied HOT 2
- Dependency Dashboard
- Migrate integration tests from ServerSpec to InSpec
- redis config file should be updated as needed (desired state) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from redisio.