I used LAMP to make a SaaS with $3700/mo profit

Here I’m going to share my experience on creating a SaaS webservice with a simple LAMP stack and making it earn $3700 per month (actually it made around $7000 before the Russian currency had tanked). Again, this story has nothing to do with investors, the Silicon Valley gold rush, and über modern technology. Just a simple story from an indie developer about making a profitable SaaS anyone could make. This webservice has been made for the Russian domestic market, so I’ve translated everything into English and USD for convenience. Otherwise, this experience is pretty general and could be adopted anywhere. It’s a blueprint, actually.Three years ago I decided to tap into social media marketing and the easiest way to do that seemed to start my own group in some niche and to try to grow it. Facebook had already been a bit competitive at the moment, to say the least,


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/CVFl79jqWAg/i-used-lamp-to-make-a-saas-with-3700-mo-profit-heres-how-1c47033900e9

Original article

Understanding the ethereum trie

The other day I finally got around to reading the entire ethereum yellow paper and to figuring out how the modified Merkle-patricia-tree (trie) works. So let’s go through a brief but hopefully complete explanation of the trie, using examples.
A block in the ethereum blockchain consists of a header, a list of transactions, and a list of uncle blocks. Included in the header is a transaction root hash, which is used to validate the list of transactions. While transactions are sent over the wire from peer to peer as a simple list, they must be assembled into a special data structure called a trie to compute the root hash. Note that this data structure is not needed except to verify blocks (and hence of course to mine them), and can technically be discarded once a block has been verified. However, it is implied that the transaction lists are stored locally in


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/CSFn1_Q-Xmw/

Original article

Minikube workflows

Minikube is a terrific tool for running a Kubernetes cluster on your local computer. It launches a single-node cluster in a virtual machine which is great for running Kubernetes locally. This post describes how to iterate fast when developing in a local Kubernetes cluster by avoiding unnecessary pushes/pulls of docker images, and shows how to mount folders from a local drive into a cluster.

The workflows are presented for MacOS using VirtualBox. Since the documentation on minikube’s official Github repository is very good, and a lot of great posts about minikube exists, this post will serve as a supplement and show how minikube’s building blocks can be combined.

Prerequisites

You will need the requirements listed below.

Starting minikube

A single command is enough to start a single-node Kubernetes cluster.

$ minikube start

A virtual machine (boot2docker) is created using the default VirtualBox VM-driver with 2 GB RAM and 2 CPUs assigned. Several custom flags are available


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/ZwvCKEcgN2Q/

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: