wild-cloud/wild-directory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update CLI references from wild to wildcloud

Browse Source
This commit is contained in:
Paul Payne
2026-08-01 23:00:44 +00:00
parent 869053afe6
commit 7d1cae481b
2 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
AGENTS.md
View File

@@ -19,11 +19,11 @@ These sources will oftentimes not use the latest version. Check to make sure you
## App package development lifecycle ## App package development lifecycle
- when developing a new app, test on the `test-cloud` instance in the `/home/payne/repos/wild-cloud-dev/wild-cloud-redmond-data` wild data dir. Prefer the `wild` CLI for managing app lifecycle as it takes care of copying and compiling kustomize templates. Example commands: - when developing a new app, test on the `test-cloud` instance in the `/home/payne/repos/wild-cloud-dev/wild-cloud-redmond-data` wild data dir. Prefer the `wildcloud` CLI for managing app lifecycle as it takes care of copying and compiling kustomize templates. Example commands:
- `wild instance use test-cloud` - `wildcloud instance use test-cloud`
- `wild app add <app>` - `wildcloud app add <app>`
- `wild app deploy <app>` - `wildcloud app deploy <app>`
- `wild app delete` - `wildcloud app delete`
- But you can always use `kubectl` directly. Just make sure you use the `test-cloud` `kubeconfig` and, when applying resources, use the `-k` flag so kustomize templates get copied. - But you can always use `kubectl` directly. Just make sure you use the `test-cloud` `kubeconfig` and, when applying resources, use the `-k` flag so kustomize templates get copied.
- kubectl --kubeconfig=/home/payne/repos/wild-cloud-redmond-data/instances/test-cloud/kubeconfig get pods -n <app> - kubectl --kubeconfig=/home/payne/repos/wild-cloud-redmond-data/instances/test-cloud/kubeconfig get pods -n <app>
- While we test in `/home/payne/repos/wild-cloud-dev/wild-cloud-redmond-data/instances/test-cloud`, the final product (our app package) must be in `/home/payne/repos/wild-cloud-dev/wild-directory`. Always make sure that, in the end, whatever is in `wild-directory` can be deployed into `test-cloud`. - While we test in `/home/payne/repos/wild-cloud-dev/wild-cloud-redmond-data/instances/test-cloud`, the final product (our app package) must be in `/home/payne/repos/wild-cloud-dev/wild-directory`. Always make sure that, in the end, whatever is in `wild-directory` can be deployed into `test-cloud`.

16
README.md
View File

@@ -31,29 +31,29 @@ The easiest way to manage apps is through the Wild Cloud web app:
### CLI ### CLI
For terminal-based workflows, use the Wild CLI: For terminal-based workflows, use the Wild Cloud CLI:
```bash ```bash
# List available apps # List available apps
wild app list wildcloud app list
# Add app to instance # Add app to instance
wild app add <app-name> wildcloud app add <app-name>
# Deploy app # Deploy app
wild app deploy <app-name> wildcloud app deploy <app-name>
# List deployed apps # List deployed apps
wild app list-deployed wildcloud app list-deployed
# Get app status # Get app status
wild app status <app-name> wildcloud app status <app-name>
# Delete app # Delete app
wild app delete <app-name> wildcloud app delete <app-name>
``` ```
The CLI connects to the Wild Central API (default: `http://localhost:5055`). You can override with `--daemon-url` or set `WILD_API_URI` environment variable. The CLI connects to the Wild Cloud API (default: `http://localhost:5056`). You can override with `--daemon-url` or set `WILD_API_URI` environment variable.
### API ### API