starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Hoarder rebranding and changing name to Karakeep #758

New Issue
Closed
opened 2026-02-04 21:19:58 +03:00 by OVERLORD · 29 comments
OVERLORD commented 2026-02-04 21:19:58 +03:00
Owner
Copy Link

Originally created by @AlkaizerLord on GitHub (Apr 5, 2025).

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Hoarder

📂 What was the exact command used to execute the script?

No command but script will need to either be updated very soon or taken down until all name changes have gone into effect

📝 Provide a clear and concise description of the issue.

This is more for or less not an issue but will be an issue very soon and want the maintainera to know.

Hoarder is changing names to Karakeep per their reddit post

https://www.reddit.com/r/selfhosted/s/obHUAkKcdB

Name change will more than likely break script and updates.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

None atm

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

No response

Originally created by @AlkaizerLord on GitHub (Apr 5, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Hoarder ### 📂 What was the exact command used to execute the script? No command but script will need to either be updated very soon or taken down until all name changes have gone into effect ### 📝 Provide a clear and concise description of the issue. This is more for or less not an issue but will be an issue very soon and want the maintainera to know. Hoarder is changing names to Karakeep per their reddit post [https://www.reddit.com/r/selfhosted/s/obHUAkKcdB](https://www.reddit.com/r/selfhosted/s/obHUAkKcdB) Name change will more than likely break script and updates. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. None atm ### ❌ Paste the full error output (if available). N/A ### 🖼️ Additional context (optional). _No response_
OVERLORD added the investigationupdate scriptrename script labels 2026-02-04 21:19:58 +03:00
OVERLORD commented 2026-02-04 21:20:08 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 5, 2025):

@MohamedBassem You are active, and the developer. What do we need to be prepared for? General changes to the script or just the name change?

@MickLesk commented on GitHub (Apr 5, 2025): @MohamedBassem You are active, and the developer. What do we need to be prepared for? General changes to the script or just the name change?
OVERLORD commented 2026-02-04 21:20:13 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Apr 6, 2025):

@MickLesk Technically, the script should continue working as is without any problems. Even the old repo links will redirect to the new ones so nothing should break.

So from that angle, it'll probably be just a name change. However, when we do the name change in the script, we'll need to be careful not to break existing installations during updates.

@MohamedBassem commented on GitHub (Apr 6, 2025): @MickLesk Technically, the script should continue working as is without any problems. Even the old repo links will redirect to the new ones so nothing should break. So from that angle, it'll probably be just a name change. However, when we do the name change in the script, we'll need to be careful not to break existing installations during updates.
OVERLORD commented 2026-02-04 21:20:15 +03:00
Author
Owner
Copy Link

@divemasterjm commented on GitHub (Apr 6, 2025):

@MickLesk Technically, the script should continue working as is without any problems. Even the old repo links will redirect to the new ones so nothing should break.

So from that angle, it'll probably be just a name change. However, when we do the name change in the script, we'll need to be careful not to break existing installations during updates.

for me is not working

@divemasterjm commented on GitHub (Apr 6, 2025): > [@MickLesk](https://github.com/MickLesk) Technically, the script should continue working as is without any problems. Even the old repo links will redirect to the new ones so nothing should break. > > So from that angle, it'll probably be just a name change. However, when we do the name change in the script, we'll need to be careful not to break existing installations during updates. for me is not working
OVERLORD commented 2026-02-04 21:20:17 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Apr 6, 2025):

@divemasterjm mind sharing the errors you're getting?

@MohamedBassem commented on GitHub (Apr 6, 2025): @divemasterjm mind sharing the errors you're getting?
OVERLORD commented 2026-02-04 21:20:22 +03:00
Author
Owner
Copy Link

@Thyr1stor commented on GitHub (Apr 6, 2025):

not working here too

i get this error when i use "update" and hoarder nukes itself

✔️ Stopped Services
⠏ Updating Hoarder to v0.23.1mv: cannot stat 'hoarder-0.23.1': No such file or directory

[ERROR] in line 51: exit code 0: while executing command mv hoarder-${RELEASE} /opt/hoarder

@Thyr1stor commented on GitHub (Apr 6, 2025): not working here too i get this error when i use "update" and hoarder nukes itself ✔️ Stopped Services ⠏ Updating Hoarder to v0.23.1mv: cannot stat 'hoarder-0.23.1': No such file or directory [ERROR] in line 51: exit code 0: while executing command mv hoarder-${RELEASE} /opt/hoarder
OVERLORD commented 2026-02-04 21:20:25 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Apr 6, 2025):

Ah I see, it seems that those two lines, b395a1846c/install/hoarder-install.sh (L65-L66) will need to be updated. The zip archive used to unzip to hoarder-${RELEASE}, now it unzips to karakeep-${RELEASE}.

Also, we should seriously consider not nuking the old installation until the new one is ready and ready to replace the old one. Basically preparing the new installation in a temp dir, and only stopping the services when the temp dir is ready to be renamed to /opt/hoarder.

@MohamedBassem commented on GitHub (Apr 6, 2025): Ah I see, it seems that those two lines, https://github.com/community-scripts/ProxmoxVE/blob/b395a1846c18ceb3899a5e4ba5b2824571c2f6bd/install/hoarder-install.sh#L65-L66 will need to be updated. The zip archive used to unzip to `hoarder-${RELEASE}`, now it unzips to `karakeep-${RELEASE}`. Also, we should seriously consider not nuking the old installation until the new one is ready and ready to replace the old one. Basically preparing the new installation in a temp dir, and only stopping the services when the temp dir is ready to be renamed to `/opt/hoarder`.
OVERLORD commented 2026-02-04 21:20:29 +03:00
Author
Owner
Copy Link

@divemasterjm commented on GitHub (Apr 6, 2025):

@divemasterjm mind sharing the errors you're getting?

✔️ Stopped Services
⠹ Updating Hoarder to v0.23.1mv: cannot stat 'hoarder-0.23.1': No such file or directory
⠸ Updating Hoarder to v0.23.1
[ERROR] in line 51: exit code 0: while executing command mv hoarder-${RELEASE} /opt/hoarder

root@hoarder:/opt/hoarder#

@divemasterjm commented on GitHub (Apr 6, 2025): > [@divemasterjm](https://github.com/divemasterjm) mind sharing the errors you're getting? ✔️ Stopped Services ⠹ Updating Hoarder to v0.23.1mv: cannot stat 'hoarder-0.23.1': No such file or directory ⠸ Updating Hoarder to v0.23.1 [ERROR] in line 51: exit code 0: while executing command mv hoarder-${RELEASE} /opt/hoarder root@hoarder:/opt/hoarder#
OVERLORD commented 2026-02-04 21:20:37 +03:00
Author
Owner
Copy Link

@antibyte commented on GitHub (Apr 6, 2025):

My install was nuked after update also

@antibyte commented on GitHub (Apr 6, 2025): My install was nuked after update also
OVERLORD commented 2026-02-04 21:20:41 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Apr 6, 2025):

Sorry for the hassle guys. Don't worry, your data will be safe once the update script is fixed.

@MohamedBassem commented on GitHub (Apr 6, 2025): Sorry for the hassle guys. Don't worry, your data will be safe once the update script is fixed.
OVERLORD commented 2026-02-04 21:20:44 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 6, 2025):

#3699

@MohamedBassem can you take a short look over the migration?

@MickLesk commented on GitHub (Apr 6, 2025): #3699 @MohamedBassem can you take a short look over the migration?
OVERLORD commented 2026-02-04 21:20:47 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Apr 6, 2025):

@MickLesk That was fast! I'll have a look in the next two days (if you don't mind).

In the meanwhile, how about we send a quick fix for mv hoarder-${RELEASE} /opt/hoarder to be mv karakeep-${RELEASE} /opt/hoarder to prevent further breakages to people's installations until the full migration lands?

@MohamedBassem commented on GitHub (Apr 6, 2025): @MickLesk That was fast! I'll have a look in the next two days (if you don't mind). In the meanwhile, how about we send a quick fix for `mv hoarder-${RELEASE} /opt/hoarder` to be `mv karakeep-${RELEASE} /opt/hoarder` to prevent further breakages to people's installations until the full migration lands?
OVERLORD commented 2026-02-04 21:20:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 6, 2025):

This may break all the services and env files.

Maybe I'll split the PR (Kakakeep as “new script” and remove the update function from Hoarder first)

@MickLesk commented on GitHub (Apr 6, 2025): This may break all the services and env files. Maybe I'll split the PR (Kakakeep as “new script” and remove the update function from Hoarder first)
OVERLORD commented 2026-02-04 21:21:01 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Apr 6, 2025):

@MickLesk I don't think it will. It's basically just the zipped directory's name got changed when you unzip the release files from github. This change doesn't touch any of the persistent files (notice how the release is still being copied to /opt/hoarder).

@MohamedBassem commented on GitHub (Apr 6, 2025): @MickLesk I don't think it will. It's basically just the zipped directory's name got changed when you unzip the release files from github. This change doesn't touch any of the persistent files (notice how the release is still being copied to `/opt/hoarder`).
OVERLORD commented 2026-02-04 21:21:09 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 6, 2025):

at first, i do this so in the PR. Migration is stored on my pc. New Installs will be karakeep only

@MickLesk commented on GitHub (Apr 6, 2025): at first, i do this so in the PR. Migration is stored on my pc. New Installs will be karakeep only
OVERLORD commented 2026-02-04 21:21:13 +03:00
Author
Owner
Copy Link

@prabhjotsbhatia-ca commented on GitHub (Apr 7, 2025):

For anyone like @antibyte @divemasterjm who's stuck with a non functional hoarder install after trying to update using the existing script, this is how I got it working:

  1. Logged into the LXC
 mv /opt/karakeep-* /opt/hoarder
  1. And then executed the rest of the script https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/hoarder-install.sh manually line by line, starting with cd /opt/hoarder.
@prabhjotsbhatia-ca commented on GitHub (Apr 7, 2025): For anyone like @antibyte @divemasterjm who's stuck with a non functional hoarder install after trying to update using the existing script, this is how I got it working: 1. Logged into the LXC ``` mv /opt/karakeep-* /opt/hoarder ``` 2. And then executed the rest of the script https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/hoarder-install.sh manually line by line, starting with `cd /opt/hoarder`.
OVERLORD commented 2026-02-04 21:21:15 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 7, 2025):

already merged

@MickLesk commented on GitHub (Apr 7, 2025): already merged
OVERLORD commented 2026-02-04 21:21:20 +03:00
Author
Owner
Copy Link

@Thyr1stor commented on GitHub (Apr 7, 2025):

already merged

yep - worked fine for me - thank you!

@Thyr1stor commented on GitHub (Apr 7, 2025): > already merged yep - worked fine for me - thank you!
OVERLORD commented 2026-02-04 21:21:25 +03:00
Author
Owner
Copy Link

@petrsimunek commented on GitHub (Apr 7, 2025):

I faced the same issue yesterday. I tried it again today, and it didn't work. Because I used the old command from yesterday. 😃
The new command works. Thank you! 👍

@petrsimunek commented on GitHub (Apr 7, 2025): I faced the same issue yesterday. I tried it again today, and it didn't work. **Because I used the old command from yesterday.** 😃 The new command works. Thank you! 👍
OVERLORD commented 2026-02-04 21:21:31 +03:00
Author
Owner
Copy Link

@shuperluu commented on GitHub (Apr 7, 2025):

To update Hoarder to Karakeep I can run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)" inside the Hoarder LXC?

@shuperluu commented on GitHub (Apr 7, 2025): To update Hoarder to Karakeep I can run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"` inside the Hoarder LXC?
OVERLORD commented 2026-02-04 21:21:33 +03:00
Author
Owner
Copy Link

@prabhjotsbhatia-ca commented on GitHub (Apr 7, 2025):

already merged

Thank you. It isn't clear whether the script would actually work for someone stuck midway - it had removed hoarder without updating.

@prabhjotsbhatia-ca commented on GitHub (Apr 7, 2025): > already merged Thank you. It isn't clear whether the script would actually work for someone stuck midway - it had removed hoarder without updating.
OVERLORD commented 2026-02-04 21:21:39 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 7, 2025):

To update Hoarder to Karakeep I can run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)" inside the Hoarder LXC?

Hoarder until its migrated

@MickLesk commented on GitHub (Apr 7, 2025): > To update Hoarder to Karakeep I can run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"` inside the Hoarder LXC? Hoarder until its migrated
OVERLORD commented 2026-02-04 21:21:42 +03:00
Author
Owner
Copy Link

@shuperluu commented on GitHub (Apr 7, 2025):

To update Hoarder to Karakeep I can run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)" inside the Hoarder LXC?

Hoarder until its migrated

Thank you. I try it again two more times as hoarder.sh and it finished the update to Karakeep v0.23.1 and is working.

@shuperluu commented on GitHub (Apr 7, 2025): > > To update Hoarder to Karakeep I can run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"` inside the Hoarder LXC? > > Hoarder until its migrated Thank you. I try it again two more times as hoarder.sh and it finished the update to Karakeep v0.23.1 and is working.
OVERLORD commented 2026-02-04 21:21:47 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 8, 2025):

Yep, but in next time maybe it need an bigger manual change (Service Files and co). I write it down in next days

@MickLesk commented on GitHub (Apr 8, 2025): Yep, but in next time maybe it need an bigger manual change (Service Files and co). I write it down in next days
OVERLORD commented 2026-02-04 21:21:58 +03:00
Author
Owner
Copy Link

@derdems commented on GitHub (Apr 8, 2025):

Hi there,
arriving here from reddit, sent by MohamedBassem himself!
I experience the following when running bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)":
✖️ No karakeep Installation Found!
It obviously makes sense as the script wants to work directories called karakeep while it is still all called hoarder.
I sense it should be easy enough to just rename all important parts to karakeep.
Can someone please nudge me into the right direction of what these renamings should be?

@derdems commented on GitHub (Apr 8, 2025): Hi there, arriving here from reddit, sent by [MohamedBassem](https://github.com/MohamedBassem) himself! I experience the following when running `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"`: ` ✖️ No karakeep Installation Found!` It obviously makes sense as the script wants to work directories called karakeep while it is still all called hoarder. I sense it should be easy enough to just rename all important parts to karakeep. Can someone please nudge me into the right direction of what these renamings should be?
OVERLORD commented 2026-02-04 21:22:04 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 8, 2025):

You use the wrong script.

The karakeep Script is only for new karakeep installs

@MickLesk commented on GitHub (Apr 8, 2025): You use the wrong script. The karakeep Script is only for new karakeep installs
OVERLORD commented 2026-02-04 21:22:06 +03:00
Author
Owner
Copy Link

@derdems commented on GitHub (Apr 8, 2025):

Thanks for the response!
Which one is the correct script to use?
When I bash hoarder-linux.sh update it returns

Checking for an update...
Caught error 1 on line 258

To clarify: hoarder-linux.sh is the script that was installed on initial install.
As far as I understood, running hoarder-linux.sh update would be the regular method as intended originally?
tiA, dems

@derdems commented on GitHub (Apr 8, 2025): Thanks for the response! Which one is the correct script to use? When I `bash hoarder-linux.sh update` it returns ``` Checking for an update... Caught error 1 on line 258 ``` To clarify: hoarder-linux.sh is the script that was installed on initial install. As far as I understood, running hoarder-linux.sh update would be the regular method as intended originally? tiA, dems
OVERLORD commented 2026-02-04 21:22:09 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 8, 2025):

Heh wtf? Never heard of this Script. Just like in all other Scripts. update or bash install command of the app

@MickLesk commented on GitHub (Apr 8, 2025): Heh wtf? Never heard of this Script. Just like in all other Scripts. update or bash install command of the app
OVERLORD commented 2026-02-04 21:22:11 +03:00
Author
Owner
Copy Link

@Kogoro commented on GitHub (Apr 9, 2025):

Yep, but in next time maybe it need an bigger manual change (Service Files and co). I write it down in next days

Just as a little help: As the .env file is relocated in line 46 of the update script, hoarder-web.service and hoarder-workers.service need to be updated to point to the right location under /etc/hoarder/. Everything else was working for me fine.
54db498942/ct/hoarder.sh (L46)

Thanks for the response! Which one is the correct script to use? When I bash hoarder-linux.sh update it returns

Checking for an update...
Caught error 1 on line 258

To clarify: hoarder-linux.sh is the script that was installed on initial install. As far as I understood, running hoarder-linux.sh update would be the regular method as intended originally? tiA, dems

This is indeed a file directly from karakeep and is used for bare metal installations. As the paths are at least partly different, it can't be used with community scripts.

@Kogoro commented on GitHub (Apr 9, 2025): > Yep, but in next time maybe it need an bigger manual change (Service Files and co). I write it down in next days Just as a little help: As the .env file is relocated in line 46 of the update script, hoarder-web.service and hoarder-workers.service need to be updated to point to the right location under /etc/hoarder/. Everything else was working for me fine. https://github.com/community-scripts/ProxmoxVE/blob/54db49894224a19a4794154c44d4bf09e068f632/ct/hoarder.sh#L46 > Thanks for the response! Which one is the correct script to use? When I `bash hoarder-linux.sh update` it returns > > ``` > Checking for an update... > Caught error 1 on line 258 > ``` > > To clarify: hoarder-linux.sh is the script that was installed on initial install. As far as I understood, running hoarder-linux.sh update would be the regular method as intended originally? tiA, dems This is indeed a file directly from karakeep and is used for bare metal installations. As the paths are at least partly different, it can't be used with community scripts.
OVERLORD commented 2026-02-04 21:22:16 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

https://github.com/community-scripts/ProxmoxVE/discussions/3764

Anyone need to check it, if all is correct by running your own instance. For me it worked in my dev setup

@MickLesk commented on GitHub (Apr 9, 2025): https://github.com/community-scripts/ProxmoxVE/discussions/3764 Anyone need to check it, if all is correct by running your own instance. For me it worked in my dev setup
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label investigation rename script update script
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#758
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?