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

Update dev setup documentation #127

Merged
merged 3 commits into from
Feb 26, 2016
Merged

Update dev setup documentation #127

merged 3 commits into from
Feb 26, 2016

Conversation

cavis
Copy link
Member

@cavis cavis commented Dec 9, 2015

Updating README with my experience installing the dev environment.

Also changes database.yml to allow a password on the test database ... which may or may not break the build. We'll find out!

@cavis cavis self-assigned this Dec 9, 2015
@cavis cavis removed the in progress label Dec 9, 2015
@cavis cavis assigned cqr and unassigned cavis Dec 9, 2015
@cavis
Copy link
Member Author

cavis commented Dec 9, 2015

I thought I remembered blank values in database.yml for username or password causing problems. But that was probably working with postgres, not mysql. This seems to work fine.

@@ -50,10 +53,13 @@ echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
source ~/.bash_profile

# ruby (.ruby-version default)
rbenv install
rbenv install 2.1.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that if .ruby-version is present in the directory you run rbenv install in (which it is if you're in a checkout for this project) rbenv install is technically more correct than rbenv install 2.1.2. That said, the ordering on this is a little wonky, so maybe good to specify

@cqr cqr assigned cavis and unassigned cqr Dec 15, 2015
cqr added a commit that referenced this pull request Feb 26, 2016
@cqr cqr merged commit 2bb8f14 into master Feb 26, 2016
@cqr cqr deleted the docs/dev_setup_process branch February 26, 2016 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants