What about forks or customized defaults for Trellis/Bedrock?
Open
Nobody has claimed this yet.
question
- Dominant language
- Go
- Stars
- 169
- Forks
- 30
- Avg merge
- 13h 43m
- Merged PRs (30d)
- 7
Description
what if you're an agency that maintains your own fork of trellis that already has certain things in place that are used on all of your trellis sites? such as:
- wp-cli packages
- certain users/keys for servers
- vault keys for licenses/services
how could you use this trellis cli to create new trellis projects with all of those defaults?
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
The issue names no files, tests, or entry points. Start by reviewing the Trellis CLI project-creation flow and how it handles templates or configuration, then define how agency-specific forks and shared defaults should be selected and applied when creating a project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, go, wordpress
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100