* Initial commit of tootctlMediaManagement/configmap.yaml
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Initial commit of tootctlMediaManagement/cronjob.yaml
The start of a CronJob that uses tootctl to manage cache usage
of headers, avators, and media attachments.
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Add tootctlMediaManagement configuration to values.yaml
The tootctlMediaManagement enables:
- Removal of cached attachments including the number of days old the files are
- Removal of cached avatar images
- Removal of cached headers for cached profiles
- Removal of orphaned files
- Reomval of cached remote custom emjoi files
- Setting a cronSchedule for the CronJob
- Setting the failedJobsHistoryLimit for the CronJob
- Setting the successfulJobsHistoryLimit for the CronJob
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Add new tootctl media helpers
mastodon.tootctlMediaManagement.includeFollows
- Prints out --include-follows if needed for tootctl commands
mastodon.tootctlMediaManagement.fullname
- Prints the full name for the tootctl-media used in the configMap and cronJob
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Use tootctlMediaManagement from values.yaml in tootctlMediaManagement templates
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Document tootctlMediaManagement options from values.yaml to README.md
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Bump Chart.yaml version to 1.4.0
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Make tootctlMediaManagement's concurrencyPolicy configurable via values.yaml
This was a request from the Bitnami Charts review of the PR.
Signed-off-by: Joel Parker <joelsparker@gmail.com>
---------
Signed-off-by: Joel Parker <joelsparker@gmail.com>
Signed-off-by: joelparker <joelsparker@gmail.com>
Signed-off-by: Rafael Ríos Saavedra <rrios@vmware.com>
Co-authored-by: Rafael Ríos Saavedra <rrios@vmware.com>
* [bitnami/several] Adapt Chart.yaml to set desired OCI annotations
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
* Bump chart version
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
---------
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
* Add forceHttpsS3Protocol to values.yaml with a default value of false
This setting will allow S3_PROTOCL in mastdon's default configmap to be
set to https independent of minio.tls.enabled's setting.
The reason? You may already have a managed/provisoned TLS cert with
and ingress terminating TLS (cert-manager with nginx-ingress for example)
where you want minio exposed as only a ClusterIP service and not TLS at the
container. For this to happen and for mastodon to create links to S3 stored
data (profile images, media) S3_PROTOCOL needs to be https and minio as a Pod
needs to be http only.
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Document forceHttpsS3Protocol in README.md
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Use forceHttpsS3Protocol to set S3_PROTOCOL mastodon setting
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Add useSecureWebSocket to values.yaml
useSecureWebSocket controls the STREAMING_API_BASE_URL setting used by Mastodon
STREAMING_API_BASE_URL is set by mastodon.streaming.url in _helpers.tpl but
previously only used unsecured websockets for streaming.
If TLS is terminated by using cert-manager or another similar package to secure
mastodon-apache or mastdon-web deployments mastdon-web will serve out unsecured
web socket connections in the generated pages of the application meaning streaming
won't work. The useSecureWebSocket set to true fixes this so the secure websocket
protocol (wss://) will be used when generating STREAMING_API_BASE_URL.
STREAMING_API_BASE_URL is stored in configmap/mastodon-default
Signed-off-by: Joel Parker <joelsparker@gmail.com>
* Bump Chart.yaml as a minor version instead of a patch
This was asked as part of my PR to change the version from a patch release
to a minor release update.
Signed-off-by: Joel Parker <joelsparker@gmail.com>
---------
Signed-off-by: Joel Parker <joelsparker@gmail.com>
Signed-off-by: corico44 <42420333+corico44@users.noreply.github.com>
Co-authored-by: corico44 <42420333+corico44@users.noreply.github.com>
* [bitnami/mastodon] fix volumePermission Init Container
- Do not run chown when no files where created.
- Use variables from .Values.web.
Signed-off-by: Matthias Frey <frey@synyx.de>
* Bump chart version
Signed-off-by: Fran Mulero <fmulero@vmware.com>
---------
Signed-off-by: Matthias Frey <frey@synyx.de>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Co-authored-by: Matthias Frey <frey@synyx.de>
Co-authored-by: Fran Mulero <fmulero@vmware.com>
If S3 is not enabled and a PVC is used, the deployments
and initjob are not rendered.
Signed-off-by: Matthias Frey <frey@synyx.de>
Co-authored-by: Matthias Frey <frey@synyx.de>
* Fix inccorrect comment and broken link for Mastodon Chart
- README.md had a broken link to learn more about Ingress configuration
- _helpers.tpl had a confusing message displayed in --debug mode when running helm
that was a copy-paste from Posrgres in the Redis helper.
* Update bitnami/mastodon Chart version
Because the patch has change other than just the README.md
the Chart version needs to be changed too
---------
Signed-off-by: Joel Parker <joelsparker@gmail.com>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Co-authored-by: Fran Mulero <fmulero@vmware.com>
- Add SMTP configuration to enable sending emails
- Add LOCAL_HTTPS environment variable to allow successful federation with other Mastodon instances
- Add RAILS_ENV and NODE_ENV environment variables to the default config
- Fix Redis auth being disabled unless externalRedis.password is set. Auth now enabled by *either* externalRedis.password or externalRedis.existingSecret
- Add DEFAULT_LOCALE environment variable
Signed-off-by: Alex Guyot <ajguyot@icloud.com>
