emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Jeff Horn <jrhorn424@gmail.com>
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Publishing htaccess files with a project
Date: Sat, 16 Oct 2010 18:39:16 +0200	[thread overview]
Message-ID: <87pqvam6rv.fsf@gmx.de> (raw)
In-Reply-To: <AANLkTikKbGLzOG8N_1SdyWhJq4wApQkFErMaVtUCrxmE@mail.gmail.com> (Jeff Horn's message of "Fri, 15 Oct 2010 21:01:46 -0400")

Jeff Horn <jrhorn424@gmail.com> writes:
> Hi orgsters,
>
> I'm wondering how I should publish .htaccess files? My current setup
> is a source directory under ~/org/, which is kept at Dropbox, and a
> publishing directory under ~/Sites/, which is not. Since data loss is
> pyschologically crippling, I like to keep *all* my source files
> (images, css, whatnot) in the source directory.
>
> I have a static project setup that pushes css, images, and a few other
> filetypes to the publishing directory. How can I do the same with
> .htaccess? I tried adding "htaccess" to :base-extenstions, but that
> unfortunately did nothing.

Hi Jeff,



use the property :include :

 (setq org-publish-project-alist
     '(("org-htaccess"
         :base-directory "~/org/"
         :recursive t
         :base-extension "xxx"    ;; non-exestent
         :include (".htaccess")
         :publishing-directory "~/public_html/"
         :publishing-function org-publish-attachment)
  ...


and make "org-htaccess" part of your compound project.



  Sebastian

  reply	other threads:[~2010-10-16 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16  1:01 Publishing htaccess files with a project Jeff Horn
2010-10-16 16:39 ` Sebastian Rose [this message]
2010-10-20  4:53   ` Jeff Horn
2010-10-20 16:14     ` Sebastian Rose
2010-10-20 16:27       ` Jeff Horn
2010-10-20 17:28         ` Sebastian Rose
2010-10-20 20:21           ` Jeff Horn

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87pqvam6rv.fsf@gmx.de \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=jrhorn424@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).