9front - general discussion about 9front
 help / color / mirror / Atom feed
From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] Two file servers sharing an auth server
Date: Wed, 02 Nov 2022 16:53:52 -0700	[thread overview]
Message-ID: <BA6C0B4DDB91772882BCF6D7C43E1CAF@thinktankworkspaces.com> (raw)
In-Reply-To: <79E17F00FA0C76BA833463939866386D@eigenstate.org>

On a bigger note. I was curious about the users. Its nice to have a single auth
as mentioned by ori. But what's the bigger goal. Do you plan to have a lot of users. 
Do those users know basic unix commands to navigate around? What type of files
or media to you plan to serve?

Quoth ori@eigenstate.org:
> Quoth Nathan Zimmen-Myers <nathan@nzm.ca>:
> > 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?
> No; I thought you wanted to move or replicate the users between the
> auth servers.
> > 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
> > configuration?
> Just give them the same auth server:
> sys=foo ether=aabbccddeeff ip=
> 	auth=
> sys=bar ether=aabbccddeeff ip=
> 	auth=
> even better if you can share an fs, and
> therefore share the ndb, but you don't
> need to; just point at the auth server
> you want to use.
> you don't even need to *own* that auth
> server, though you'll need the owner of
> the auth server to add a speaksfor line
> if your hostowner is different.

  reply	other threads:[~2022-11-02 23:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 19:18 Nathan Zimmen-Myers
2022-11-02 20:23 ` ori
2022-11-02 23:53   ` william [this message]
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=BA6C0B4DDB91772882BCF6D7C43E1CAF@thinktankworkspaces.com \
    --to=william@thinktankworkspaces.com \
    --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).