You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible for a charmed deploy using S3 integration to enter a state where the generated HTML references S3-hosted files that don't exist - see #208.
Currently the least painful workaround is to get a discourse console session on a pod, and run bundle exec rails s3:upload_assets.
This enhancement proposal is a request for a charm action to perform the above, and ideally to confirm a successful upload.
The text was updated successfully, but these errors were encountered:
Hi @barryprice, IINM, currently the pods gets into error state if the migration fails. As the redis bug should be fixed by now, I do not think a new action should be necessary.
If this is still happening with the latest version of the charm, please inform us so we can investigate it.
Enhancement Proposal
Hi
It's possible for a charmed deploy using S3 integration to enter a state where the generated HTML references S3-hosted files that don't exist - see #208.
Currently the least painful workaround is to get a discourse console session on a pod, and run
bundle exec rails s3:upload_assets
.This enhancement proposal is a request for a charm action to perform the above, and ideally to confirm a successful upload.
The text was updated successfully, but these errors were encountered: