Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Push the helm chart to github pages #2107

Closed
1 task done
M0NsTeRRR opened this issue Oct 26, 2024 · 7 comments · Fixed by #2208
Closed
1 task done

[Feature Request]: Push the helm chart to github pages #2107

M0NsTeRRR opened this issue Oct 26, 2024 · 7 comments · Fixed by #2208
Labels
enhancement New feature or request

Comments

@M0NsTeRRR
Copy link
Contributor

M0NsTeRRR commented Oct 26, 2024

Feature Description

As described here #335 (comment)
The helm chart is unusable without pushing it to a registry when doing gitops.

Why is this feature valuable?

This feature is mandatory for fluxcd/argocd deployment (gitops)

Suggested Implementation

Additional Information

No response

No Duplicate of the Feature

  • I have verified that there are no existing features requests similar to my request.
@LionKingIsBack

This comment was marked as spam.

@M0NsTeRRR M0NsTeRRR reopened this Nov 10, 2024
@M0NsTeRRR
Copy link
Contributor Author

@Frooodle Hello, I saw you disable the CI for the Helm chart can you tell me what was the issue so we can fix it ?

@Frooodle
Copy link
Member

Going to be moving it to a different repo to avoid release confusion and duplication etc

@Frooodle
Copy link
Member

A stirling-pdf-chart repo

@Frooodle
Copy link
Member

@Frooodle
Copy link
Member

Going to be trying to move logic here if possible, I appreciate your help if you're able

@M0NsTeRRR
Copy link
Contributor Author

Sure, I will do it no problem :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@M0NsTeRRR @Frooodle @LionKingIsBack and others