From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH] Add note about Oort Gnus releases, and No Gnus.
Date: Sat, 18 Dec 2010 09:13:07 -0600 [thread overview]
Message-ID: <877hf7glmk.fsf@lifelogs.com> (raw)
In-Reply-To: <m3aak4fpi9.fsf@quimbies.gnus.org>
On Fri, 17 Dec 2010 15:22:22 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> ...but haven't deployed it because I forgot. I'll do it tonight unless
>> Lars beats me to it.
LMI> Go ahead... but I forgot about the HTML SCM thing, so I edited
LMI> index.html directly a few weeks back. Could you incorporate that?
I brought your change into the gnus-html repo (the clone URL is
https://git.gnus.org/gnus-html.git if anyone is interested).
I then did the deployment like this:
cd /home/tzz
sudo rm -rf gnus-html-external-worktree /var/tmp/gnus-html
git --work-tree /var/tmp/gnus-html clone git://git.gnus.org/home/gnus/html/gnus-html.git gnus-html-external-worktree
sudo chown -R www /var/tmp/gnus-html
sudo chmod -R a+rX /var/tmp/gnus-html
sudo rsync -avP --delete /var/tmp/gnus-html/ $GNUS_HTML_ROOT
...which I think is reasonable and is in /home/tzz/deploy-gnus-html.sh.
The work tree has no Git data so the rsync works nicely. The
favicon.ico was not in the repo so I added it; I believe (outside of the
*~ filed I cleaned) the deployed site is the same as before. You can
check against /home/tzz/gnus-html-initial.tgz which is a snapshot of the
old site.
If you're OK with this deployment script, I'll set it up to run
automatically on every commit to the gnus-html repo and move it to a
bin/ directory within. But the .htaccess is a security risk so you may
want to leave the deployment script manual or explicitly exclude the
.htaccess from getting rsynced or deployed.
Ted
next prev parent reply other threads:[~2010-12-18 15:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 15:47 Latest version of Gnus? Tommy Kelly
2010-11-27 16:47 ` Adam Sjøgren
2010-11-27 18:35 ` Tommy Kelly
2010-11-27 18:47 ` Adam Sjøgren
2010-12-14 23:12 ` Ted Zlatanov
2010-12-16 21:00 ` [PATCH] Add note about Oort Gnus releases, and No Gnus Adam Sjøgren
2010-12-16 21:35 ` Ted Zlatanov
2010-12-17 14:14 ` Ted Zlatanov
2010-12-17 14:22 ` Lars Magne Ingebrigtsen
2010-12-18 15:13 ` Ted Zlatanov [this message]
2010-12-18 15:20 ` Adam Sjøgren
2010-12-18 15:30 ` Ted Zlatanov
2010-12-18 15:44 ` Adam Sjøgren
2010-12-18 16:08 ` Ted Zlatanov
2010-12-18 23:29 ` Adam Sjøgren
2010-12-19 14:41 ` Ted Zlatanov
2010-12-18 18:58 ` [PATCH] " Lars Magne Ingebrigtsen
2010-12-19 14:24 ` Ted Zlatanov
2010-12-19 15:45 ` Lars Magne Ingebrigtsen
2011-03-17 11:28 ` HTML deployments from Git (was: [PATCH] Add note about Oort Gnus releases, and No Gnus.) Ted Zlatanov
2011-03-17 16:47 ` HTML deployments from Git Lars Magne Ingebrigtsen
2011-03-17 17:19 ` Ted Zlatanov
2011-03-17 17:27 ` Lars Magne Ingebrigtsen
2011-03-18 10:30 ` Ted Zlatanov
2011-03-29 18:50 ` Lars Magne Ingebrigtsen
2011-03-29 19:17 ` Ted Zlatanov
2011-03-29 19:36 ` Lars Magne Ingebrigtsen
2011-03-29 19:46 ` Ted Zlatanov
2011-03-30 10:08 ` Ted Zlatanov
2011-04-03 17:44 ` Lars Magne Ingebrigtsen
2011-04-04 10:03 ` Ted Zlatanov
2011-04-12 16:27 ` Lars Magne Ingebrigtsen
2011-04-12 17:16 ` Ted Zlatanov
2011-04-12 17:23 ` Lars Magne Ingebrigtsen
2011-04-12 17:26 ` Lars Magne Ingebrigtsen
2011-04-25 12:35 ` Ted Zlatanov
2011-05-01 14:57 ` Lars Magne Ingebrigtsen
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=877hf7glmk.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).