• Exploring Google Cloud Functions

    Location visible to members

  • Kubernetes and Docker and Microservices

    Location visible to members

    Docker has become increasingly useful as a development and deployment platform. Separating out the problems of installed dependencies from delivering applications from volumes from interconnections is a complex task. This Code Lounge looks at Kubernetes and how it solves those problems. I have rejected Docker Swarm as too incomplete and Apache Mesos as too complex - but if you are interested in deploying your application stack in Docker, you may be interested in coming along. You will need to have Vagrant installed on your machine - and it will need to be Linux or MacOSX (Windows users will need to run an additional VM to use the kube command line). We will be tying everyones machines into a single cluster of nodes and then partitioning it up to allow different applications to be run. Further instructions will be forthcoming and there is a codelounge Slack channel you can ask questions on. You can bring your own example microservice if you like, but I will have a selected sample of docker images (and will make a local docker repo available so speed up deploy).

    16
  • Electronics Open Day

    Location visible to members

    4
  • Electronics Open Day

    Location visible to members

    This has MOVED from Sunday. I will be around, in case anyone else wants to turn up. This is an electronics open day for people who want to build something with a group of others who also want to build something. We have spare ESP8266 and Arduino devices for people to play with if desired and should have plenty of cables, bread boards and extra bits and bobs as necessary. The Shopbot Desktop CNC is all up and firing so I'm happy to show people how that device works in case future projects require it. Presumably the 3d printers also work, but the laser does not and will probably be my project for the day.

    1
  • ESP8266 and the Internet of Things

    Location visible to members

    The ESP8266 was one of the more exciting chips to be hit mainstream in the last year. A full wi-fi stack chip between $US2-$US4 that you could reload with Python, LUA and later the Arduino stack, with many accessible pins, running at 3.3v was a lot of people's nirvana. The chipset isn't perfect, the lower power modes aren't as low power as the MSP430s, the support infrastructure isn't as wide as Arduino, but there are many things to enjoy about this tiny device. Each participant will receive an FTDI serial programmer and ESP8266 loaded with NodeMCU and LUA. A light detecting resistor will be provided for those who don't bring along their own kit - and if you have some interesting stuff, please feel free to bring different kinds of sensors along. If you end up wanting to take the provided parts home, I can arrange to part with them, they will probably amount to about $10. The aim is to start by learning a bit of LUA, seeing what can be done with the language, talk to an MQTT server (Mosquitto), having notifications pop up on your phone, and if we get a bit more tricky, host a web server and interact with the device to do simple things. Please note, this is the existing ESP device, the new one with an included bluetooth stack and dual-core is not out yet.

    18
  • Scripting your server install with Ansible

    Location visible to members

    For various reasons at work we are using Ansible, and given I detest Puppet, it seems like a good reason to learn a bit of Ansible. Ansible differs primarily in that it has no agents and seems designed to bring new images up to a well known state along with redeploying your code. If you run a server on Amazon or GCE (or both, or somewhere else) and want to make sure you have the steps necessary to provision it down pat so you can update and upgrade base OSs and create local copies, you may find this interesting. I'm finding my feet with it, but anyone is welcome who is interested.

    11
  • Towards Angular 2.0: Directive only development in Angular 1.4

    Location visible to members

    This is a focused session on detailing how to build Directive only applications with Angular 1, talking about mechanisms around avoiding the use of $scope and new techniques introduced in Angular 1.4 to write more migratable code.

    3
  • Using OAuth Services

    RIchard's New Place

    OAuth2 clients - it can be letting someone else manage identity, it can be just getting access to services. In this session we will look at OAuth2 actually works in its browser only and server side flow. Then we will implement a basic client side Web OAuth2 - from a pure Javascript service, from a server side OAuth2 (we will do ours on the JVM, but if there are node/rails/python people exploring other technologies (except PHP) are welcome). We have two existing projects we will be dissecting - one that uses Google for its identity (having no other logic mechanism) and the issues around that (including offline access, storing credentials, updating credentials, etc) and another that is designed to allow you access to the APIs for your own "stuff". Afterwards, weather permitting, there will be an end of year Code Lounge BBQ - Texan style ribs and sausages will be provided, if you want anything else, please bring it!

    11
  • Distributed Configuration Management using etcd

    Location visible to members

    Managing the configuration of server side applications as they make their way through multiple environments with multiple instances, elements of configuration that need to be secure or not, with the ability to see and understand what configuration a server is actually using at any particular time and manage that can be hard. Some go for the easy route - just a text or xml file, some opt for a full revision control history solution which can have its own downsides. The big companies use ZooKeeper (Yahoo, Youtube, etc) or something else. But what about the NKOTB? etcd aims at solving the same problems, has a fairly simple API and is written in Go, so its deployment infrastructure is also fairly straightforward. This session looks at distributed configuration management using etcd - how you populate it, how you watch it for changes, what you could and should do when it does change, atomicity of changes, implications of distributed configuration, sharing configuration so different environments see different config, sources of config, access control around populating configuration and other such topics. The session needs you to have either a Mac or a Linux machine, or a VM that runs Linux or Docker. Please ensure you are using the 0.4.x latest version (0.4.6 at time to writing) and bring along a language that can do network stuff. That could be Javascript in your browser. Session is limited to 10, some of the participants have an agenda. End time is approximate.

    3