-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[bitnami/discourse] Issue with discourse-calendar plugin #67939
Comments
Hi, Is the issue only happening with the discourse calendar plugin? Can you see the same issue with other plugins? |
Hi, @javsalgar I have installed the |
Hi, It is not clear to me if the issue has to do with the Bitnami packaging of Discourse or with Discourse itself. Did you check if the plugin with upstream Discourse? |
Hi, @javsalgar Thank you for the quick response. A question on this topic was already posted on the Discourse community two years ago. The Discourse team responded that they cannot provide support for Bitnami images. Given that the Discourse Calendar GitHub source has been updated this week, it is expected that it works correctly with Discourse itself. Please note that due to my development environment, I am unable to use the cloud installation suggested by Discourse, and therefore cannot confirm if Discourse itself is functioning properly. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/discourse:3
What architecture are you using?
None
What steps will reproduce the bug?
discourse-calendar
plugin.https://github.com/discourse/discourse-calendar
followed the below instructions.
https://docs.bitnami.com/aws/apps/discourse/configuration/install-plugins/
and also tried to copy GitHub repository to the plugin folder of the Docker volume and restarting it.
What is the expected behavior?
The service should start normally.
What do you see instead?
The service is not running with the error log below.
Additional information
No response
The text was updated successfully, but these errors were encountered: