[GH-ISSUE #7] Group/System structure #4

New Issue

administrator · 2026-02-25T17:05:40+11:00

administrator commented

2026-02-25 17:05:40 +11:00

Originally created by @pieartsy on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/pieartsy/PluralFlux/issues/7

Currently each member is tied directly to a fluxer account id, which prevents settings for the group overall and transfer between accounts.

Making a separate database entity for the account's member groups would allow these things more easily, as well as autoproxy and group/system tags.

The proxy members would need to be transferred over from being tied to the account to being tied to a system tied to the account without data loss. At minimum the structure could be:

System:
    accountid: string
    systemid: string
    systemname: string?
    autoproxy: enum [latch/front/set/null]
    fronter: string?
    tag: string?

Originally created by @pieartsy on GitHub (Feb 22, 2026). Original GitHub issue: https://github.com/pieartsy/PluralFlux/issues/7 Currently each member is tied directly to a fluxer account id, which prevents settings for the group overall and transfer between accounts. Making a separate database entity for the account's member groups would allow these things more easily, as well as autoproxy and group/system tags. The proxy members would need to be transferred over from being tied to the account to being tied to a system tied to the account without data loss. At minimum the structure could be: ``` System: accountid: string systemid: string systemname: string? autoproxy: enum [latch/front/set/null] fronter: string? tag: string? ```

administrator added the enhancement label 2026-02-25 17:05:40 +11:00

administrator referenced this issue

2026-02-25 17:05:55 +11:00

[GH-ISSUE #4] ability to add attachments #2

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/PluralFlux#4