Ann.Dev

In this first post of my new Local Dev Craft series, we will be setting up a local Kubernetes cluster using kind, KEDA, and LocalStack AWS in order to build a development/debugging environment that is similar to production. But first, let’s get familiar with the tools we are going to use here:

• Kubernetes: An open-source platform designed to automate deploying, scaling, and operating application containers.
• kind (Kubernetes in Docker): A tool for running local Kubernetes clusters using Docker container “nodes”.
• KEDA (Kubernetes Event-Driven Autoscaling): A set of components that extends Kubernetes to provide event-driven autoscaling for every container.
• LocalStack AWS: A fully functional local AWS cloud stack for testing and mocking AWS services locally.

Now that we know what we’re dealing with, let’s move on and create our local development environment that mimics our cloud setup. This setup will be a set of stateless jobs that will be spawned by KEDA events, exit after execution, and scale to zero.

This is part 3 of EOS quick-start. Please makesure you have completed [Part 2] Install from sources and have all requirements installed.

Before we begin

First things first: By voting you are accepting the EOS Constitution. Make sure you have read it!

As we already stated in [Part 1] Introduction, EOS is in many ways a social experiment in governance. One of the aspects of this is voting for block producers and you vote matters. There are currently few ways to vote for EOS block producers currently available:

This is part 4 of EOS quick-start. Please makesure you have completed [ Part 2 ] Install from sources and have all requirements installed.

Also refer to [ Part 1 ] Introduction for basic information on EOS.IO

Run EOS.IO Local Testnet

after the build successfully finished, you need to run

nodeos --config-dir ./config --data-dir ./data

this will generate data and config folder with default config.ini  file in you working folder, then stop it with Ctrl + C.

This is part 2 of EOS quick-start. Please refer to [ Part 1 ] Introduction for basic information on EOS.IO

Installation and configuration

In EOS.IO there are three main progreams that weare going to use througout this tutorials:

• nodeos is n EOS node daemon
• keosd is a wallet keys daemon
• cleos is a cli - command line interface tool

Option 1. Run Docker image

This is the simplest and easiest way. Just run the following command to get into EOS enabled shell:

docker run -it eosio/eos:latest /bin/bash

Option 2. Build using build script

So according to the README on https://github.com/EOSIO/eos, all I need to do to run local testnet is:

What the heck is EOS, and why should I care?

According to EOS.IO: EOS is a software that introduces a blockchain architecture designed to enable vertical and horizontal scaling of decentralized applications.

But what does it mean?..

This is a post that shows how to install and configure serverless framework for google cloud platform.

What do you mean serverless?..

For those of you who don’t know, serverless architecture is an architecture in which you get a dynamic allocation of machine resources and charged for the actual amount of resources consumed by an application, rather than on pre-purchased units of capacity.

The problem:

A week ago, after some update(not really sure which one), I faced a very frustrating issue: I could not start my android emulator(AVD) anymore. It failed with a not very informative error:

UPDATE October 2017: As of today, OpenShift 2 is officially reached its end of life and is shut down rendering this guide irrelevant. I will keep it here for historical purposes.

Please note that this guide was for version 2 of OpenShift cloud platform. parse-server-example supports OpenShift 3 platform out of the box, so there is no need for any external guide.

TL;DR just take me to the instructions

Few months ago I was consulting a start-up called AbiliSense on their cloud solution. They build this amazing mobile app for people with hearing disabilities. After understanding their service needs we decided to go with Parse BaaS solution, and it was all good until the dramatic Parse Announcement  about the retirement of their services. So there was a bit of frustration.. But then we realized that parse-server

Few days ago my Debian jessie package update(e.g. apt-get upgrade) start failing with following message:

Sometimes you need to install the latest and greatest kernel image on you Debian testing installation. In most cases that is to support some newer hardware piece, or to get latest features. You have two choices here: You can either compile it from sources, or you can just take it from the Debian experimental repository. There are plenty guides online on how to build you kernel from sources, so we won’t go into it.