HashNuke / HashNuke/heroku-buildpack-elixir
App environment available in all builds
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 812
- Forks
- 329
- PR merge metrics
- No merged PRs in 30d
Description
Source https://devcenter.heroku.com/changelog-items/416
ENV_DIR is a directory that contains a file for each of the application’s configuration variables.
We should read that instead of relying on user defined values that are duplicated. People might forget REDIS_URL or SECRET_KEY_BASE, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked Heroku changelog entry and inspect the buildpack entry points that configure the application environment; the issue names ENV_DIR as the source to use. Done means application configuration variables are read from ENV_DIR in all builds, without requiring duplicated user-defined values such as REDIS_URL or SECRET_KEY_BASE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, shell
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100