feat(dev): develop this add-on inside a locally-run Portainer [R8S-1167] - #79
Open
RHCowan wants to merge 1 commit into
Open
feat(dev): develop this add-on inside a locally-run Portainer [R8S-1167]#79RHCowan wants to merge 1 commit into
RHCowan wants to merge 1 commit into
Conversation
Wire portainer-run into the local add-on dev loop documented in the reference add-on (portal-template/docs/developing-inside-portainer.md), which runs a Portainer server inside a real local cluster and serves this add-on through the production gateway. - VITE_DEV_PORT moves the Vite dev server and its matching HMR clientPort, so live reload works across the split origin (page on :8999, Vite here) and this add-on can run alongside others. - image.pullPolicy is now a chart value (still defaulting to Always), so a locally-built image loaded onto the cluster's nodes runs without a registry when set to IfNotPresent/Never via DEV_ADDON_VALUES. - `bun run redeploy` builds, loads onto the cluster's nodes (auto-detecting kind / minikube / k3d / k3s / microk8s / a runtime shared with the host) and rollout-restarts the Deployment. It resolves the tag from dev-values.yaml, since `rollout restart` never changes a pod's image spec and a mismatch would silently ignore the rebuild. - dev-values.yaml.example is the starting point for the values file (including how to reach the host-run Portainer, which differs per cluster); the copy is gitignored, since it holds per-developer image tags and URLs.
|
Note PR image published: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wire portainer-run into the local add-on dev loop documented in the
reference add-on (portal-template/docs/developing-inside-portainer.md), which runs a
Portainer server inside a real local cluster and serves this add-on through
the production gateway.
so live reload works across the split origin (page on :8999, Vite here)
and this add-on can run alongside others.
locally-built image loaded onto the cluster's nodes runs without a
registry when set to IfNotPresent/Never via DEV_ADDON_VALUES.
bun run redeploybuilds, loads onto the cluster's nodes (auto-detectingkind / minikube / k3d / k3s / microk8s / a runtime shared with the host)
and rollout-restarts the Deployment. It resolves the tag from
dev-values.yaml, since
rollout restartnever changes a pod's image specand a mismatch would silently ignore the rebuild.
how to reach the host-run Portainer, which differs per cluster); the copy is
gitignored, since it holds per-developer image tags and URLs.