Automattic / Automattic/jetpack
Launch docker:up with tunnel from jetpack cli
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
#### Is your feature request related to a problem? Please describe.
I'm a lazy Jetpack developer. I don't want to mess around with multiple terminals.
#### Describe the solution you'd like
`jetpack site [args]`
Launches a site in a new docker container.
Some possible args:
`--name=mysite` (a name used to refer to this site - you should be able to launch multiple sites on the same machine without conflicts, in individual shells)
`--modules=photon,likes`
`--plugins=woocommerce,wcship`
`--subdomain=goldsounds6`
`--tunnel=true/false`
`--tail` (tails the logs in the same shell, including debug.log)
`--` (everything after this is passed through to `wp site create`?)
Output:
```
Launching Jetpack with photon & likes
Jetpack launched on localhost:67263
Tunnel available at http://goldsounds6.jurassic.tube
```
#### Describe alternatives you've considered
Doing everything manually. Which is a hassle.
Contributor guide
Research direction
Start by locating the Jetpack CLI entry point and the existing docker:up workflow, then review how arguments could be passed to wp site create. Done would include a jetpack site command supporting the requested site, module, plugin, subdomain, tunnel, tail, and pass-through options without conflicts between simultaneous sites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php, 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