From: Chris Brannon <chris@the-brannons.com>
To: Adam Thompson <arthompson1990@gmail.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] wordexp again
Date: Sat, 18 Apr 2015 16:03:46 -0700 [thread overview]
Message-ID: <87oaml599p.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150418200508.GP5949@toaster.adamthompson.me.uk> (Adam Thompson's message of "Sat, 18 Apr 2015 21:05:08 +0100")
Adam Thompson <arthompson1990@gmail.com> writes:
> Hmmm, what about sftp only ssh accounts chrooted to the web dir? Would that work?
I need a public key from each of you.
Yes, this sounds really good! sftp for you guys, chrooted to the
edbrowse web directory. All the textual content goes into a git
repo on the VM where the site is hosted. The web server stays in sync
with that repo, and we all have push access.
I need to get cracking and figure out how to use gitolite.
It may also be time to move edbrowse off to its own subdomain,
say, edbrowse.the-brannons.com.
> I don't want to host the edbrowse website on github,
> that's not a web hosting platform.
Well that isn't its primary intent, but with Github Pages, you can turn
it into a web hosting platform, if all your content is static text.
Lots of people are hosting blogs on it these days, for better or worse.
I have my own complaints about GitHub, though.
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
Karl Dahlke
` Adam Thompson
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Karl Dahlke
` Adam Thompson
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Chris Brannon
` Adam Thompson
` Chris Brannon [this message]
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
` Adam Thompson
` Karl Dahlke
-- strict thread matches above, loose matches on Subject: below --
Karl Dahlke
Karl Dahlke
` Chris Brannon
Chris Brannon
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oaml599p.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=arthompson1990@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 read-only IMAP folder(s) and NNTP newsgroup(s).