allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrinda" <vrind...@in.bosch.com>
Subject [allura:tickets] #8262 System configuration for production environment
Date Wed, 14 Nov 2018 18:34:29 GMT
Thank you very much Dave :)
I'll start with splitting MongoDB from the Allura server.

I looked around to find how I can set up MongoDB on a separate server and make it accessible
from Allura server.

One hint that I got to make the MongoDB server accessible from  Allura server is to change
the bind_ip configuration in /etc/mongod.conf to point to 0.0.0.0 so as to allow any IP to
access it
Is this all I have to do on the MongoDB server?

And in Allura's development.ini, change:
activitystream.master = mongodb://<MongoDB server's IP>:27017
and ming configurations to point to the MongoDB server.
Anything else that I need to change in Allura configurations?


---

** [tickets:#8262] System configuration for production environment**

**Status:** open
**Milestone:** unreleased
**Created:** Mon Nov 12, 2018 11:22 AM UTC by Vrinda
**Last Updated:** Tue Nov 13, 2018 03:26 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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message