-
-
Notifications
You must be signed in to change notification settings - Fork 7
Add dragonfly chart #7
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
base: main
Are you sure you want to change the base?
Conversation
| {{/* | ||
| Expand the name of the chart. | ||
| */}} | ||
| {{- define "dragonfly.name" -}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure we should name this chart dragonfly.
This is specifically related to Mastodon, so something like dragonfly-mastodon-instance is probably more accurate here, or maybe even dragonfly-operator-mastodon-instance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That definitely makes sense.
I prefer names of things to be as short as possible, so I would prefer dragonfly-mastodon-deploy
- Add ability to separate out app and sidekiq (default is single instance)
Similar to the cloudnative chart, makes it easier to just define what we need while keeping the configuration as DRY as possible.