Reactive Setup

[TimPasquini]

As a stopgap until the full reactive resume readme gets finished, here is a copy of a reply on the unraid thread outlining what I did to get things running:

Ok, I ended up getting it running!

 

For support containers I used:

    cheesemarathon's minio container
    jj9987's postgresql15 container
    A75G's redis continer (jj9987 also had a redis container, but I was already using it for immich, I'm guessing I can get them to share but didn't look into it yet just wanted things up and running)
    Masterwishx's browserless container

For configuration stuff:

You will need the chrome token, access token, storage key access, and storage key secret EUROTIMMY mentions for this setup. You can follow the directions from EUROTIMMY to randomly create them, that is what I did.

I also realized I wrote "check for port conflicts" under every container, so I'm just going to mention that up here. You should always check for conflicts when installing any containers, unraid lets you expand the "Show docker allocations" option at the bottom of a container setup page to see all containers and their active ports.

 

Minio

Not much to do here, the MINIO_ROOT_USER should be set to your "storage key access" value that you generated and your MINIO_ROOT_PASSWORD should be set to the "storage key secret" you generated

 

POSTGRESQL15

Set a username and password, you can pick anything and you'll need them again for the reactive resume config. I didn't bother changing the DB name off the default "postgres". Verify you have a valid database storage path.

 

redis

Set "allow empty password" to "no". I didn't change anything else here and it had already populated a string of digits for the default password which I kept.

 

Browserless

Add a variable named "chrome token" with the KEY of "TOKEN" and VALUE of the randomly generated chrome token.

 

Ok, now moving on the application itself. Once the support containers are in place you can configure and launch EUROTIMMY's reactive resume V4 container. There is quite a bit to configure but it is all pretty straightforward:

 

If you're doing reverse proxying put your URLs in the PUBLIC_URL and STORAGE_URL. From what I can tell public url is the login page and storage url will display your "default" resume to anyone who goes to that page.

 

CHROME_TOKEN - enter the same value you entered in the browserless config for the TOKEN variable you created there.

 

CHROME_URL - use "http://<IP>:<PORT>/" for the browserless container

 

DATABASE_URL - this has a specific format of: "postgresql://<USER>:<PASSWORD>@<IP>:<PORT>/<DB_NAME>" the user, password, and db_name should all match the values in your postgresql15 config. For example, my string is something like "postgresql://reactive_user:[email protected]:5432/postgres"

 

ACCESS_TOKEN_SECRET & REFRESH_TOKEN_SECRET - these should be 2 of the 5 values your randomly generated following EUROTIMMY's existing instructions for creating tokens.

 

MAIL_FROM & SMTP_URL - use your email address and the SMTP url. This follows a simmilar pattern to the DATABASE_URL and there is an example string on the container instructions. If you're using gmail, I suggest following EUROTIMMY's instructions in the readme to create an app specific password.

 

STORAGE_ENDPOINT & STORAGE_PORT - the IP and PORT for your Minio container.

 

STORAGE_ACCESS_KEY & STORAGE_SECRET_KEY - these should match the values you used in your Minio config. Make sure you match the strings correctly, the access key and root user should be the same, and the secret key and root password should match each other.

 

REDIS_URL - Another url string simmilar to postgres and the smtp setups. if you used my instructions above for redis, this one should be "redis://default:<PASSWORD>@<IP>:<PORT>" with the password being the value entered on the redis config and the IP and port of the redis container as the IP and PORT

 

I did not need to adjust anything under the "SHOW MORE SETTINGS" heading.

 

I made sure all the support containers were launched and then fired up reactive and it seems to be working!