This repository has been archived by the owner on Apr 13, 2019. It is now read-only.
Sorry ruby, but chef has got to go. #17
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hm. To keep its dependencies minimal, So we may keep ruby after all. |
|
There's no real reason it must be ERB though; we only use it to interpolate a small number of strings. The older |
phs
force-pushed
the
phs/ditch-chef
branch
3 times, most recently
from
21668a5
to
96f1998
Compare
phs
force-pushed
the
phs/ditch-chef
branch
13 times, most recently
from
ae30f03
to
8d058db
Compare
phs
force-pushed
the
phs/ditch-chef
branch
11 times, most recently
from
31eb536
to
b3a5db0
Compare
phs
force-pushed
the
phs/ditch-chef
branch
8 times, most recently
from
f125ba4
to
b634e43
Compare
Apparently chef can't sit on its hands for a few months without breaking itself. Out you go! Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts. This prompts a number of not-so-small changes: * `make` is now the build tool. * Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool. * Version commit/tag management has been extracted to `bump-version`. * Ditch Ubuntu 14 for 16. * Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox * `install` grows a `LOCAL` mode, intended to update an existing repo. The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1). However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy. We keep ubuntu 16 since it's the future anyhow. My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16. These have been [resolved][3]. [1]: https://github.com/sstephenson/bats [2]: vmware/open-vm-tools#90 [3]: fgrehm/vagrant-cachier#175
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry ruby, but chef has got to go.
Apparently chef can't sit on its hands for a few months without breaking itself. Out you go! Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.
This prompts a number of not-so-small changes:
makeis now the build tool.bats, a bash testing tool.bump-version.The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1). However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy. We keep ubuntu 16 since it's the future anyhow.
My previous adherence to ubuntu 14 was driven by a problem between
vagrant-cachierand permissions/ownership problems appearing in 16. These have been resolved.