bmann

; Basic Drush Make file
; See the Drush Make prject page for info:
;	http://drupal.org/project/drush_make
; This file originally by Brock Boland [brock@brockboland.com]
; Modified by Boris Mann [http://bmannconsulting.com/contact]

; Core version
; ------------
; Each makefile should begin by declaring the core version of Drupal that all
; projects should be compatible with.

bmann

<?php
// $Id: blogapi.module,v 1.115.2.5 2008/10/08 20:12:17 goba Exp $

/**
 * @file
 * Enable users to post using applications that support XML-RPC blog APIs.
 */

/**
 * Implementation of hook_help().

bmann

; from http://www.lullabot.com/articles/wysiwyg-feature
; DRUPAL VERSION
core = 6.x

; CORE MODULES
projects[] = drupal
projects[views][subdir] = "contrib"

; FILE HANDLING
projects[imagecache][subdir] = "contrib"

bmann

<?php

function acquiaslim_profile_modules() {
  $modules = array(
    // Default Drupal modules.
    'color', 'comment', 'help', 'menu', 'taxonomy', 'dblog',
    // More core
    'path',
    // Contributed modules
    'admin_menu', 'backup_migrate', 'backup_migrate_files', 'token', 'pathauto'

bmann

; from the auto-generated make from drupal.org
projects[diff] = 2.0
projects[freelinking] = 1.10
projects[token] = 1.13
projects[talk] = 1.6
projects[pathauto] = 1.3
projects[wikitools] = 1.2
projects[flexifilter] = 1.2
projects[admin_menu] = 1.5
projects[extlink] = 1.11

bmann

Installation profiles are a combination of core Drupal plus additional contributed modules, themes, and configuration combined into one download. Profiles are like pre-fabricated Drupal sites, built with a specific configuration out of the box. These sites aim to provide features and functions for specific purposes or types of sites without having to combine and configure everything from scratch.

For example, an installation profile for conferences might automatically install and configure modules for advanced user registration & profiles, ticketing, and a list of speakers and sessions.

If there is an installation profile that fits your needs, they can be a great starting point. Once you have installed it, you can still configure and customize your Drupal site as usual.

bmann

#!/usr/bin/env ruby

# Script to import tumblr posts into local markdown posts ready to be consumed by Jekyll.
# Inspired by New Bamboo's post http://blog.new-bamboo.co.uk/2009/2/20/migrating-from-mephisto-to-jekyll
# Supports post types: regular, quote, link, photo, video and audio
# Saves local copies of images
# via gist at https://gist.github.com/867468

require 'rubygems'
require 'open-uri'

bmann

require 'rubygems'
require 'sequel'
require 'fileutils'
require 'yaml'

# NOTE: This converter requires Sequel and the MySQL gems.
# The MySQL gem can be difficult to install on OS X. Once you have MySQL
# installed, running the following commands should work:
# $ sudo gem install sequel
# $ sudo gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config

bmann

My bias is towards PaaS compatible implementations (i.e. no full LAMP server required). Russell Beattie has the definitive and updated list of all readers right now: http://www.russellbeattie.com/blog/readerpocalypse-the-players

• Stringer - Ruby-based reader - Sinatra, PostgreSQL, designed to run on Heroku
• Leselys - Python / Mongo / Redis, designed to run on Heroku
• CommaFeed - Java + AngularJS + MySQL, runs on OpenShift
• BirdReader - the only Node-based feed reader I could find. Uses CouchDB / Cloudant as the DB, no instructions for PaaS hosting

bmann

<%
  if (public.images[current.source]) { %>
    <div id="slider" class="swipe">
      <div class="swipe-wrap"> <%
		    for (image in public.images[current.source].contents) { %>
		       <div><img src="/images/<%= current.source %>/<%= public.images[current.source].contents[image] %>" class="image image-full" /></div>
		    <% } %>
      </div>
    </div>
<% } %>