jasonbrooks

<?php
// Turn on all error reporting so we can see if anything goes wrong
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(-1);

// Relative path to your wp-config.php file (to connect to the database)
require '../../wp-config.php';
require './frontmatter.php'; // Parses YAML frontmatter - https://github.com/Modularr/YAML-FrontMatter
require './Parsedown.php'; // Markdown parser - https://github.com/erusev/parsedown

jasonbrooks

.NET
ActionScript
ActiveMQ
Ada
Agile
Akka
Android
Ansible
AngularJS/js[Angular]
Apache

jasonbrooks

Atomic Host Definition [Discussion Draft]

This document is meant to serve as a baseline definition for Project Atomic hosts, to be implemented from CentOS, Fedora, and Red Hat Enterprise Linux (RHEL).

The purpose of the document is not to restrict the packages or services offered with an Atomic host, but to ensure a baseline of functionality and working standard that each product team can implement before adding additional functionality.

The initial working draft is being taken from work going into RHEL Atomic, but it is expected that the CentOS Atomic SIG and Fedora Cloud Workgroup will provide input and direction to Project Atomic going forward. This is simply the first cut at a shared understanding that gives each team a basis for cooperation.

Atomic Host Definition

jasonbrooks

1. git clone git://github.com/getpelican/pelican.git

2. cd pelican

3. python setup.py install

4. pelican-import --wpfile -o ~/$output-location ~/Downloads/$wp-xml-file

5. cd ~/$output-location

6. for i in *.rst; do pandoc $i --no-wrap -f rst -t asciidoc post-content.html -o $i.adoc

7. rename .rst.adoc .adoc *.rst.adoc

8. use sed to cleanup [haven’t tested these sed bits myself yet]