feat: enhance deployment process with Gitea Actions integration and improved environment variable handling
This commit is contained in:
22
README.md
22
README.md
@@ -1,3 +1,25 @@
|
||||
# WPop
|
||||
|
||||
WordPress operations CLI for Websimple projects.
|
||||
|
||||
## Deploy environment
|
||||
|
||||
`wpop deploy` needs:
|
||||
|
||||
- `REMOTE_HOST`
|
||||
- `REMOTE_PORT`
|
||||
- `REMOTE_USER`
|
||||
- `REMOTE_PATH`
|
||||
|
||||
If any `REMOTE_*` value is missing, `wpop` tries to read Websimple Gitea Actions variables from the
|
||||
current repository and its organization. Provide a read-only Gitea token with one of:
|
||||
|
||||
- `WEBSIMPLE_GITEA_API_TOKEN`
|
||||
- `WPOP_GITEA_TOKEN`
|
||||
- `GITEA_TOKEN`
|
||||
|
||||
By default, the repository is inferred from `git remote get-url origin`. You can override this with:
|
||||
|
||||
- `WPOP_GITEA_REPO=wp-sites/example`
|
||||
- `WPOP_GITEA_OWNER=wp-sites` and `WPOP_GITEA_REPO_NAME=example`
|
||||
- `WPOP_GITEA_BASE_URL=https://gitea.websimple.com`
|
||||
|
||||
Reference in New Issue
Block a user