noteed

Business and customers values

The different ways a service price can be structured will put pressure on the business owner to develop and improve that service in different directions. It will also put pressure on the customers to use the service in different ways. In some case the pressure is even such that the business will try to degrade the service, instead of improving it. For Reesd, I want to make a conscious choice where the created pressure both naturally pushes me to improve the service, and pushes the customers to make the right technical decisions.

noteed

Self

You want to make money with a SaaS business. But you need an idea. Well, you don't.

You want to make a lot of money, so you'd better prepare for it. For instance, be ready to accept payments, and store and deliver invoices. But you want to really make a lot of money, right ? So you develop a scalable application to deal with that load of payments and invoices. And since a lot of other businesses have the same needs, you offer your application with a subscription model.

You now have a SaaS and you can continue to offer services that you need yourself. Accepting payments and invoicing was just the beginning. You need backups, so you offer a backup service. You need monitoring, and a status page. You need to send email, you need to deploy updates, you need to host your source code, ... you have a lot of needs, so you can offer a lot.

To start, you identify one of those needs, and you offer a solution, to yourself and also to others.

noteed

-- | Horde data types. These data types are serializable using the `safecopy`
-- package. Serialization/deserialization should be done with the `safeEncode`
-- and `safeDecode` functions.
--
-- Using `safecopy`, we can change these data types and migrate already
-- serialized data structures. To do so, we change the
-- `deriveSafeCopy 1 'extension` (and
-- `deriveSafeCopy 0 'base`) to `deriveSafeCopy 2 'extension` (and to
-- `deriveSafeCopy 1 'extension`) and provide migrations.
--

noteed

Reesd Images

Reesd Images is a hosted private Docker registry. It is currently in alpha.

Getting started

Reesd Images is running at images.reesd.com and can used with the docker executable.

The first time you upload an image, you will be prompted for a username, a password, and an email address. You can also log into the registry prior to upload with docker login.

noteed

Running Docker on two hosts, bridged with Tinc

This Gist is similar to https://gist.github.com/noteed/8656989 which uses Open vSwitch instead of Tinc.

Setup

Download the install.sh script and run it:

> https://gist.githubusercontent.com/noteed/11031504/raw/install.sh

noteed

"""
Simple workflow engine.

A workflow is a directed graph where nodes are activities. The returned
value of an activity is used to dispatch on its outgoing transitions.

Activities are functions, accepting a `state` argument.

    def ACTIVITY(state):
        pass

noteed

How I use Docker for Reesd

Docker is all the rage these days. I started to look at Docker seriously maybe around April last year. It has gained a lot of momentum and I think it's just the beginning. For instance new tools and services are created regularly, or Docker, inc. has not yet unveiled their exact commercial offering (and I think they have a very rich view about what it is possible to achieve with Docker).

When I started to build Reesd, I have directly used Docker. Even if it is not production-ready, or even if there is some risk that it might evolve

noteed

Running Docker on two hosts, bridged with Open vSwitch

This Gist shows how to use Open vSwitch to bridge Docker containers on two hosts. It is based on this blog post http://goldmann.pl/blog/2014/01/21/connecting-docker-containers-on-multiple-hosts/.

A similar Gist using Tinc instead of Open vSwitch is available: https://gist.github.com/noteed/11031504.

Setup

noteed

Introducing the rees command-line tool

I have been interested in creating a simple service to backup files. At first, the service was mainly intended to save PostgreSQL WAL segment files and I thought to simply use the scp command to upload the files to a remote machine. Then putting some more thoughts in it, it felt like a nice well-defined project and possibly like a minimum viable product.

More precisely I decided to expose a service, [email protected] (think about the similarity with [email protected] or [email protected] when using the SSH transport) that would allow users to use the regular scp command to save and restore files. When scp would complete an upload to Reesd, it would mean that Reesd has actually streamed the content to multiple backend machines.

Although useable, Reesd is not yet ready for commercial use. I have still some tools to write to automate its deployment and more importantly, make sure I can restore data quickly in the event a replica fails. That being said, I have be

noteed

from ubuntu:12.04
maintainer Vo Minh Thu <[email protected]>

run echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list
run apt-get update

# Install PostgreSQL (for the postgres user)
run apt-get install -q -y postgresql-9.1

# Install OpenSSH (for scp)