From dev-return-8976-archive-asf-public=cust-asf.ponee.io@allura.apache.org Wed Nov 14 19:34:35 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 067BF180676 for ; Wed, 14 Nov 2018 19:34:34 +0100 (CET) Received: (qmail 73614 invoked by uid 500); 14 Nov 2018 18:34:34 -0000 Mailing-List: contact dev-help@allura.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@allura.apache.org Delivered-To: mailing list dev@allura.apache.org Received: (qmail 73535 invoked by uid 99); 14 Nov 2018 18:34:33 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2018 18:34:33 +0000 Received: from allura-vm2.apache.org (unknown [62.210.60.238]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPS id 8680A47B0 for ; Wed, 14 Nov 2018 18:34:32 +0000 (UTC) Received: from [172.18.0.10] (unknown [172.18.0.10]) by allura-vm2.apache.org (ASF Mail Server at allura-vm2.apache.org) with ESMTPS id EBC4BA000C for ; Wed, 14 Nov 2018 18:34:29 +0000 (UTC) Content-Type: multipart/related; boundary="===============7454844604483370979==" MIME-Version: 1.0 To: dev@allura.apache.org From: "Vrinda" Reply-To: "[allura:tickets] " <8262@tickets.allura.p.forge-allura.apache.org> Subject: [allura:tickets] #8262 System configuration for production environment Message-ID:

Date: Wed, 14 Nov 2018 18:34:29 -0000 Sender: tickets@allura.p.forge-allura.apache.org In-Reply-To: <5be96277c82918083ce23720.tickets@allura.p.forge-allura.apache.org> References: <5be96277c82918083ce23720.tickets@allura.p.forge-allura.apache.org> --===============7454844604483370979== Content-Type: multipart/alternative; boundary="===============6421280557302739221==" MIME-Version: 1.0 --===============6421280557302739221== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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://: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. --===============6421280557302739221== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

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 ip="" server's="">:27017
and ming configurations to point to the MongoDB server.
Anything else that I need to change in Allura configurations?</mongodb>

[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.

--===============6421280557302739221==-- --===============7454844604483370979==--