I'm be using DreamCompute as my OpenStack provider, but there are dozens to choose from. I assume you already have Ansible and the OpenStack CLI tools installed.
With the proliferation of OpenStack public clouds offering free and intro tiers, it's becoming very easy to effectively run a simple application for free or nearly free. Also with the emergence of Ansible, you don't need to learn and deploy complicated tools to do configuration management.
This is a simple snippet for adding a loading screen to a Polymer application. It is useful if your Polymer application is rather large and some users may be on a very slow internet connection.
The basic idea is that a very simple (and small) loading screen page will be loaded by the browser. When the browser has fully loaded and displayed the loading page then it will start loading all the files required for the Polymer application.
For a further speed improvement: the loading.css, and polymerAppLoader.js files can be placed inline with the index.html thus reducing the amount of files to be loaded from the server.
filestoload.html is a seperate file so that the usual grunt/gulp build functions can still be applied as before. Shouldn't require re-writting your build scripts.
Any improvements/comments are encouraged.
| # In config/application.rb | |
| config.watchable_dirs['lib'] = [:rb] | |
| # When requiring something, use require_dependency | |
| # To use lib/myclass.rb | |
| require_dependency 'myclass' |
| module Paperclip | |
| # A wrapper for a queued item. Normally this would be a temporary file, but we can't do that, because Paperclip | |
| # would copy the temporary file before the content is actually written. | |
| class BulkQueueItem | |
| attr_reader :destination | |
| def initialize(destination) | |
| @destination = destination | |
| end | |
| end |
| description "Properly handle haproxy" | |
| start on startup | |
| env PID_PATH=/var/run/haproxy.pid | |
| env BIN_PATH=/usr/sbin/haproxy | |
| script | |
| exec /bin/bash <<EOF | |
| $BIN_PATH -f /etc/haproxy.cfg -D -p $PID_PATH |
| # Hack to implement per-directory history. If you run the same commands in the same directories, | |
| # then why not have a separate history for each directory? | |
| HISTBASE=~/.bash_directory_hist | |
| LASTHIST= | |
| _hash() { | |
| echo "$@" | sha512sum | cut -f1 -d' ' | |
| } |
A lot of important government documents are created and saved in Microsoft Word (*.docx). But Microsoft Word is a proprietary format, and it's not really useful for presenting documents on the web. So, I wanted to find a way to convert a .docx file into markdown.
As it turns out, there are several open-source tools that allow for conversion between file types. Pandoc is one of them, and it's powerful. In fact, pandoc's website says "If you need to convert files from one markup format into another, pandoc is your swiss-army knife." But, although pandoc can convert from markdown into .docx, it doesn't work in the other direction.
| inputs = %w[ | |
| CollectionSelectInput | |
| DateTimeInput | |
| FileInput | |
| GroupedCollectionSelectInput | |
| NumericInput | |
| PasswordInput | |
| RangeInput | |
| StringInput | |
| TextInput |
| ## The MIT License (MIT) | |
| ## --------------------- | |
| ## | |
| ## Copyright (C) 2014 Nicco Kunzmann | |
| ## | |
| ## https://gist.github.com/niccokunzmann/6038331 | |
| ## | |
| ## Permission is hereby granted, free of charge, to any person obtaining | |
| ## a copy of this software and associated documentation files (the "Software"), |
