docs: note about private deploys
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
See toolshed/abra#585
This commit is contained in:
@ -464,6 +464,10 @@ route requests after. You're free to make as many `$whatever.yml` files in your
|
|||||||
Yes, it's possible although currently Quite Experimental! See
|
Yes, it's possible although currently Quite Experimental! See
|
||||||
[`#388`](https://git.coopcloud.tech/toolshed/organising/issues/388) for more.
|
[`#388`](https://git.coopcloud.tech/toolshed/organising/issues/388) for more.
|
||||||
|
|
||||||
|
## Can I deploy images from a private registry?
|
||||||
|
|
||||||
|
Yes, as of [`#585`](https://git.coopcloud.tech/toolshed/abra/pulls/585), this is possible. At current time of writing, this feature is unreleased but this will change shortly. You need to run `docker login` before you run your deploy command.
|
||||||
|
|
||||||
## Running an offline coop-cloud server
|
## Running an offline coop-cloud server
|
||||||
|
|
||||||
You may want to run a coop-cloud directly on your device (or in a VM or machine on your LAN), whether that's for testing a recipe or to run coop-cloud apps outside of the cloud ;-)
|
You may want to run a coop-cloud directly on your device (or in a VM or machine on your LAN), whether that's for testing a recipe or to run coop-cloud apps outside of the cloud ;-)
|
||||||
|
Reference in New Issue
Block a user