First preview version of the updated Grimoire is here!

[goniszewski]

It is my pleasure to announce the release of Grimoire v0.4.0-pre.1, a preview of our extensively refactored project. This version brings significant improvements and simplifications:

🚀 Streamlined Setup: Now runs in a single container - no more separate PocketBase container!
⚡ Enhanced Performance: We've migrated to Bun for faster operations and are connecting to the database directly with Drizzle ORM.
🛠️ Improved Maintainability: The new architecture is easier to maintain, extend and deploy.

Try it out now:
docker pull goniszewski/grimoire:develop

I can't wait to hear your feedback on this significant step for Grimoire. Give it a spin and share with us know what you think!

Link to preview release: https://github.com/goniszewski/grimoire/releases/tag/v0.4.0-pre.1

Happy bookmarking! 📚✨

[SnowyJaguar1034]

I appear to be getting "Internal Server Error" when I try to deploy the stack as is (non preview version, I think). Is it worth me doing that or would it be better if I just waited for the full release of the new version?

[goniszewski]

Hi @SnowyJaguar1034! I'd suggest starting with the preview version and then switching to the stable release later. The updated Grimoire is pretty stable and works great with the available browser extension.

[SnowyJaguar1034]

@goniszewski Thanks for the reply! I'll give the preview/pre-release version a go and get back to you on if I have any issues.

I presume the branch with the pre-release version is "develop"? It's currently pinned to the "latest" container image and not the "develop" one you mention in pre-release announcement 1.

[goniszewski]

Yeah, the README.md could be updated to reflect all the changes. Be sure to use the develop tag for the Docker image!

[SnowyJaguar1034]

Yeah, the README.md could be updated to reflect all the changes. Be sure to use the develop tag for the Docker image!

I gave the develop tag a whirl earlier today and received a 501 (or 50x) internal error code. I was trying it with some minor adjustments to make it work with portainer so I'm going to try the bone stock version tomorrow and see what I get. I'll then try troubleshooting why the error occured. I might pr the changes as they're pretty minor and should apply to any other container orchestration platform like portainer, dockge, rancher (kubernetes).