You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2018/11/15 15:28:24 UTC
[allura:tickets] Re: #8262 System configuration for production environment
Yep, activitystream and ming entries in the .ini file are the only settings you need to change for it.
Depending on your network/firewall setup, make sure that your mongodb server is not accessible to the outside world.
---
** [tickets:#8262] System configuration for production environment**
**Status:** open
**Milestone:** unreleased
**Created:** Mon Nov 12, 2018 11:22 AM UTC by Vrinda
**Last Updated:** Wed Nov 14, 2018 06:34 PM UTC
**Owner:** nobody
I am setting up a production server to host Allura platform.
So I have some general questions before I start:
1. What is the expected system requirement/configuration for a production server to host Allura?
2. Are there any specific configurations that I need to do in Allura to get a good performance when the load is high (for >100 users)?
3. Any other points that I need to be aware about?
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.