#prosodyim — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #prosodyim, aggregated by home.social.
-
For those who run #ProsodyIM as #xmpp server, I did something simple but effective in my failover architecture:
- 2 Prosody instances in two different regions in a datacenter
- lsyncd syncing from primary to stand by instance all data
- an entrypoint script supervising Prosody execution
- a lock file controlling if entrypoint script can up Prosody
- a daemon checking if floating ip is linked to hosts and controlling the lock file and the lsyncd execution and configuration to primary/standby modes
Perfect solution? Of course not.
Effective solution? Hell yeah.:isacloud: :isacloudim:
-
For those who run #ProsodyIM as #xmpp server, I did something simple but effective in my failover architecture:
- 2 Prosody instances in two different regions in a datacenter
- lsyncd syncing from primary to stand by instance all data
- an entrypoint script supervising Prosody execution
- a lock file controlling if entrypoint script can up Prosody
- a daemon checking if floating ip is linked to hosts and controlling the lock file and the lsyncd execution and configuration to primary/standby modes
Perfect solution? Of course not.
Effective solution? Hell yeah.:isacloud: :isacloudim:
-
For those who run #ProsodyIM as #xmpp server, I did something simple but effective in my failover architecture:
- 2 Prosody instances in two different regions in a datacenter
- lsyncd syncing from primary to stand by instance all data
- an entrypoint script supervising Prosody execution
- a lock file controlling if entrypoint script can up Prosody
- a daemon checking if floating ip is linked to hosts and controlling the lock file and the lsyncd execution and configuration to primary/standby modes
Perfect solution? Of course not.
Effective solution? Hell yeah.:isacloud: :isacloudim:
-
For those who run #ProsodyIM as #xmpp server, I did something simple but effective in my failover architecture:
- 2 Prosody instances in two different regions in a datacenter
- lsyncd syncing from primary to stand by instance all data
- an entrypoint script supervising Prosody execution
- a lock file controlling if entrypoint script can up Prosody
- a daemon checking if floating ip is linked to hosts and controlling the lock file and the lsyncd execution and configuration to primary/standby modes
Perfect solution? Of course not.
Effective solution? Hell yeah.:isacloud: :isacloudim:
-
For those who run #ProsodyIM as #xmpp server, I did something simple but effective in my failover architecture:
- 2 Prosody instances in two different regions in a datacenter
- lsyncd syncing from primary to stand by instance all data
- an entrypoint script supervising Prosody execution
- a lock file controlling if entrypoint script can up Prosody
- a daemon checking if floating ip is linked to hosts and controlling the lock file and the lsyncd execution and configuration to primary/standby modes
Perfect solution? Of course not.
Effective solution? Hell yeah.:isacloud: :isacloudim:
-
#Prosody 13.0.2 has been released (#XMPP / #Jabber / #ProsodyIM / #Lua / #lxmppd / #SCRAM / #SCRAMSHA / #SCRAMSHA1 / #SCRAMSHA256) https://prosody.im/
-
#Prosody 13.0.1 has been released (#XMPP / #Jabber / #ProsodyIM / #Lua / #lxmppd / #SCRAM / #SCRAMSHA / #SCRAMSHA1 / #SCRAMSHA256) https://prosody.im/
-
#Prosody 13.0.0 has been released (#XMPP / #Jabber / #ProsodyIM / #Lua / #lxmppd / #SCRAM / #SCRAMSHA / #SCRAMSHA1 / #SCRAMSHA256) https://prosody.im/