shore-config - project init providing shore config
- Dominant language
- Go
- Stars
- 21
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
Original Author: @dkirillov
`shore project init` should provide a `shore.yml`.
This shore config could have multiple profiles - either included or commented out - to show off the ability to do in-line configuration or use/source external configs from elsewhere.
`default` profile and executor config must be defined! So `executor.config.default` and `profiles.default` must exist so that what is provided by `shore project init` continues to function out of the box - you can do `shore render` right after you finish `shore project init`.
## Motivation
## Describe alternatives you've considered
## Additional context
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the implementation of `shore project init` and inspect how it creates project files, then run it and follow with `shore render`. The generated `shore.yml` should include usable `executor.config.default` and `profiles.default` entries, with example profiles showing inline or external configuration while rendering works immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100