Using put to change a forgejo instance_id has no (immediate) effect on inbox list #236
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
orinoco/dump-things-service#236
Loading…
Reference in a new issue
No description provided.
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?
Initially the
instance_idwas set tonone. This caused inbox names likeforgejo-a104f6f4cc21f713989fd8295a83677b-user-miha bit of a mouthful, so I set the
instance_idto "psyinfhub", using the PUT/collectionsendpoint. This work, as far as a subsequent GET reflects the change. However, a query viadtcdoes 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.
Using put to change a forgejo instance_id has no effect on inbox listto Using put to change a forgejo instance_id has no (immediate) effect on inbox listYes, 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.