From owner-freebsd-questions@FreeBSD.ORG Sat Dec 28 02:57:16 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3ADE5734 for ; Sat, 28 Dec 2013 02:57:16 +0000 (UTC) Received: from mail.monochrome.org (e.febed1.client.atlantech.net [209.190.254.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA09616EB for ; Sat, 28 Dec 2013 02:57:15 +0000 (UTC) Received: from [192.168.1.11] ([192.168.1.11]) by mail.monochrome.org (8.14.4/8.14.4) with ESMTP id rBS2VeYf081157; Fri, 27 Dec 2013 21:31:40 -0500 (EST) (envelope-from chris@monochrome.org) Date: Fri, 27 Dec 2013 21:31:14 -0500 (EST) From: Chris Hill To: Chris Stankevitz Subject: Re: Running FreeBSD for my personal website: collocation, cloud, etc. In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Dec 2013 02:57:16 -0000 On Fri, 27 Dec 2013, Chris Stankevitz wrote: > Can you recommend a place/procedure by which I can easily (and > cheaply) get up and running with a "publicly accessible" FreeBSD > machine connected to the internet on which I can run a web and mail > server? Maybe I'll hookup a VPN for use when I am on a public > connection (e.g. starbucks). There are lots of colo providers out there (see 2 below), but I have no personal experience with any of them. > The way I see it I have these options: > > 1. Buy and run machines from home and figure out a scheme to deal with > my dynamic ip address This is what I do, but I have a static IP. If you have a dynamic IP address, there is a good chance that your contract doesn't allow you to run servers. Your ISP may also block the ports you want, or even all ports but a few. Check your Terms and Conditions. > 2. Co-location (which I've never done but I think I understand the > concept) The idea is that you own (or rent) a machine that is physically in a data center somewhere. It "belongs" to you, so you administer it remotely and run what you want. > 3. Cloud (which I don't understand) Neither do I. It smells like "new name for an old concept", though. -- Chris Hill chris@monochrome.org ** [ Busy Expunging ]