[GH-ISSUE #5920] Reactive-Resume

kerem commented

2026-02-26 12:48:17 +03:00

Owner

Originally created by @cloudbr34k84 on GitHub (Jul 10, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5920

Originally assigned to: @vhsdream on GitHub.

📌 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 - https://github.com/AmruthPillai/Reactive-Resume/issues/2338

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

Originally created by @cloudbr34k84 on GitHub (Jul 10, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5920 Originally assigned to: @vhsdream on GitHub. ### 📌 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 - https://github.com/AmruthPillai/Reactive-Resume/issues/2338 It would be good to have this script updated to this forked version as its now maintained

kerem

2026-02-26 12:48:17 +03:00

closed this issue
added the
website

update script

refactor

json
labels

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@vhsdream commented on GitHub (Jul 11, 2025):

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

@vhsdream commented on GitHub (Jul 11, 2025): 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](https://github.com/lazy-media/Reactive-Resume)

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@cloudbr34k84 commented on GitHub (Jul 12, 2025):

Sweet as.

@cloudbr34k84 commented on GitHub (Jul 12, 2025): Sweet as.

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@lazy-media commented on GitHub (Jul 12, 2025):

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:

Updated URLs: All relevant URLs have been updated to reflect new owner.
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

@lazy-media commented on GitHub (Jul 12, 2025): 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

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@tremor021 commented on GitHub (Jul 12, 2025):

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.

@tremor021 commented on GitHub (Jul 12, 2025): 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.

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@vhsdream commented on GitHub (Jul 12, 2025):

@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
}

@vhsdream commented on GitHub (Jul 12, 2025): @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 } ```

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@lazy-media commented on GitHub (Jul 12, 2025):

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

Transparency: Any breaking changes will be clearly documented in release notes with advance notice.
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.
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

@lazy-media commented on GitHub (Jul 12, 2025): 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

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@MickLesk commented on GitHub (Jul 17, 2025):

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

@MickLesk commented on GitHub (Jul 17, 2025): @vhsdream I've just skimmed through it, it looks clean so far, you can pump it into Live for all I care

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@tremor021 commented on GitHub (Jul 17, 2025):

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

@tremor021 commented on GitHub (Jul 17, 2025): Yep, if no other changes are required except changing the repo url @vhsdream, just PR it

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@vhsdream commented on GitHub (Jul 17, 2025):

Resolved by #6051

@vhsdream commented on GitHub (Jul 17, 2025): Resolved by #6051

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@lazy-media commented on GitHub (Jul 21, 2025):

@vhsdream

I hope this message finds you well and apologize if you are not the correct person to ping for this, but I wanted to bring to your attention a minor discrepancy I noticed on the ProxmoxVE community scripts page.

Currently, the page at https://community-scripts.github.io/ProxmoxVE/scripts?id=reactive-resume lists Reactive Resume as version v4.4.4, while the current version according to the new fork is v1.2.1.

While this may not be a critical issue, I thought it would be beneficial to address this to ensure users have accurate information when downloading and using the script.

Best regards,
Lazy Media

@lazy-media commented on GitHub (Jul 21, 2025): @vhsdream I hope this message finds you well and apologize if you are not the correct person to ping for this, but I wanted to bring to your attention a minor discrepancy I noticed on the ProxmoxVE community scripts page. Currently, the page at [https://community-scripts.github.io/ProxmoxVE/scripts?id=reactive-resume](https://community-scripts.github.io/ProxmoxVE/scripts?id=reactive-resume) lists Reactive Resume as version **v4.4.4**, while the current version according to the new fork is **v1.2.1**. While this may not be a critical issue, I thought it would be beneficial to address this to ensure users have accurate information when downloading and using the script. Best regards, Lazy Media

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@MickLesk commented on GitHub (Jul 21, 2025):

Thats an Crawling from newreleases.io, i always have to adjust the repos manually. Should be done with the next crawl.

@MickLesk commented on GitHub (Jul 21, 2025): Thats an Crawling from newreleases.io, i always have to adjust the repos manually. Should be done with the next crawl.

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@Dunky13 commented on GitHub (Nov 12, 2025):

Interestingly development on the fork has died down since september, and the original developer started releasing again 🙃 What to believe? 🙈

@Dunky13 commented on GitHub (Nov 12, 2025): Interestingly development on the fork has died down since september, and the original developer started releasing again 🙃 What to believe? 🙈

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@lazy-media commented on GitHub (Nov 14, 2025):

Thank you for your interest in the fork. I would like to clarify that the project is still active. However, as the current maintainer, my development bandwidth is limited, as this is a community-driven initiative that I contribute to in my spare time.

The core purpose of this fork is to serve as a community version, and I welcome pull requests from developers who have ideas or features they would like to implement beyond the scope of the original project.

I am currently in the process of re-syncing with the upstream repository and will be porting over the popular features from the community version. Please be advised that I am not a professional developer and am navigating this process as a learning experience.

@lazy-media commented on GitHub (Nov 14, 2025): Thank you for your interest in the fork. I would like to clarify that the project is still active. However, as the current maintainer, my development bandwidth is limited, as this is a community-driven initiative that I contribute to in my spare time. The core purpose of this fork is to serve as a community version, and I welcome pull requests from developers who have ideas or features they would like to implement beyond the scope of the original project. I am currently in the process of re-syncing with the upstream repository and will be porting over the popular features from the community version. Please be advised that I am not a professional developer and am navigating this process as a learning experience.

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@Dunky13 commented on GitHub (Jan 12, 2026):

@lazy-media There have been multiple released on the "old" reactive resume, whereas there haven't been any in your repo since september. Any update on this?

@Dunky13 commented on GitHub (Jan 12, 2026): @lazy-media There have been multiple released on the "old" reactive resume, whereas there haven't been any in your repo since september. Any update on this?

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@lazy-media commented on GitHub (Jan 13, 2026):

@lazy-media There have been multiple released on the "old" reactive resume, whereas there haven't been any in your repo since september. Any update on this?

My repo is still active. It was never meant to replace the original since I am not a developer but am trying to learn. It was meant for a community version that can be contributed to if the original was abandoned or no longer maintained or if there was something someone wanted that wasn't implemented into the original. Since the original is still being maintained, I plan to merge the original and mine if I like how things look. I am currently working on merging the current version of the original owner and mine in my spare time, but that is kind of slim as of right now, so it is taking a lot longer than I would like.

@lazy-media commented on GitHub (Jan 13, 2026): > [@lazy-media](https://github.com/lazy-media) There have been multiple released on the "old" reactive resume, whereas there haven't been any in your repo since september. Any update on this? My repo is still active. It was never meant to replace the original since I am not a developer but am trying to learn. It was meant for a community version that can be contributed to _if_ the original was abandoned or no longer maintained or if there was something someone wanted that wasn't implemented into the original. Since the original is still being maintained, I plan to merge the original and mine if I like how things look. I am currently working on merging the current version of the original owner and mine in my spare time, but that is kind of slim as of right now, so it is taking a lot longer than I would like.

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@tremor021 commented on GitHub (Jan 13, 2026):

@lazy-media if the original repository picked up development and is updating again, we will most likely have to switch back to pulling releases from that repo, as its the original project repository.
If your repository has some unique features that original repository doesn't have, we could probably offer two script versions. One original and one fork (kind of like NPM and NPMPlus).
@community-scripts/contributor will most likely discussing this internaly as to determine course of action here

@tremor021 commented on GitHub (Jan 13, 2026): @lazy-media if the original repository picked up development and is updating again, we will most likely have to switch back to pulling releases from that repo, as its the original project repository. If your repository has some unique features that original repository doesn't have, we could probably offer two script versions. One original and one fork (kind of like NPM and NPMPlus). @community-scripts/contributor will most likely discussing this internaly as to determine course of action here

Rows
Columns

[GH-ISSUE #5920] Reactive-Resume #1259

📌 Task summary

📋 Task details