Codeberg storage adapter fails to create files in the right location and fails to save over files #68

5310 commented 2026年01月10日 11:48:29 +01:00 (Migrated from github.com)

The Codeberg storage adapter can read files from the repo once the path is clearly defined, but fails to save to those files, throwing: Error: Forgejo API request failed: 500 Internal Server Error

I think this issue might be related to the other and perhaps even stranger problem that happens at the same time:

1. If I try to save a completely new path that doesn't yet exist in my repo the file does get created, but always under a completely unrelated content directory, with the intended path kept in the filename with slashes escaped with %2F!
2. And yet, the adapter can read existing files on the correct path only if I set the path to src folder correctly to src, but still tries to save to content/src%2F...
3. But when it tries to save a doc to an existing file (all under content for now) it throws error 500

---

As an example, contained in this repo snapshot:

1. This repo has a src/index.yaml file that the CMS can read when I set the storage adapter to Scio/goyenda-club/src
2. And yet, when it saves the file, it does so to content/%252Findex.yaml for the first attempt.
   1. But for subsequent attempts, simply fails with error 500
3. The other two files under content were created by changing the document path for testing, please ignore them

---

I only just discovered the Codeberg storage adapter this morning. And I know that the docs don't mention its existence, so it might not be ready for use. But I couldn't help but create this issue because the adapter module itself is deployed on the CDNs.

The Codeberg storage adapter can read files from the repo once the path is clearly defined, but fails to save to those files, throwing: `Error: Forgejo API request failed: 500 Internal Server Error` I think this issue might be related to the other and perhaps even stranger problem that happens at the same time: 1. If I try to save a completely new path that doesn't yet exist in my repo the file _does_ get created, but _always_ under a completely unrelated `content` directory, with the intended path kept in the filename with slashes escaped with `%2F`! 2. And yet, the adapter can _read_ existing files on the correct path only if I set the path to src folder correctly to `src`, but still tries to save to `content/src%2F...` 3. But when it tries to save a doc to an existing file (all under `content` for now) it throws error 500 --- As an example, contained in this [repo snapshot](https://codeberg.org/Scio/goyenda-club/src/commit/ca57e3e3760012c143d75f7ee65038509bf5ebfb): 1. This repo has a `src/index.yaml` file that the CMS can read when I set the storage adapter to `Scio/goyenda-club/src` 2. And yet, when it saves the file, it does so to `content/%252Findex.yaml` for the first attempt. 1. But for subsequent attempts, simply fails with error 500 3. The other two files under `content` were created by changing the document path for testing, please ignore them --- I only just discovered the Codeberg storage adapter this morning. And I know that the [docs](https://lume.land/cms/configuration/storage/) don't mention its existence, so it might not be ready for use. But I couldn't help but create this issue because the adapter module itself is deployed on the CDNs.

oscarotero commented 2026年01月10日 13:58:37 +01:00

Yeah, I knew this error and that's why it's not mentioned yet in the docs because I didn't know why it failed.
But your comment gave me some clues and I figured out that the bug was a stupid thing. I just fixed it.

I've also made some changes in the Lume implementation to fix issues related with additional storages. Now you can overwrite the "src" storage, making it easy to switch from filesystem to a remote storage. For example:

const token = Deno.env.get("CODEBERG_TOKEN");
// overwrite "src"
if (token) {
 cms.storage("src", Codeberg.create("Scio/goyenda-club/src", token);
}

To test this, you have to upgrade Lume and LumeCMS to the latest development version (deno task lume upgrade --dev).
Let me know if you find any issue. Thanks!

Yeah, I knew this error and that's why it's not mentioned yet in the docs because I didn't know why it failed. But your comment gave me some clues and I figured out that the bug was a stupid thing. I [just fixed it](https://github.com/lumeland/cms/commit/fe1ecced177bb3e31cf2d6065d1201f7e38370cf). I've also made some changes in the Lume implementation to fix issues related with additional storages. Now you can overwrite the "src" storage, making it easy to switch from filesystem to a remote storage. For example: ```js const token = Deno.env.get("CODEBERG_TOKEN"); // overwrite "src" if (token) { cms.storage("src", Codeberg.create("Scio/goyenda-club/src", token); } ``` To test this, you have to upgrade Lume and LumeCMS to the latest development version (`deno task lume upgrade --dev`). Let me know if you find any issue. Thanks!

5310 commented 2026年01月11日 10:49:07 +01:00 (Migrated from github.com)

Working flawlessly! Thanks a lot for the multiple quick fixes. Creation edition and deletion, it all works now! Including more easily overriding the storage 🥳

Working flawlessly! Thanks a lot for the _multiple_ quick fixes. Creation edition and deletion, it all works now! Including more easily overriding the storage 🥳