From: sirjofri <email@example.com>
Subject: Re: [9front] Two file servers sharing an auth server
Date: Thu, 3 Nov 2022 11:33:56 +0100 (GMT+01:00) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
03.11.2022 10:30:27 Steve Simon <email@example.com>:
> having the web server boot diskless is very nice, if its content is small that is enough.
> for a little extra performance you can copy the web content to a ramfs at boot.
> if the content is big you could mount a local spinning/ssd at boot onto /usr/web and serve that, but having a diskless web and cpu servers makes things very clean and easy to maintain.
Not to mention there's also cfs which can be nice for bigger stuff. Afaik it works by caching all accessed files on a local disk (except they're changed on the server) and all writes go to the server directly.
next prev parent reply other threads:[~2022-11-03 10:36 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
2022-11-03 0:43 ` Nathan Zimmen-Myers
2022-11-03 9:28 ` Steve Simon
2022-11-03 10:33 ` sirjofri [this message]
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
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 \
* 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).