Eurotimmy

Hey @xokia Did you catch any of the posts in this thread (above) prior to your claim of “non existent support”? There is an active community of very knowledgeable and respectful people, including the developers and contributors to this great project. They’ll help you out if you take some time to repeat your needs in the Discord channel. OFFICIAL ROMM SUPPORT Discord - RomM -support

The start of support thread for Documenso Documenso (Github)

The start of support for Bitbucket Pipelines Runner

Support of typesense / typesense-dashboard.

Hey @LordShad0w , frustrating to hear it! Please could you raise this with the strong comunity of supporters over on Discord? People are friendly, knowlegeable and gamers, so awesome for support. OFFICIAL ROMM SUPPORT Discord - RomM -support

Please jump on to: OFFICIAL SUPPORT Discord - RomM -support Plenty of help from ther community over there.

Please test this new 'rc.webhookd' file? The "start" function will: 1. Create the scripts directory at "/mnt/user/appdata/webhookd/scripts" if it doesn't exist 2. Create a .env file at "/mnt/user/appdata/webhookd/webhookd.env" with some simple default values if it doesn't exist 3. Read in the .env file for use in the current environment 4. Start webhookd using the current environment variables #!/bin/sh NAME="webhookd" CMD="/usr/bin/webhookd" ENV_FILE="/mnt/user/appdata/webhookd/webhookd.env" PROCESSNAME="/usr/bin/webhookd" USERNAME="root" func_stop() { if [ "$(ps aux | grep $PROCESSNAME | grep -v grep)" ]; then echo -n "Stopping $NAME ... " killall $PROCESSNAME sleep 1 fi if [ ! "$(ps aux | grep $PROCESSNAME | grep -v grep)" ]; then echo "Done!" else echo "Error!" fi } func_start() { echo -n "Starting $NAME ... " # Ensure the webhookd config directory exists CONFIG_DIR="/mnt/user/appdata/webhookd" if [ ! -d "$CONFIG_DIR" ]; then echo "Creating config directory at $CONFIG_DIR" mkdir -p "$CONFIG_DIR" fi # Ensure the webhookd.env file exists if [ ! -f "$ENV_FILE" ]; then echo "Creating webhookd environment file at $ENV_FILE" cat <<EOF > "$ENV_FILE" WHD_HOOK_SCRIPTS=/mnt/user/appdata/webhookd/scripts WHD_HOOK_DEFAULT_EXT=.sh WHD_LISTEN_ADDR=:8080 WHD_LOG_LEVEL=info EOF fi # Ensure the hook scripts directory exists HOOK_SCRIPTS_DIR="/mnt/user/appdata/webhookd/scripts" if [ ! -d "$HOOK_SCRIPTS_DIR" ]; then echo "Creating hook scripts directory at $HOOK_SCRIPTS_DIR" mkdir -p "$HOOK_SCRIPTS_DIR" fi # Export environment variables from the webhookd.env file set -a . "$ENV_FILE" set +a echo "Loaded environment variables from $ENV_FILE:" # Uncomment the next line to output the environment variables # cat "$ENV_FILE" # Start webhookd su - $USERNAME -c "$CMD" & sleep 1 if [ "$(ps aux | grep $PROCESSNAME | grep -v grep)" ]; then echo "Started!" else echo "Error!" fi } case "$1" in "start") func_start ;; "stop") func_stop ;; "restart") func_stop sleep 1 func_start ;; *) echo "Usage: $0 start|stop|restart" ;; esac Please see if that works, or not?

Hey @fejich, thanks for producing these. In the 'webhookd' plugin. I see this text in the 'Plugins' section in Unraid. I notice the path " /mnt/user/appdata/webhookd" doesn't exist, is that to be manually created?

Smashing news! I have been dealing with “life” and certainly don’t want to hinder this awesome project. Let’s get your template in to the right place to move the ball forward. I’ll get some time back soon to make adjustments. Will DM with you.

Hey folks Due to personal circumstances I can continue to support the Unraid template (and update it where needed) but can’t replace the good support from the Odoo community (and their own paid support service) as I cannot be across the enormity of Odoo itself. Hopefully the Odoo community here can assist in specific cases that I cannot myself replicate.

Gold! Haha

Hey @Nick.L I’d suggest to try using your “http://192.168.x.x:PORT” addresses in the two fields in the Reactive Resume container instead of using the domain names in there. Hey @icarus69 Sounds like a good feature but it’ll need to be requested of the developer, in GitHub.

Hi @Nick.L, thanks for giving Reactive Resume a go and watching the tutorial. If you could please check the value in your "STORAGE_URL:" on the Reactive Resume container looks like this: https://cv-store.mydomain.com/default Please let us know if that helps, or show some more of your setup and I'll try to help some more. Cheers

Personally I have not figured out how to correct this, but instead I don't reverse proxy the Reactive Resume container and only the MinIO container. I can work on resumes remotely via Wireguard or locally on my server, but having the MinIO container on my NPM reverse proxy will allow anybody with the URL to each resume to download them.

Hi @icarus69 I've only been able to look briefly so far. The PDF looks like it's failing due to the ports being misaligned between Reactive resume and the Chrome container. Reactive Resume container is pointing at the Chrome container: 192.168.0.229:3010 but you're Chrome container appears to be at :3004 A quick edit to that entry should correct the PDF creation.