From owner-freebsd-questions@freebsd.org Mon Jan 29 13:21:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA49EEC6B34 for ; Mon, 29 Jan 2018 13:21:56 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward102p.mail.yandex.net (forward102p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0428E72867 for ; Mon, 29 Jan 2018 13:21:55 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback8j.mail.yandex.net (mxback8j.mail.yandex.net [IPv6:2a02:6b8:0:1619::111]) by forward102p.mail.yandex.net (Yandex) with ESMTP id 677424302C77; Mon, 29 Jan 2018 16:21:44 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback8j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id fCeTeEeAcf-LioWfvOY; Mon, 29 Jan 2018 16:21:44 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1517232104; bh=j4YHJjVl3au513vwasvf7cE6+uTPrBfta0Ze+/p3LZs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=NVs+ge22m+aO81SSSrp8ARfy9Wy8UXkgUqWjWkPXb6SSpzgF6GVgb/fPXT/KS5cGz dK1NIbAGW+joU9dwKMEyx8/UeCnEo88DLD4OodTGfl/lI/pyDfdhG5c0gFsecNWmD5 +i3WoKPNQL1K6O+LpMqjrJFiCGbrYg6rmdRMIO7A= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id qqfMmW6xiu-LhdW9pea; Mon, 29 Jan 2018 16:21:43 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1517232103; bh=j4YHJjVl3au513vwasvf7cE6+uTPrBfta0Ze+/p3LZs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=TA4eD9Sr9iq3uB7wGg6svu2nBPQUjX2tu+gIn4+eH1Opwfh83ydKIXaOwBiIsh9Jp idfe+XhqBSUNg+kSOW7q5uazi1UTowtHHf8H42pC0pmmIUlobwKWVNOnJxXfeekLiN ORxe6NfeYqH67Jst6h0bsPBiFAQezqAG1vdbqCgs= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: Setting up an https accessible git server on FreeBSD To: David Mehler , freebsd-questions References: From: Boris Samorodov Message-ID: <62e7858b-b2ba-ce1b-6150-c302dcfe7dd1@passap.ru> Date: Mon, 29 Jan 2018 16:21:43 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 13:21:56 -0000 29.01.2018 04:10, David Mehler пишет: > If anyone has a git server going on FreeBSD, accessible via http smart > protocol https only, i'd appreciate knowing how you got it going? I'm > wanting to make private repos accessible to myself and a select group > of users invisible to everyone else. I use www/gitea for git repositories. Nice and fast enough tool. It listens at localhost only: [...] [server] HTTP_ADDR = 127.0.0.1 HTTP_PORT = 3333 [...] While for HTTPS I use www/nginx reverse proxy: [...] listen 443 ssl; location / { proxy_pass http://localhost:3333; } [...] HTH -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve