Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Is :tarball or :package the preferred installation type? #389

Closed
spuder opened this issue Nov 20, 2015 · 2 comments
Closed

Is :tarball or :package the preferred installation type? #389

spuder opened this issue Nov 20, 2015 · 2 comments

Comments

@spuder
Copy link
Contributor

spuder commented Nov 20, 2015

More of the examples use :tarball for the install type, though it seems to me that packages would be preferred in a lot of situations.

Is there a recommended installation?
@karmi
Copy link
Contributor

karmi commented Nov 20, 2015

Hi, in general, the packages are definitely the recommended type of installation, if only because of the init scripts.

@martinb3
Copy link
Contributor

Indeed, the packages are preferred. As I just commented on the other issue you filed, we have a 2.0.0_wip branch going that we're about to release; it's also much better tested with the packaged versions of ES. Hope this helps!

@spuder spuder mentioned this issue Nov 20, 2015
Closed
martinb3 added a commit that referenced this issue Nov 22, 2015
@martinb3
Additional docs, :package default
24f769a 
- Ensure :package is the default installation method everywhere, update docs to reflect. Fixes #389.
- Ensure defaults for :package and :tarball are clear; remove incorrect comment on resource. Fixes #391.
- Ensure actions are firing correctly when providers really do updates, so restarting is easier. Fixes #394.
- Drastically clarify elasticsearch_plugin docs, allow URL specifier for installs. Fixes #392.
- Re-comment the node role in the configure resource to be more plain. Fixes #393.
- Pass through default service notifications from elasticsearch_service to service. Fixes #392.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@karmi @martinb3 @spuder