From owner-freebsd-ports@FreeBSD.ORG Sun Jun 6 20:36:53 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10A3D106564A for ; Sun, 6 Jun 2010 20:36:53 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (gate6.infracaninophile.co.uk [IPv6:2001:8b0:151:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 67AF08FC1E for ; Sun, 6 Jun 2010 20:36:52 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o56KalTN084903 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 6 Jun 2010 21:36:48 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4C0C06DF.7070607@infracaninophile.co.uk> Date: Sun, 06 Jun 2010 21:36:47 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Kaya Saman References: <4C0B8B9B.5080206@netscape.net> <4C0BAE9A.7060503@netscape.net> In-Reply-To: <4C0BAE9A.7060503@netscape.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.96.1 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_50,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-ports@freebsd.org Subject: Re: Torrentflux and Zabbix Apache Include files?? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2010 20:36:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/06/2010 15:20:10, Kaya Saman wrote: > I don't know.... it is fun; lot's of fun when have the time but if > configuring for business grade production then I just feel that there > should be slightly more help in the files with templates and examples > etc.... - highly debatable of course and apologies if I sound like I'm > whining I honestly really enjoyed myself doing all this and what made it > more fun is that the systems that I did the work on are geographically > separated from myself which just shows the power of UNIX and SSH over MS > Win and RDP which to me is only for Sun Ray's and nothing more :-) . Doug already made some general comments, but on the particular subject of Apache configuration, you're right. Ported web applications generally do not install sample Apache configuration files. There are three aspects to this: * FreeBSD ports of daemons, etc. are usually installed in a disabled configuration. The sysadmin needs to take extra steps to turn everything on. While this may seem like forcing users to jump through pointless hoops to some, to many others this is a lifesaving security enhancement and foot-shooting avoidance measure. * We don't necessarily want to assume that you are using Apache as your webserver. Apache is great, but there are alternative HTTP servers in the ports which can leave it in the dust in terms of performance. * Even if you are using Apache, we don't necessarily want to assume that a 'one size fits all' configuration is going to be right for you. Having to grovel through a maze of twisty little apache configuration snippets (all alike) in order to undo some well meaning but ultimately wrong settings gets old really quickly. Especially if you have to do it again every time some related port gets updated. It's a philosophical difference between *BSD and much of the rest of the world: we think computers are there to do what the *admin* in charge tells them to do, no more and no less. Consequently we expect to take pains to tell them exactly what we want. Having said all that, many web applications will display a pkg-message on installation with hints about how to configure Apache. You can display these messages again by: % pkg_info -Dx portname There are also frequently instructions in various documentation installed under /usr/local/share. Most web apps generally want some combination of aliases to map the application directory into the web tree at an appropriate URL, plus a or block (or several) to set options, access controls, basic auth password and so forth. Given a little practice such setups are not particularly hard to write, and there are a lot of people on this list who would be happy to help with any specific problems. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwMBt8ACgkQ8Mjk52CukIzSagCdFrLouTfwa19/e7aoztf5S70x GdoAniFIYtp0GMMoWlolZoxQsqbyvtsb =1X8Q -----END PGP SIGNATURE-----