Install on Subdomain for better performance?
Hey there!
Is it recommended to install FluentCommunity on a subdomain of your site in order to avoid overload to the main site and database?
This is also assuming using Cloudflare R2 for media storage and Loom for all course videos, etc.
It depends on your use case. We used a sub-domain because when we started using it early this year it was super unstable.
Shahjahan Jewel - What situations would call for installing FC on a subdomain? What considerations should one make?
Chris Moore Let's say your domain is a marketing site like content, landing pages etc. Then you may use a sub domain to install the community and other functional plugins to run your whole business.
Shahjahan Jewel pls, any guide on how to install on subdomain? It's enforcing me to add a slug and that's my challenge
But for speed and resource reasons it is not necessary to separate the FC instance from the main website, right?
Thomas Fischer That should not be the reason. FluentCommunity does not store any data to default WordPress tables so basically it will not slow down your regular WP pages. All the requests are over WP REST API and powered by VueJS 3.
Of course, it will take server memory and CPU but based on your con-current user traffic you can always upgrade your server.
Shahjahan Jewel Thank you, good to know 👍
For our setup, I’ve decided to create separate instances for better organization and optimization. We sell plugins related to LearnDash, and we also have LearnDash itself installed, along with a community platform. With so many plugins in play, maintaining optimal performance has become an art.
To simplify things, we’re splitting everything into three distinct sites:
- Main Site: Focused on plugin sales and related activities.
- Academy Site: Dedicated solely to hosting courses. We have a lot of plugins for this, and separating it from the main site will make testing and management much easier.
- Community Site: A streamlined, lean space for community engagement.
Our current site is fast, but keeping it that way requires effort and careful optimization. Separating these components not only improves performance but also makes troubleshooting significantly easier.
If your setup is simpler and you don’t have a lot going on, keeping everything in one place might work just fine. But for us, this approach makes sense.
Ryk Melck and how about users, you're syncing users with wp remote user sync?