From: Ian Barton <lists@wilkesley.net>
To: emacs-orgmode@gnu.org
Subject: Re: Tangling text files
Date: Fri, 27 Jan 2012 18:13:23 +0000 [thread overview]
Message-ID: <4F22E943.9040603@wilkesley.net> (raw)
In-Reply-To: <46C672C4-4401-4ADD-8E30-68CAC7B1522F@coateconnection.com>
On 27/01/12 18:07, dlc wrote:
> How do I tangle txt to a txt file?
>
> #+TITLE: Centos 5 Apache Configuration
> #+AUTHOR: David Coate
>
> * Basic Conguration
> * Php Settings
> * Virtual Host
> e.g. for apache configuration
> ** example.com
> Use this as main website, use drupal, various other notes
>
> #+BEGIN_SRC: txt :tangle vhost.conf
> ServerName Example.com
> DocumentRoot "/var/www/example.com"
> #+END_SRC:
>
> ** companyb.com
> notes about company b.
> #+BEGIN_SRC: txt :tangle vhost.conf
> ServerName Companyb.com
> DocumentRoot "/var/www/companyb.com"
> #+END_SRC:
>
> ... and so on for 40 more web sites.
>
> I still want to be able to export this as HTML to document to others
> what i've done and use the org file to maintain the webpage and the
> source conf files.
>
> Same issue for documenting my configuration files for postfix, dovecot,
> drupal settings, php.ini settings.
>
> I'm sure this is easy, but searching the org manual or googling is not
> getting me the right answer.
>
> #+BEGIN_ASCII and #+BEGIN_EXAMPLE seem to be for exporting only and not
> tangling.
>
I don't know if this is the "right" way, but I just pretend my files are
shell scripts:
* Dovecot.
** dovecot.conf
#+BEGIN_SRC sh :tangle
~/dropbox/configuration_files/wilkesley.org/dovecot/dovecot.conf
:exports none :noweb yes
protocols = imap sieve
ssl = yes
ssl_cert = </etc/ssl/certs/mail2.wilkesley.net.crt
ssl_key = </etc/ssl/private/mail2.wilkesley.net.key
Ian.
next prev parent reply other threads:[~2012-01-27 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 18:07 Tangling text files dlc
2012-01-27 18:13 ` Ian Barton [this message]
2012-01-28 1:43 ` Eric Schulte
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=4F22E943.9040603@wilkesley.net \
--to=lists@wilkesley.net \
--cc=emacs-orgmode@gnu.org \
--cc=ian@manor-farm.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.
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).