Edit history

Earlier versions of New Voice System: allow multiple self-hosted instances to use the same New Voice System instance, newest first.

Current version | Edited by Rex
Changes
This way, I can get higher performance nodes around the world instead of multiple lower-performance nodes in the same locations, for New Voice System servers.Removed: ### ChecksRemoved: Removed: - ☑ I searched existing discussions.Removed:
Show

New Voice System: allow multiple self-hosted instances to use the same New Voice System instance

Problem

I run multiple Fluxer instances. I want to reduce resource usage and share 1 New Voice System server with multiple self-hosted Fluxer instances.

Proposal

Instead of only allowing 1 self-hosted instance to connect to a New Voice System instance, multiple self-hosted instances should be able to use/share a single New Voice System instance.

Notes

This way, I can get higher performance nodes around the world instead of multiple lower-performance nodes in the same locations, for New Voice System servers.
Original by Rex
Show

New Voice System: allow multiple self-hosted instances to use the same New Voice System instance

Problem

I run multiple Fluxer instances. I want to reduce resource usage and share 1 New Voice System server with multiple self-hosted Fluxer instances.

Proposal

Instead of only allowing 1 self-hosted instance to connect to a New Voice System instance, multiple self-hosted instances should be able to use/share a single New Voice System instance.

Notes

This way, I can get higher performance nodes around the world instead of multiple lower-performance nodes in the same locations, for New Voice System servers.

Checks

  • ☑ I searched existing discussions.