Reactive-Resume

[cloudbr34k84]

📌 Task summary

Update Reactive-Resume to use new Fork Version

📋 Task details

It appears the reactive resume has been forked. Reactive Resume Self-Hosted Community Fork - Contribution Guidelines - AmruthPillai/Reactive-Resume#2338

It would be good to have this script updated to this forked version as its now maintained

[vhsdream]

Thanks @cloudbr34k84 - I noticed this myself and have been following the progress of the fork as well.

@MickLesk should this be something for the Dev repo? It might not just be a simple matter of switching the Github URLs.

New repo is https://github.com/lazy-media/Reactive-Resume

[cloudbr34k84]

Sweet as.

[lazy-media]

Hello,

As the new maintainer of this fork, I wanted to take a moment to introduce myself and outline the primary changes implemented in this version compared to the original:

1. Updated URLs: All relevant URLs have been updated to reflect new owner.
2. Docker Compose Enhancements:
   • Docker Compose files have been updated to use environment variables instead of hardcoded values.
   • Note: A few minor adjustments to some Compose files are still pending, though these changes are relatively small in scope and should not impact any further development.

Beyond these updates, the core functionality remains unchanged from the original version.

I recognize that the shift to environment variables in Docker Compose may temporarily impact existing update workflows, and I sincerely apologize for any inconvenience this causes. Our team's priority with this Reactive Resume fork is to:

• Improve baseline security by using env variables instead of hard coded compose values.
• Implement high-value pull requests from the original repository
• Implement any future pull requests that improve the functionality of the app.
• Implement a new cloud version with more storage for everyone to use.

We appreciate your patience during this transition and welcome any feedback.

Best regards,
Lazy Media

[tremor021]

Hi @lazy-media, i'm glad that this project carries on. As long as there are no breaking changes introduced at a regular basis, we have no problem keeping up with having install script for it. Happy development and i encourage you to contact us if any breaking changes are planned for future releases, so we can account for it in our scripts and prevent disruptions for the end user.

@vhsdream we will most likely have to check it at our dev repo before doing the switch. If you can gather a list of changes needed on our end and/or put them in a new script on VED to test that would be awesome.

[vhsdream]

@tremor021 It appears to work without any changes besides switching the repo! The Open WebUI integration works as well.

The current .env works out of the box, for reaching the service on your LAN without TLS.

If you want to put it behind a reverse proxy (I tested with Caddy), the .env needs two small changes:

PUBLIC_URL=https://<your FQDN>
STORAGE_URL=https://<your FQDN>/rxresume

rxresume is the name of the storage bucket.

In my Caddy config, I had to slightly alter my typical configuration to proxy requests to the storage endpoint (/rxresume/*) to port 9000, and the rest to port 3000:

handle @resume {
  @storage path /rxresume/*
  reverse_proxy @storage http://10.10.20.139:9000
  reverse_proxy http://10.10.20.139:3000
}

[lazy-media]

Thank you for your thoughtful feedback @tremor021 —it’s greatly appreciated. To ensure smooth collaboration:

1. Transparency: Any breaking changes will be clearly documented in release notes with advance notice.
2. Proactive Communication: We’ll make a concerted effort to keep you informed of significant updates, especially those that might impact your scripts or end users.
3. Stability Commitment: At this time, we do not anticipate introducing breaking changes in future releases. Should this ever change, we’ll prioritize direct communication to minimize disruptions.

Please don’t hesitate to reach out if you’d like to align further on workflows or version planning. We’re committed to maintaining a seamless experience for all users.

Best regards,
Lazy Media

[MickLesk]

@vhsdream I've just skimmed through it, it looks clean so far, you can pump it into Live for all I care

[tremor021]

Yep, if no other changes are required except changing the repo url @vhsdream, just PR it