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.

@TheCyberQuake Update the Repository: entry with "rommapp/romm:3.1.0-rc.1" - thank you @zurdi15!!

Thank you @dallus for giving the tutorial a shot! I only proxy 2 servers... in my tutorial I use the following settings: Port 3000 - for Reactive Resume V4 Web UI Port 9004 - for MinIO file storage In NPM - Proxy Hosts (for example): cv.mydomain.com >> http://192.168.1.200:3000 cv-store.mydomain.com >> http://192.168.1.200:9004 Please note: Due to me not wanting other (public) users being able to create accounts / resumes's I have Disabled the "cv.mydomain.com" proxy host. This means your "cv-store.mydomain.com" will still serve your completed resume files publicly for those you share the link to. Unfortunately the docker env. for disabling public account creation doesn't work...

Yup, I am sorry folks... I took a long time to get started in here due to... well, 'life'. Please accept my apologies and I hope the video walkthrough I have created will assist in peoples own installations!! Any feedback appreciated! and... I hope you make the resume that lands you the job you'll love!

NOTE: As of posting this the Unraid CA library may not have picked up my edits yet, it's usually pretty quick though. I have updated the ':latest' tag option in the Unraid CA template. Select the ':latest' option on a fresh install of RomM to get the new variable and repo. Check the 'Repository' is pre-set to "rommapp/romm:latest" If the template is correct the 'UMASK' will be in the "Show more settings..." section and pre-set to "000" Thank you to @Cryptic3258 & @ktfcaptain for posting up the changes here (above). 🏆 Please report back with any issues / results for me to keep the template up-to-date. 💪

Hey team! I have published another RomM CA template now. (it took a couple of days to appear / publish in CA, please excuse the delay) When you are performing a fresh install, you will be presented with 2 options. Please select 'latest' in the option list to get the current v3.X and the template will have all the current variables available for you. Note: v3.X requires a MariaDB container, which is quick to add in Unraid CA. FYI: @Green Dragon - please notify the Discord community if you feel its appropriate.

For now I have added an option in the XML template to select which 'tag' you want to install. On a fresh installation, you will see' Option: = 2.3.1 - The last of the 2.X versions (requiring only minor efforts on the installers part) = latest - The most recent of the 3.X version (as of writing this... requiring the "PORTS, PATHS, AND VARIABLES" from @Green Dragon 🙏 post above) I'll adjust the XML template again soon... to auto include all the right ports, paths & variables for the 'latest' tag.

Hey @jrmcmillan, thanks for giving Odoo17 a try. I'll try to assist you as best I can. Please check: On a fresh Postgres database, you ran the Odoo17 container for the very first time with the "Post Arguments" field set to -i base ... THEN, you removed the "-i base" from the "Post Arguments" field and restarted both Postgres and Odoo17 Also, I found a couple of threads (addmittedly I feel they could be long shots) about adding the "PGUSER" environment variable to the Docker environment. In Unraid it would look like the attached example for anybody else reading this. Please consider (if safe to do so) redoing the database part again...? In Unraid Docker tab Remove the 'postgresql15' docker your using for Odoo (Remove, Yes) Delete "/mnt/cache/appdata/postgresql15" (if you're comfortable to remove that folder) In the Odoo17 container, add "-i base --without-demo=all --stop-after-init" in to "Post Arguments" Add a new 'postgesql15' Docker container, configure it and start it Run Odoo17 container one time It should run and stop on it's own View it's 'Logs' to see if it initialised the database Let us know how you go? Cheers!

Thank you @trurl! Seems like a super-power action. 🦾

Hey @trurl, It seems the 'After posting... Hide Topic' has hidden it from me completely. (or, I'm not looking in the right places to find the way to view 'hidden' posts)

Hey @JorgeB ugh, sorry to necro this topic... I just did exactly the same thing. I have a [SUPPORT] thread I started for a CA container... "Reactive Resume v4" Any chance I can get the URL to it (for my Unraid CA template XML) please?