-
-
Notifications
You must be signed in to change notification settings - Fork 545
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
New Script: Zammad #640
New Script: Zammad #640
Conversation
Updated the PR to account for the changes. You can test it on my dev branch: bash -c "$(wget -qLO - https://raw.githubusercontent.com/michelroegl-brunner/ProxmoxVE/refs/heads/DEV/ct/zammad.sh)" |
nope |
Can you test again if this was an isolated error? I´ve run the script on 3 hosts now without a problem. |
I'm new to these community scripts but have a successful build on my server. |
if you get an user passwort question, your lxc is defect! |
@michelroegl-brunner Switch CT to new Default |
@MickLesk Done! |
fix OS
ready for test: bash -c "$(wget -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/refs/heads/develop/ct/zammad.sh)" @florianwilde | @second2falcon |
Works for me, thank you |
@MickLesk sorry for the late response, but it worked for me fine too. |
Just ran this today, failed to setup correctly, the update/running the script again will also say "no installation found" |
Please open a issue and fill out the form and dont answer on closed Pull Requests. Thank you! |
Nvm, the issue is with Nginx, should probably create an option in the script to just expose directly so we can use our own reverse proxy |
Note
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.
Description
Provide a summary of the changes made and/or reference the issue being addressed.
Fixes #642
Type of change
Please check the relevant option(s):
Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:
Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here: