stackbuilders / stackbuilders/hapistrano
Single configuration file
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 108
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Most of the settings across different deployment scripts such as staging.yaml and production.yaml are the same. Usually, they only differ in the name of the branch, therefore I would like to propose to use a single configuration file with different sections instead of separate files, the format might look like:
repo: git@github.com:<org>/<repo>
build_script:
- stack setup
- stack build
restart_command: <restart command>
staging:
revision: origin/master
production:
revision: origin/production
Then we could change the CLI to take a section as an argument:
$ stack exec hap -- deploy staging
$ stack exec hap -- deploy production
``Contributor guide
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
Start by locating the deployment configuration files named staging.yaml and production.yaml, then trace the CLI entry point for the deploy command. Compare the shared settings and determine how configuration sections are selected; done means the proposed single-file format and staging/production commands work without separate deployment files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, yaml
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100