Replace Booklore with Grimmory

[Araxeus]

Booklore dev crashed out and deleted everything to do with booklore

The community now continues the project at https://github.com/grimmory-tools/grimmory

[Araxeus]

@tremor021 im not sure why you converted the issue (#13154) into a discussion but anyways this has obviously broken the existing booklore script, and grimmory is definitely the successor

[tremor021]

Read the replies

[Araxeus]

I'm really trying to be nice here, but you aren't being very nice. I don't really understand why. I have been nothing but respectful

[tremor021]

I told you to read the replies because @MickLesk and @dalenjohnson explained exactly what you're asking me to repeat. I'm literaly pointing you where to look, but you would like more to be offended than actualy doing what i told you to do... oh well...

Also, the mere fact that i have to write explanation about why i said that you should read replies, while the answer to your question is 2 replies down is so mentaly exhausting for me....

Now you can say i'm not nice, not before

[JcMinarro]

Many of us are following this thread for updates and potential solutions. Comments that dismiss legitimate questions with 'it’s not easy' without providing technical context don't contribute to the discussion.

Furthermore, the condescending tone toward @Araxeus is unnecessary. He has been respectful and constructive throughout this transition, simply asking for clarification. There is no need for such an arrogant approach or to imply intellectual superiority when we are all here to find a way forward after the repository's removal. Let’s keep the conversation professional and focused on the workarounds already being discussed.

[MickLesk]

#13155 (comment)

grimmory-tools/grimmory#120 (reply in thread)

[neoscaler]

it would be really nice if there would be a migration path to Grimmory.

[JcMinarro]

Looks like they keep it backward compatible:

Upgrading from an existing Booklore container? Keep your current service name, container_name, database name/user, ports, and mounted volumes exactly as they are and replace only the image: line with grimmory/grimmory:<tag> or ghcr.io/grimmory-tools/grimmory:<tag>.

https://github.com/grimmory-tools/grimmory?tab=readme-ov-file#step-2-docker-compose
Adapt the previous script should be easy

[jferdom]

Here is my adaptation to the script... Tested with no problems from Booklore 2.2.0

https://pastebin.com/bQdVAJJ1

[MickLesk]

Before i take a Look,

The repo is named "grimory" but it uses f.e. "booklore-ui" as folder. In the .env are BookLore too.

If this are Changed in next weeks, we need an extra refactor. Why? Why there are old folder names? Its stupid.On top of that, there’s an extra theme. It’ll require more resources than before. What bothers me most (and this is something the ‘hardcore’ fans here don’t seem to get) is that it’s a botched fork that hasn’t even been properly thought through – the paths haven’t been adjusted properly, and neither has anything else. It makes migrating really easy for now, but in the long run it’ll do more harm than good.

[dalenjohnson]

Here is my version of the update script that I used. The one major change is that it includes setup and migration of kepubify used for Kobo Sync. There seems to be an issue with it not installing in non docker compose setups and Grimmory not being able to find the previous install location.

I agree with MickLesk there seems to be a lot of issues with this fork, at least with how fast all this is happening. Frustratingly, the original maintainer didn't give the community much choice here. Hopefully some of the things I chose to rename in the migration script don't come back to bite me in the butt later. I'll definitely be keeping my booklore backups around until all this settles down in case I need to roll back and do a fresh migration.

[MickLesk]

The @community-scripts/contributor 's team and the Helpers have agreed not to proceed with an official migration or support for Grimmory at this time.

There is currently no stable migration path, and no reliable upstream collaboration or support for this use case. The project is still undergoing active structural changes.

As a result, we will not invest time into building or maintaining a migration that may break or require rework in the near future.

If you choose to migrate, you can do so manually (e.g. via Docker) at your own risk.
We strongly recommend keeping full backups before proceeding.

For context, see:
https://github.com/orgs/grimmory-tools/discussions/120#discussioncomment-16283093

[MickLesk]

We never had any problems with the OG Booklore Maintainer.

[MathisP75]

So... it's not a flat out "No", but rather a "We will wait until things have settled" ? If so, totally understandable, but then the discussion should not be marked as closed, in the mean time.

[tremor021]

[MathisP75]

Yes, this is also what I see on my screen

[tremor021]

I'm trying to point out its closed for us, until we decide its worth checking out

[vhsdream]

I'd like to reopen this as I've just done a migration of my v2.2.0 BookLore to Grimmory. There is no longer any need to build a frontend or backend as the Releases contain the JAR file. The migration path combines that of @jferdom and @dalenjohnson with some small changes.

Still have a v2+ BookLore LXC collecting dust? Try the update from my fork after making a backup. Run the command below in your BookLore LXC:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/vhsdream/ProxmoxVE/refs/heads/grimmory-dev/ct/grimmory.sh)"

There isn't currently an install script, but it'll be pretty straightforward.

[summoningpixels]

thanks, transition from booklore to grimmory went a-ok!

[Aloe-recite]

hey @vhsdream did you remove your script? 😢 I just noticed since an update to grimmory just came out; I was relying on it since it seems that Community Scripts is not considering Grimmory at all, at least for the time being. Did you find anything wrong with it or simply decided to move on?

[knorrre]

I use BookOrbit instead. It works seamlessly and has an import function from Booklore/Grimmory to BookOrbit. It’s actively being developed and runs like clockwork.

[MickLesk]

and its faster ^^ there is an big reddit comparsion thread, that was the reason to add bookorbit

[Aloe-recite]

looks neat, quite similar and with kobo sync and OIDC which check all my needs. Will migrate tonight! Thanks!

[SpaceAgeHero]

BookLore repo is back and active for 2 weeks now.

[MickLesk]

yeah i know. i track both

[pfassina]

@MickLesk with booklore up again, would it make sense to create a separate script for grimmory?

I'm happy to give it a shot and submit it to dev if maintainers would be open to consider taking it in.

[spocoeric]

yeah i know. i track both

So how about reinstating the booklore script?

[michelroegl-brunner]

yeah i know. i track both

So how about reinstating the booklore script?

Not at the moment. Both repos are not really stable we think. So not gonna happen for now

[c-prompt]

Not discounting at all the decision (and, more importantly, the reasoning) but just wanted to reference an example of how quickly users will likely get left behind: https://github.com/orgs/grimmory-tools/discussions/1049#discussioncomment-16791518.

[JaneX8]

I would really like to see Grimmory as a community script even if there is no migration path available from Booklore.