* Refactor:Remove ENVied Gem in Favor of Default application.yml * Copy sample_application.yml for Travis * Create .env_sample file, Warn of missing ENV variables, ignore .env file * Use dotenv For ENV variables and create Rake Task to Populate * Update docs to copy .env_sample file * make application config a bit more resilient * update more documentation and only initialize dotenv in dev and test * Update doc code snippet types and refactor rake task and app config * remove push defaults * Make initializers more resilient, remove unused ENV from travis * Exit new rake task if application.yml does not exist, include dotenv in docs
27 lines
509 B
Markdown
27 lines
509 B
Markdown
---
|
|
title: FAQs
|
|
---
|
|
|
|
# Frequently Asked Questions
|
|
|
|
## How do I build my local copy of the Ruby source code documentation?
|
|
|
|
```shell
|
|
cd docs
|
|
make ruby-doc
|
|
```
|
|
|
|
Then open `.static/ruby-doc/index.html` in the `docs` directory and browse the
|
|
Ruby documentation
|
|
|
|
## How do I enable logging to standard output in development?
|
|
|
|
By default Rails logs to `log.development.log`.
|
|
|
|
If, instead, you wish to log to `STDOUT` you can add the variable:
|
|
|
|
```shell
|
|
export RAILS_LOG_TO_STDOUT=true
|
|
```
|
|
|
|
to your own `.env` file.
|