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 onboarding documentation #4215

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Correct spelling of Algolia
jacobherrington committed Oct 3, 2019
commit f005d35f36a7c8eb6c5809a01ebbebcfe78a098e
4 changes: 2 additions & 2 deletions docs/getting-started/config-env.md
Original file line number Diff line number Diff line change
@@ -4,7 +4,7 @@ title: Configuring Environment Variables

# Configuring environment variables and secret keys

Take a look at `Envfile`. This file lists all the `ENV` variables we use and provides a fake default for any missing keys. You'll need to get your own free [Agolia credentials][agolia] to get your development environment running.
Take a look at `Envfile`. This file lists all the `ENV` variables we use and provides a fake default for any missing keys. You'll need to get your own free [Algolia credentials][algolia] to get your development environment running.

The [backend guide][backend_guide] will show you how to get free API keys for additional services that may be required to run certain parts of the app.

@@ -27,6 +27,6 @@ If you are missing `ENV` variables on bootup, the [envied][envied] gem will aler

Only certain features require "real" keys, so you may be able to add them as you work on different areas of the application.

[agolia]: /backend/algolia
[algolia]: /backend/algolia
[backend_guide]: /backend
[envied]: https://rubygems.org/gems/envied