Skip to content

Conversation

@emanuel-quix
Copy link
Collaborator

No description provided.

@github-actions
Copy link

Docs preview site available at https://quixdocsdev.blob.core.windows.net/pr445/index.html

To summarize, your workflow for deploying an external image is:

1. **Prepare the external image**: Ensure it's built and pushed to a container registry accessible by the platform.
\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, thanks!

| **Public Access** | Configure whether the container is accessible externally via a public URL. |
| **State Management** | If state is enabled, a `state` folder is created to persist data across restarts. See [state management docs](./state-management.md). |
| **Deployment Name** | The name of the deployment. You can change it to something descriptive. |

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need a Yaml example?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pointing to the yaml configuration here

To deploy an external image from the command line, modify your [`quix.yaml`](../quix-cli/yaml-reference/pipeline-descriptor.md) file to include the image, then use the following commands:

@emanuel-quix emanuel-quix merged commit 03cab04 into main Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants