9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Nathan Zimmen-Myers <nathan@nzm.ca>
To: 9front@9front.org
Subject: [9front] Two file servers sharing an auth server
Date: Wed, 2 Nov 2022 15:18:04 -0400	[thread overview]
Message-ID: <CABaXbEYtEwE3Upjv5gZfgBgvP26SJUfDZzyAcWbpVz5j=7WMeQ@mail.gmail.com> (raw)

Hello all,

I'm still somewhat new to getting 9 set up in a distributed way, and
am struggling to have two separate fileservers sharing an auth server.
Firstly, I want to confirm that this is feasible and (relatively)
common. If this is uncommon/incorrect, is it preferable to maintain
localized documents on a non-OS drive, while booting from an auth

The initial goal that I had started with, was to have a web server
installation that boots from disk, but obtains authentication
information from an authentication server with which it does not share
a disk.

To illustrate: fs1 hosts auth with its own fileserver, currently
nothing else. web1 hosts a fileserver and will host an httpd. These
VPSs are both hosted in the same Vultr datacenter, so the latency
between them is minimal.

As ori mentioned in IRC, keyfs is used to maintain the authentication
database which can be queried remotely (I believe? this might not be a
correct interpretation), is it correct to simply mount keyfs on web1
from fs1?

The other option which comes to mind, is to boot web1 from fs1, and
use web1's disk for documents to be connected to httpd, which may make
long-term maintenance easier. Would this be a more common

My assumption is that web1 should not get all of its web documents
from fs1, as this would duplicate traffic - and I am happy if I am

Thanks all!


             reply	other threads:[~2022-11-02 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 19:18 Nathan Zimmen-Myers [this message]
2022-11-02 20:23 ` ori
2022-11-02 23:53   ` william
2022-11-03  0:43     ` Nathan Zimmen-Myers
2022-11-03  9:28       ` Steve Simon
2022-11-03 10:33         ` sirjofri
2022-11-03 20:57           ` Steve Simon
2022-11-04  0:00             ` william
2022-11-04  6:58             ` sirjofri
2022-11-04  7:09               ` william
2022-11-04  8:29                 ` sirjofri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABaXbEYtEwE3Upjv5gZfgBgvP26SJUfDZzyAcWbpVz5j=7WMeQ@mail.gmail.com' \
    --to=nathan@nzm.ca \
    --cc=9front@9front.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).