1
0
forked from HPR/hpr-tools

Updates from previous repo

FAQ/FAQ.mkd, FAQ/Makefile: this version of the FAQ is now out of date
    and probably should be deleted.

InternetArchive/repair_item: script to upload missing shows after tie
    out errors during the normal upload; still under development.

InternetArchive/update_state: script to update show state in the
    'reservations' table in the database. Uses the CMS interface.

Link_Checker/scan_links: under development. Not currently usable.

Miscellaneous/fix_tags: audio metadata manipulation script. Recently
    added to this repo for convenience. Updates for 'experimental::try',
    the official Perl try/catch.

PostgreSQL_Database/add_hosts_to_show, PostgreSQL_Database/hpr_schema_2.pgsql,
    PostgreSQL_Database/nuke_n_pave.sh: an old experimental Pg database
    to take over from the previous MySQL version (from before 2023).
    Kept for reference; never implemented.
This commit is contained in:
Dave Morriss
2024-06-14 16:00:04 +01:00
parent 38abbcdd39
commit 50edeccc88
12 changed files with 1874 additions and 146 deletions

View File

@@ -1,66 +1,13 @@
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="generator" content="pandoc">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
<meta name="author" content="HPR Contributors">
<title>Hacker Public Radio FAQ (draft)</title>
<style type="text/css">code{white-space: pre;}</style>
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<link rel="stylesheet" href="http://hackerpublicradio.org/css/hpr.css">
</head>
<body id="home">
<div id="container" class="shadow">
<header>
<h1 class="title">Hacker Public Radio FAQ (draft)</h1>
<h2 class="subtitle">A collection of questions and answers with links to the HPR site</h2>
<h2 class="author">HPR Contributors</h2>
<hr/>
</header>
<main id="maincontent">
<article>
<header>
<h1>Table of Contents</h1>
<nav id="TOC">
<ul>
<li><a href="#hacker-public-radio-faq">Hacker Public Radio FAQ</a>
<ul>
<li><a href="#what-is-hacker-public-radio"><span class="toc-section-number">0.1</span> What is Hacker Public Radio?</a></li>
<li><a href="#what-is-a-show"><span class="toc-section-number">0.2</span> What is a show?</a></li>
<li><a href="#can-i-submit-a-show-made-for-another-podcast"><span class="toc-section-number">0.3</span> Can I submit a show made for another podcast?</a></li>
<li><a href="#what-defines-a-show-as-being-produced-for-hacker-public-radio"><span class="toc-section-number">0.4</span> What defines a show as being "<em>Produced for Hacker Public Radio</em>"?</a></li>
<li><a href="#what-are-the-mandatory-elements-of-an-hpr-show"><span class="toc-section-number">0.5</span> What are the mandatory elements of an HPR show?</a></li>
<li><a href="#is-it-ok-if-i-dont-include-notes-with-my-show"><span class="toc-section-number">0.6</span> Is it OK if I don't include notes with my show?</a></li>
<li><a href="#how-do-i-include-photographs-or-other-files-with-my-show"><span class="toc-section-number">0.7</span> How do I include photographs or other files with my show?</a></li>
<li><a href="#what-is-and-is-not-edited-in-a-show-after-submission"><span class="toc-section-number">0.8</span> What is and is not edited in a show after submission?</a></li>
<li><a href="#what-are-some-common-errors-in-show-notes"><span class="toc-section-number">0.9</span> What are some common errors in show notes?</a>
<ul>
<li><a href="#html-notes"><span class="toc-section-number">0.9.1</span> HTML notes</a></li>
<li><a href="#markdown-notes"><span class="toc-section-number">0.9.2</span> Markdown notes</a></li>
<li><a href="#general-errors"><span class="toc-section-number">0.9.3</span> General errors</a></li>
</ul></li>
<li><a href="#if-i-notice-an-error-in-my-shows-details-how-can-it-be-fixed"><span class="toc-section-number">0.10</span> If I notice an error in my show's details how can it be fixed?</a></li>
<li><a href="#does-hobbypublicradio.com-have-anything-to-do-with-hpr"><span class="toc-section-number">0.11</span> Does <code>hobbypublicradio.com</code> have anything to do with HPR?</a></li>
<li><a href="#how-can-i-talk-to-other-hpr-hosts-and-listeners"><span class="toc-section-number">0.12</span> How can I talk to other HPR hosts and listeners?</a></li>
</ul></li>
</ul>
</nav>
</header>
<h1 class="unnumbered" data-number="" id="hacker-public-radio-faq">Hacker Public Radio FAQ</h1>
<h1 class="unnumbered" data-number="" id="hacker-public-radio-faq-2021-04-01">Hacker Public Radio FAQ 2021-04-01</h1>
<h2 data-number="0.1" id="what-is-hacker-public-radio"><span class="header-section-number">0.1</span> What is Hacker Public Radio?</h2>
<ul>
<li><p>Hacker Public Radio (HPR) is an Internet Radio show (podcast) that releases shows every weekday Monday through Friday.</p></li>
<li><p>What differentiates HPR from other podcasts is that the shows are crowd sourced from the community — fellow listeners like you. There is no restriction on how long shows can be, nor on the topic you can cover as long as they are not spam and "are of interest to Hackers".</p>
<p>If you want to see what topics have been covered so far just have a look at our <a href="http://hackerpublicradio.org/index_full.php">Archive</a>. We also allow for a <a href="http://hackerpublicradio.org/series.php">series</a> of shows so that hosts can go into more detail on a topic.</p></li>
<li><p>Hacker Public Radio (HPR) is an Internet Radio show (podcast) that releases shows (episodes) every weekday Monday through Friday.</p></li>
<li><p>What differentiates HPR from other podcasts is that the shows are crowd sourced from the community — fellow listeners like you. There is no restriction on how long shows can be, nor on the topic you can cover, as long as they are not spam and "are of interest to Hackers".</p>
<p>If you want to see what topics have been covered so far just have a look at our <a href="http://hackerpublicradio.org/index_full.php">Archive</a>. We also allow for shows to be grouped into <a href="http://hackerpublicradio.org/series.php">series</a> so that hosts can go into more detail on a topic.</p></li>
<li><p>Look at the <a href="http://hackerpublicradio.org/about.php"><em>About HPR</em></a> page for a full description of <em>The HPR Community</em>, <em>Free Culture</em>, <em>Governance</em> and our <em>Patrons</em>.</p></li>
<li><p>A recent question on the mailing list asks if HPR is a Content Publication Network like YouTube, or is it a Podcast that random people contribute to? Or to put it another way, is the host addressing the Internet in general or the HPR Audience?</p>
<li><p>A question on the mailing list in 2020 asked if HPR is a Content Publication Network like YouTube, or is it a Podcast that random people contribute to? Or to put it another way, is the host addressing the Internet in general or the HPR Audience?</p>
<ul>
<li>The consensus of opinion is that HPR is a Podcast contributed to by the community.</li>
<li>The consensus of opinion is that HPR is a Podcast contributed to by the community, not a Content Publication Network.</li>
</ul></li>
</ul>
<h2 data-number="0.2" id="what-is-a-show"><span class="header-section-number">0.2</span> What is a show?</h2>
@@ -79,7 +26,7 @@
<li><p>Each show is expected to have certain mandatory attributes listed <a href="#what-are-the-mandatory-elements-of-an-hpr-show">below</a>.</p></li>
<li><p>HPR shows are usually expected to be informative or educational, and as such some sort of accompanying written material is highly desirable. This might consist of brief notes, links to relevant web sites, or possibly longer notes and examples. Photographs, diagrams and example files are also welcome if the host feels it helps to get the message across.</p></li>
<li><p>Shows are released under a <a href="">Creative Commons Attribution-ShareAlike 3.0 Unported</a> license. See <a href="http://hackerpublicradio.org/stuff_you_need_to_know.php"><em>Stuff you need to know</em></a> for much more detail about this and related issues.</p></li>
<li><p>As a contributor you can choose when your show will be released. We only release one show a day, during week days, but if a slot is free you can claim it. Go to the <a href="http://hackerpublicradio.org/calendar.php"><em>calendar</em></a> page to do this. You need to have your show ready to upload before you do this though.</p></li>
<li><p>As a contributor you can choose when your show will be released. We only release one show a day, during week days, but if a slot is free you can claim it. Go to the <a href="http://hackerpublicradio.org/calendar.php"><em>calendar</em></a> page to do this. You need to have your show ready to upload before you reserve a slot though.</p></li>
</ul>
<h2 data-number="0.3" id="can-i-submit-a-show-made-for-another-podcast"><span class="header-section-number">0.3</span> Can I submit a show made for another podcast?</h2>
<ul>
@@ -105,30 +52,37 @@
<li>Audio</li>
</ul></li>
</ul>
<h2 data-number="0.6" id="is-it-ok-if-i-dont-include-notes-with-my-show"><span class="header-section-number">0.6</span> Is it OK if I don't include notes with my show?</h2>
<h2 data-number="0.6" id="what-are-tags"><span class="header-section-number">0.6</span> What are tags?</h2>
<ul>
<li>No, please don't do that. It is important to provide good show notes for reasons described on the <a href="http://hackerpublicradio.org/request_a_slot.php"><em>Picking a slot for your show</em></a> page:
<li><p>We are trying to maintain a collection of tags to allow people to find shows on the same (or similar) topic.</p></li>
<li><p>Tags are simple words or short phrases describing aspects of a show such as what topics are covered in it. To get hints about what tags have already been used you can view all the current tags in alphabetical order on this page: <a href="http://hackerpublicradio.org/tags.php">Tag summary</a></p></li>
<li><p>Some examples are: <b>android</b>, <b>creative commons</b> and <b>gaming</b>.</p></li>
<li><p>Are there any tags that are best avoided?</p></li>
</ul>
<h2 data-number="0.7" id="is-it-ok-if-i-dont-include-notes-with-my-show"><span class="header-section-number">0.7</span> Is it OK if I don't include notes with my show?</h2>
<ul>
<li>They provide the listeners with more information on the topic</li>
<li>They ensure your show gets posted on time</li>
<li><strong>Please don't do that</strong>. It is important to provide good show notes for reasons described on the <a href="http://hackerpublicradio.org/request_a_slot.php"><em>Picking a slot for your show</em></a> page:
<ul>
<li>They provide the listeners with more information on the topic your show is covering</li>
<li>They ensure your show gets posted on time (the volunteers don't have to make notes for you)</li>
<li>They encourage people to download your show</li>
<li>They allow your show to be indexed by search engines</li>
<li>They make your show accessible to the deaf and hard of hearing</li>
</ul></li>
</ul>
<h2 data-number="0.7" id="how-do-i-include-photographs-or-other-files-with-my-show"><span class="header-section-number">0.7</span> How do I include photographs or other files with my show?</h2>
<h2 data-number="0.8" id="how-do-i-include-photographs-or-other-files-with-my-show"><span class="header-section-number">0.8</span> How do I include photographs or other files with my show?</h2>
<ul>
<li>TBA</li>
</ul>
<h2 data-number="0.8" id="what-is-and-is-not-edited-in-a-show-after-submission"><span class="header-section-number">0.8</span> What is and is not edited in a show after submission?</h2>
<h2 data-number="0.9" id="what-is-and-is-not-edited-in-a-show-after-submission"><span class="header-section-number">0.9</span> What is and is not edited in a show after submission?</h2>
<ul>
<li><p>We don't listen to the audio before posting a show to the website, so we don't change the content.</p></li>
<li><p>Unless you have done so and told us, we add an introduction to the audio announcing what it is. Similarly we add an <em>outro</em>. This is not <u>editing</u> since we don't change the content.</p></li>
<li><p>Unless you have done so and told us you have, we add an introduction to the audio announcing what it is. Similarly we add an <em>outro</em>. This is not <u>editing</u> since we don't change the content.</p></li>
<li><p>We may make changes to the show title, summary or tags. Usually these are minor changes such as spelling corrections. The intention is not any sort of censorship, merely to make these items more understandable or easier to index.</p></li>
<li><p>Depending on the form the show notes take we may modify these.</p>
<ul>
<li>If what is submitted is plain text we convert it to Markdown in order to generate HTML.</li>
<li>If the notes are one of the permitted markup formats (mostly Markdown) we may adjust this to ensure that valid HTML is generated.</li>
<li>If the notes are one of the permitted markup formats (mostly Markdown flavours) we may adjust this to ensure that valid HTML is generated.</li>
<li>If the notes are HTML we run them through an HTML checker and correct any mistakes it highlights.</li>
<li>We may correct spelling, grammar and punctuation if this clarifies anything which might otherwise be unclear.</li>
<li>If despite the request for show notes of some kind, none are provided, we may add notes which help to clarify the content of the show. This may be done after the show is released (when we have had a chance to listen to it).</li>
@@ -137,33 +91,33 @@
<li><p>We may make changes to a show's metadata if the host requests it (see the item on <a href="#if-i-notice-an-error-in-my-shows-details-how-can-it-be-fixed">fixing errors after upload</a>).</p></li>
<li><p>If a show contains links to resources which disappear after a period of time, we may at some future time change the notes to refer to any <em>Wayback Machine</em> copy that can be found.</p></li>
</ul>
<h2 data-number="0.9" id="what-are-some-common-errors-in-show-notes"><span class="header-section-number">0.9</span> What are some common errors in show notes?</h2>
<h2 data-number="0.10" id="what-are-some-common-errors-in-show-notes"><span class="header-section-number">0.10</span> What are some common errors in show notes?</h2>
<p>It depends on the note format to some extent:</p>
<h3 data-number="0.9.1" id="html-notes"><span class="header-section-number">0.9.1</span> HTML notes</h3>
<h3 data-number="0.10.1" id="html-notes"><span class="header-section-number">0.10.1</span> HTML notes</h3>
<ul>
<li><p>It's very easy to hand-write bad HTML. That's why we use an HTML checker on it, and fix the errors it reports.</p></li>
<li><p>A common fault is to write <code>&lt;code&gt;&lt;pre&gt;</code> to define a pre-formatted block of text using a fixed-width font. However it's illegal because the <code>&lt;pre&gt;</code> tag can't be enclosed in other tags like <code>&lt;code&gt;</code>. Use <code>&lt;pre&gt;&lt;code&gt;</code> instead.</p></li>
</ul>
<h3 data-number="0.9.2" id="markdown-notes"><span class="header-section-number">0.9.2</span> Markdown notes</h3>
<h3 data-number="0.10.2" id="markdown-notes"><span class="header-section-number">0.10.2</span> Markdown notes</h3>
<ul>
<li>This is quite a forgiving format. Some people embed HTML in the Markdown, and the HTML used suffers from some of the issues discussed in this document. These are <em>much</em> harder to spot. The HTML checker can't really help unless it's run on the output from Pandoc.</li>
</ul>
<h3 data-number="0.9.3" id="general-errors"><span class="header-section-number">0.9.3</span> General errors</h3>
<h3 data-number="0.10.3" id="general-errors"><span class="header-section-number">0.10.3</span> General errors</h3>
<ul>
<li><p>Spelling is often an issue in notes. As the notes are processed they are edited in the Vim editor with the spell check option turned on. In most cases spelling problems flagged by Vim are corrected.</p></li>
<li><p>Grammar and punctuation can also be issues. We do not have very effective grammar checking tools in the note preparation workflow. Modifications may be made to split up extra-long (often <em>comma-spliced</em>) sentences, rationalise the use of capital letters and similar.</p></li>
</ul>
<h2 data-number="0.10" id="if-i-notice-an-error-in-my-shows-details-how-can-it-be-fixed"><span class="header-section-number">0.10</span> If I notice an error in my show's details how can it be fixed?</h2>
<h2 data-number="0.11" id="if-i-notice-an-error-in-my-shows-details-how-can-it-be-fixed"><span class="header-section-number">0.11</span> If I notice an error in my show's details how can it be fixed?</h2>
<ul>
<li><p>The HPR administrators can make changes to show titles, summaries, notes and so forth. Ideally send an email to <code>admin</code> at <code>hackerpublicradio.org</code> explaining what the problem is and we'll fix it for you. We'll also ensure that the changes are propagated to the relevant page on archive.org.</p></li>
<li><p>Don't be tempted to send in your corrections as a comment. Comments are not propagated to archive.org, so people referring to that copy will not see the changes.</p></li>
</ul>
<h2 data-number="0.11" id="does-hobbypublicradio.com-have-anything-to-do-with-hpr"><span class="header-section-number">0.11</span> Does <code>hobbypublicradio.com</code> have anything to do with HPR?</h2>
<h2 data-number="0.12" id="does-hobbypublicradio.com-have-anything-to-do-with-hpr"><span class="header-section-number">0.12</span> Does <code>hobbypublicradio.com</code> have anything to do with HPR?</h2>
<ul>
<li><p>Some environments prevent access to sites which use the word <code>'hacker'</code> or <code>'hackers'</code> in their names (or content in extreme cases). The site names <code>hobbypublicradio.{com,net,org}</code> have been created, which link to the main HPR site, in order to get around this restriction.</p></li>
<li><p>See the mailing list thread here: <a href="http://hackerpublicradio.org/pipermail/hpr_hackerpublicradio.org/2015-February/013267.html" class="uri">http://hackerpublicradio.org/pipermail/hpr_hackerpublicradio.org/2015-February/013267.html</a></p></li>
</ul>
<h2 data-number="0.12" id="how-can-i-talk-to-other-hpr-hosts-and-listeners"><span class="header-section-number">0.12</span> How can I talk to other HPR hosts and listeners?</h2>
<h2 data-number="0.13" id="how-can-i-talk-to-other-hpr-hosts-and-listeners"><span class="header-section-number">0.13</span> How can I talk to other HPR hosts and listeners?</h2>
<ul>
<li>You have a number of choices:
<ul>
@@ -174,8 +128,3 @@
<li>An HPR tradition exists where we record a 26-hour show at the turn of the year celebrating the arrival of the New Year around the world. We use Mumble to record the show and anyone can connect to the Mumble server and speak to other HPR listeners and hosts. The recording is used to make multiple shows which are released when they are ready.</li>
</ul></li>
</ul>
</article>
</main>
</div>
</body>
</html>

View File

@@ -1,9 +1,11 @@
[%# FAQ.mkd 2020-09-26 14:26:49 version: 0.0.3 -%]
[%# FAQ.mkd <2021-04-01 15:17:14> version: 0.0.5 -%]
[% USE date -%]
---
title: Hacker Public Radio FAQ (draft)
title: Hacker Public Radio FAQ (draft) [% date.format(date.now,"%F") %]
subtitle: A collection of questions and answers with links to the HPR site
author: HPR Contributors
...
[%# {{{ Links %]
[% about = "http://hackerpublicradio.org/about.php" -%]
[% reqslot = "http://hackerpublicradio.org/request_a_slot.php" -%]
[% needtoknow = "http://hackerpublicradio.org/stuff_you_need_to_know.php" -%]
@@ -15,32 +17,34 @@ author: HPR Contributors
[% maillist = "http://hackerpublicradio.org/maillist" -%]
[% freenode = "http://webchat.freenode.net/?channels=oggcastplanet" -%]
[% podrec = "http://hackerpublicradio.org/series.php?id=75" -%]
[% tags = "http://hackerpublicradio.org/tags.php" -%]
[%# }}} %]
# Hacker Public Radio FAQ {.unnumbered}
# Hacker Public Radio FAQ [% date.format(date.now,"%F") %] {.unnumbered}
## What is Hacker Public Radio?
- Hacker Public Radio (HPR) is an Internet Radio show (podcast) that releases
shows every weekday Monday through Friday.
shows (episodes) every weekday Monday through Friday.
- What differentiates HPR from other podcasts is that the shows are crowd
sourced from the community &mdash; fellow listeners like you. There is no
restriction on how long shows can be, nor on the topic you can cover as long
restriction on how long shows can be, nor on the topic you can cover, as long
as they are not spam and "are of interest to Hackers".
If you want to see what topics have been covered so far just have a look at
our [Archive]([% index %]). We also allow for a [series]([% series %]) of
shows so that hosts can go into more detail on a topic.
our [Archive]([% index %]). We also allow for shows to be grouped into
[series]([% series %]) so that hosts can go into more detail on a topic.
- Look at the [*About HPR*]([% about %]) page for a full description of *The HPR
Community*, *Free Culture*, *Governance* and our *Patrons*.
- A recent question on the mailing list asks if HPR is a Content Publication
- A question on the mailing list in 2020 asked if HPR is a Content Publication
Network like YouTube, or is it a Podcast that random people contribute to? Or
to put it another way, is the host addressing the Internet in general or the
HPR Audience?
- The consensus of opinion is that HPR is a Podcast contributed to by the
community.
community, not a Content Publication Network.
## What is a show?
@@ -81,7 +85,7 @@ author: HPR Contributors
- As a contributor you can choose when your show will be released. We only
release one show a day, during week days, but if a slot is free you can claim it.
Go to the [*calendar*]([% calendar %]) page to do this. You need to have
your show ready to upload before you do this though.
your show ready to upload before you reserve a slot though.
## Can I submit a show made for another podcast?
@@ -115,13 +119,30 @@ author: HPR Contributors
- Tags
- Audio
## What are tags?
- We are trying to maintain a collection of tags to allow people to find shows
on the same (or similar) topic.
- Tags are simple words or short phrases describing aspects of a show such as
what topics are covered in it. To get hints about what tags have already
been used you can view all the current tags in alphabetical order on this
page: [Tag summary]([% tags %])
- Some examples are: <b>android</b>, <b>creative commons</b> and
<b>gaming</b>.
- Are there any tags that are best avoided?
## Is it OK if I don't include notes with my show?
- No, please don't do that. It is important to provide good show notes for
- **Please don't do that**. It is important to provide good show notes for
reasons described on the [*Picking a slot for your show*]([% reqslot %])
page:
- They provide the listeners with more information on the topic
- They ensure your show gets posted on time
- They provide the listeners with more information on the topic your show
is covering
- They ensure your show gets posted on time (the volunteers don't have to
make notes for you)
- They encourage people to download your show
- They allow your show to be indexed by search engines
- They make your show accessible to the deaf and hard of hearing
@@ -135,8 +156,8 @@ author: HPR Contributors
- We don't listen to the audio before posting a show to the website, so we
don't change the content.
- Unless you have done so and told us, we add an introduction to the audio
announcing what it is. Similarly we add an *outro*. This is not
- Unless you have done so and told us you have, we add an introduction to the
audio announcing what it is. Similarly we add an *outro*. This is not
<u>editing</u> since we don't change the content.
- We may make changes to the show title, summary or tags. Usually these are
@@ -147,8 +168,8 @@ author: HPR Contributors
- Depending on the form the show notes take we may modify these.
- If what is submitted is plain text we convert it to Markdown in order to
generate HTML.
- If the notes are one of the permitted markup formats (mostly Markdown)
we may adjust this to ensure that valid HTML is generated.
- If the notes are one of the permitted markup formats (mostly Markdown
flavours) we may adjust this to ensure that valid HTML is generated.
- If the notes are HTML we run them through an HTML checker and correct
any mistakes it highlights.
- We may correct spelling, grammar and punctuation if this clarifies

View File

@@ -1,31 +1,52 @@
# ==============================================================================
# FAQ Makefile 2021-01-30 11:00:47
# FAQ Makefile 2021-04-01 09:52:16
# ==============================================================================
#
# Simple Makefile to rebuild the components in this file
#
all : markdown
MDFILE = FAQ.mkd
HTMLFILE = FAQ.html
DEVFILE = FAQ_dev.html
TPLFILE = FAQ.tpl
PHPFILE = FAQ.php
all : markdown php
#
# Find all *.mkd files in the current directory and turn them into a list of
# *.html files as a rule target
# Rules for converting the Markdown into two files, one for stitching into
# the PHP framework via FAQ.tpl and the other just a stand-alone HTML file for
# development.
#
markdown: $(addsuffix .html,$(basename $(wildcard *.mkd)))
markdown: $(HTMLFILE) $(DEVFILE)
$(HTMLFILE): $(MDFILE)
tpage $< | pandoc -f markdown-smart -t html5 \
--number-sections --table-of-contents --toc-depth=4 -o $@
$(DEVFILE): $(MDFILE)
tpage $< | pandoc -f markdown-smart -t html5 --standalone \
--template=hpr.html5 -c http://hackerpublicradio.org/css/hpr.css \
--number-sections --table-of-contents --toc-depth=4 -o $@
#
# Rule to get from a Markdown (*.mkd) file to an HTML equivalent allowing for
# Template Toolkit stuff within the file
# When we generate the file FAQ.html (HTML fragment) we use tpage to make
# a complete standalone PHP page called FAQ.php
#
%.html: %.mkd; tpage $< | pandoc -f markdown-smart -t html5 --standalone \
--template=hpr.html5 -c http://hackerpublicradio.org/css/hpr.css \
--number-sections --table-of-contents --toc-depth=4 -o $@
.PHONY: php upload
php: $(PHPFILE)
$(PHPFILE): $(HTMLFILE)
tpage $(TPLFILE) > $(PHPFILE)
#
# Upload the FAQ HTML to the server for development
# Upload the FAQ HTML+PHP to the server for development
#
upload:
scp -P 22074 FAQ.html hpr@hackerpublicradio.org:www/
upload: $(PHPFILE)
scp -P 22074 $(PHPFILE) hpr@hackerpublicradio.org:www/
# ==============================================================================
#
# Use 'make sync' to copy updates to the visible project area
#
@@ -35,7 +56,7 @@ upload:
sync: put
fromdir = $(HOME)/HPR/FAQ/
todir = $(HOME)/HPR/Projects/hpr-admin/FAQ/
todir = $(HOME)/HPR/Projects/hpr-tools/FAQ/
filter = $(fromdir).rsync_export
syncmsg = Updating git directory with updates from development version
@@ -44,5 +65,5 @@ put:
@echo "** $(syncmsg)"
rsync -vaP --filter=". $(filter)" $(fromdir) $(todir)
.PHONY: upload sync put
.PHONY: sync put