Using put to change a forgejo instance_id has no (immediate) effect on inbox list #236

Open
opened 2026-06-25 10:59:31 +00:00 by mih · 1 comment
Owner

Initially the instance_id was set to none. This caused inbox names like

forgejo-a104f6f4cc21f713989fd8295a83677b-user-mih

a bit of a mouthful, so I set the instance_id to "psyinfhub", using the PUT /collections endpoint. This work, as far as a subsequent GET reflects the change. However, a query via dtc does not reflect it, still shows the previous name. A service restart does not change this.

Looking server-side, I still see the inbox directory under the old name (and also in addition under the name where it was before instance_ids.

Keeping those, rather than migrating makes sense. It should become documented behavior, though.

Initially the `instance_id` was set to `none`. This caused inbox names like `forgejo-a104f6f4cc21f713989fd8295a83677b-user-mih` a bit of a mouthful, so I set the `instance_id` to "psyinfhub", using the PUT `/collections` endpoint. This work, as far as a subsequent GET reflects the change. However, a query via `dtc` does not reflect it, still shows the previous name. A service restart does not change this. Looking server-side, I still see the inbox directory under the old name (and also in addition under the name where it was before instance_ids. Keeping those, rather than migrating makes sense. It should become documented behavior, though.
mih changed title from Using put to change a forgejo instance_id has no effect on inbox list to Using put to change a forgejo instance_id has no (immediate) effect on inbox list 2026-06-25 11:00:28 +00:00
Owner

Yes, both inboxes, i.e., the "old" and the "new" will still exist. Newly posted records will be written to the "new" inbox as soon as it is configured. There is no automated migration from the "old" inbox to the new "inbox".

I will add it to the documentation.

Yes, both inboxes, i.e., the "old" and the "new" will still exist. Newly posted records will be written to the "new" inbox as soon as it is configured. There is no automated migration from the "old" inbox to the new "inbox". I will add it to the documentation.
cmo closed this issue 2026-07-08 13:22:22 +00:00
cmo reopened this issue 2026-07-08 14:24:09 +00:00
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
orinoco/dump-things-service#236
No description provided.