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.

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

Add copy/paste execution strings for convenient builds #1750

Merged
merged 1 commit into from
Oct 9, 2019

Conversation

lbakerchef
Copy link
Contributor

@lbakerchef lbakerchef commented Sep 19, 2019

Paste this into your shell for convenient builds!

cd && . load-omnibus-toolchain.sh && cd chef-server/omnibus && sudo chown -R vagrant ~/.bundle/ && bundle install --binstubs && bin/omnibus build chef-server -l internal

@lbakerchef lbakerchef force-pushed the lbakerchef/readme-execution-strings branch from a26160b to ea6c44b Compare September 19, 2019 15:54
@lbakerchef lbakerchef self-assigned this Sep 19, 2019
@snapp
Copy link
Contributor

snapp commented Oct 1, 2019

@lbakerchef, just a couple of thoughts on the docs:

  • maybe use source ~/load-omnibus-toolchain.sh as an alternative to . load-omnibus-toolchain.sh; some people may not realize that the period character is used to source a file

@PrajaktaPurohit
Copy link
Contributor

@lbakerchef - this is helpful only first time the build is run. For all the subsequent builds we would run only the last command. It would help to get some clarification around that.

@lbakerchef
Copy link
Contributor Author

lbakerchef commented Oct 2, 2019

@PrajaktaPurohit - For the lazy approach, you can always just paste the same thing and it still works (it's what I do). I think it's 'idempotent' so it runs through the first commands quick if it's not necessary. The idea is to have one "always works, don't need to think" string you can just "paste and forget." "One execution string to rule them all and bind them." But I will add some clarification. Personally, this saves me a lot of time and effort, so I thought others would find it useful.

@christopher-snapp - The period (.) is in the original docs so that's what I used in the execution string. I will try to add a note as to what you are saying if I can figure out a way to do it without muddying the waters.

@lbakerchef lbakerchef force-pushed the lbakerchef/readme-execution-strings branch 2 times, most recently from 6cfa5be to ce9eee3 Compare October 4, 2019 13:59
@PrajaktaPurohit PrajaktaPurohit force-pushed the lbakerchef/readme-execution-strings branch from ce9eee3 to 9639e59 Compare October 9, 2019 18:55
@PrajaktaPurohit PrajaktaPurohit merged commit 0fe0ae1 into master Oct 9, 2019
@PrajaktaPurohit PrajaktaPurohit deleted the lbakerchef/readme-execution-strings branch October 9, 2019 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants