We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation .
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
Following the template for one-click deployment based on this posting of UVdesk: https://mariushosting.com/how-to-install-uvdesk-on-your-synology-nas/
Yet, my template does not work ... what is then so wrong?
captainVersion: 4 services: $$cap_appname-db: image: mysql:$$cap_database_version volumes: - $$cap_appname-db-data:/var/lib/mysql restart: always environment: MYSQL_ROOT_PASSWORD: $$cap_db_pass MYSQL_DATABASE: uvdesk MYSQL_USER: $$cap_db_user MYSQL_PASSWORD: $$cap_db_pass caproverExtra: notExposeAsWebApp: 'true' $$cap_appname: depends_on: - $$cap_appname-db image: nuttcorp/uvdesk:$$cap_version restart: always environment: MYSQL_USER: $$cap_db_user MYSQL_PASSWORD: $$cap_db_pass MYSQL_ROOT_PASSWORD: $$cap_db_pass MYSQL_DATABASE: uvdesk caproverOneClickApp: variables: - id: $$cap_db_user label: Database user defaultValue: uvuser validRegex: /^([a-zA-Z0-9])+$/ - id: $$cap_db_pass label: Database password description: '' validRegex: /.{1,}/ - id: $$cap_version label: UVdesk Version defaultValue: 'latest' description: Check out their Docker page for the valid tags https://hub.docker.com/r/library/UVdesk/tags/ validRegex: /^([^\s^\/])+$/ - id: $$cap_database_version label: Database Version, default is MySQL defaultValue: '5.7' description: Check out the Docker pages for the valid tags https://hub.docker.com/r/library/mysql/tags/ or https://hub.docker.com/_/mariadb?tab=tags validRegex: /^([^\s^\/])+$/ instructions: start: >- UVdesk is an open-source helpdesk system that allows businesses to manage their customer support and communication efficiently. It provides a ticketing system that helps organizations handle customer inquiries, issues, and support requests in a structured manner. Enter your UVdesk Configuration parameters and click on next. A MySQL (database) and a UVdesk container will be created for you. The process will take about a minute for the process to finish. end: > UVdesk is deployed and available as $$cap_appname-UVdesk . IMPORTANT: It will take up to 2 minutes for UVdesk to be ready. Before that, you might see a 502 error page. displayName: UVdesk isOfficial: true description: UVdesk is a content management system based on PHP and MySQL that is usually used with the MySQL or MariaDB database documentation: Taken from https://docs.docker.com/compose/UVdesk/.
The text was updated successfully, but these errors were encountered:
When you say not working, what do you exactly mean?
Does it not deploy the apps or after you deployed, the app doesn't work?
Sorry, something went wrong.
I tried using docker-compose, and the app is working, but within CapRover it does not as I received a NGINX 502 Error :/ Even using websocket support does not work either.
I don't see anything obvious that is wrong with your template. Have you followed the 502 troubleshooting guide? Is uvdesk application running? What do the logs say?
https://caprover.com/docs/troubleshooting.html#successful-deploy-but-502-bad-gateway-error
Well, all is ok except this error in the container log:
2023-12-07T08:01:19.226253930Z * Starting Apache httpd web server apache2 2023-12-07T08:01:19.383350660Z AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.1.213. Set the 'ServerName' directive globally to suppress this message 2023-12-07T08:01:20.408312863Z *
Not sure if this is related to the service not working ... using a normal docker compose file, all is working though? So, I do not understand why I would need to use ServerName with caprover, and not within docker compose?
Could not reliably determine the server's fully qualified domain name
This warning is usually not important. The logs are fully normal. Probably requires some debugging, like shelling into the container and run curl internally, and see if that works.
No branches or pull requests