Conversation

Notices

1. Xeon² :menheradame: (izaya@social.shadowkat.net)'s status on Tuesday, 09-Jul-2024 22:13:26 JST Xeon² :menheradame:

   • Proud owner of a potato sack :flag:
   hey @hj would clustering pleroma work? can I run multiple instances against the same DB?
   • tusooa :Cat_girls_Emoji_004: 西风 (tusooa@kazv.moe)'s status on Tuesday, 09-Jul-2024 22:13:23 JST tusooa :Cat_girls_Emoji_004: 西风

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • LS
     • Proud owner of a potato sack :flag:
     • feld
     @hj @feld @lain @lanodan @izaya you know, i had a MR (wip) making running multi-node work
   • Proud owner of a potato sack :flag: (hj@shigusegubu.club)'s status on Tuesday, 09-Jul-2024 22:13:25 JST Proud owner of a potato sack :flag:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • LS
     • feld
     @izaya i highly doubt it but i'm far from being expert. @lain @lanodan @feld might know better
   • feld (feld@bikeshed.party)'s status on Tuesday, 09-Jul-2024 22:13:55 JST feld

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • LS
     • Proud owner of a potato sack :flag:
     • tusooa :Cat_girls_Emoji_004: 西风
     @tusooa @lain @lanodan @hj @izaya
     
     I think it's possible and we should support it.
     
     Phoenix channels, sessions, etc are multi node aware
     
     Oban is multi node aware
     
     Cachex can be made multi-node aware
     
     ConfigDB changes could be made into broadcasts
     
     Other things could probably be solved with Singleton
     
     Supporting this should finally give us Pleroma 3.0