Gist simplicity can turn blogging into a liberating experience.
Pros | Cons |
---|---|
✅ Free, simple, fast, hassle-free | ❌ Image upload in comments only |
✅ Tagging | ❌ No post pinning |
✅ Search | ❌ Doesn't look like a blog |
✅ Revisions | ❌ Unfriendly URLs |
FROM ruby:2.4-alpine3.7 | |
# Install dependencies: | |
# - build-base: To ensure certain gems can be compiled | |
# - nodejs: Compile assets | |
# - postgresql-dev postgresql-client: Communicate with postgres through the postgres gem | |
# - libxslt-dev libxml2-dev: Nokogiri native dependencies | |
# - imagemagick: for image processing | |
RUN apk --update add build-base nodejs tzdata postgresql-dev postgresql-client libxslt-dev libxml2-dev imagemagick |
Opened mongoose connection | |
Successfully created and inserted new records | |
--------- | |
Black 2016 BMW 135is | |
Silver 2016 BMW 335is | |
Red 2016 BMW 535is | |
Alpine White 2016 BMW M6 | |
--------- | |
UPDATED: | |
Japan Red 2016 BMW M6 |
# gem 'rails' | |
gem "activerecord" | |
gem "actionpack" | |
gem "actionview" | |
gem "actionmailer" | |
gem "activejob" | |
gem "activesupport" | |
gem "railties" | |
gem "sprockets-rails" | |
gem 'sqlite3' |
Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.
By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.
<?php | |
namespace App\Console\Commands; | |
use Illuminate\Console\Command; | |
/** | |
* Class SeedResource | |
* @package App\Console\Commands\Resource | |
*/ |
/home/dan/Apps/vsc
in the code.desktop file to the location you extracted the application to.This how only been tested by myself on ElementaryOS Freya.
var gulp = require('gulp'); | |
var browserify = require('browserify'); | |
var babelify = require('babelify'); | |
var source = require('vinyl-source-stream'); | |
gulp.task('browserify', function() { | |
return browserify('./js/app.js') | |
.transform(babelify, { stage: 0 }) | |
.bundle() | |
.on('error', function(e){ |