deforciant

I didn't find it hard to set up, it's just once CLI that also has "flutter doctor" command that tells you if something is wrong. Since I already had XCode (as I was doing some work on Swift) and Android Studio, I didn't find it even a little bit annoying :)

What really made the difference for me was their CLI to build and run the app + batteries included approach where the router is available out of the box and you don't need to look through some GitHub projects on how to implement routing and authentication in your app. That wasn't the case with RN.

Also, in this setup, all the infrastructure is in your computer, no need for a cloud service like Expo. However, I do agree with you that if you just want to try something simple, it will be easier with it, it's just how much can you trust that service and why would you for something more serious?

I tried to like TypeScript a bit more than a year ago but couldn't, maybe I should give it another chance. I mostly do my frontend development in Vue.js so even though it supports TypeScript, I never found any need for it (I use typed Props to pass data between the components) as I try to make my UI as thin as possible, just fetching some data from the backend and displaying it. You can have a look at my project- https://webhookrelay.com (management UI is under my.webhookrelay.com), so far made it quite simple, material UI and only a little bit of JS.

Obviously coming from Go to frontend I think I would benefit a lot from TypeScript.. Maybe one day :)

I prefer something that you can build yourself so expo wasn't an option for me. Plus, I think most of the platforms one day (might be soon) will ban these services as they can deliver code to the app after it has been approved.

With Flutter it's super easy, they have a CLI that creates an initial boilerplate for your code that you can compile and deploy to your phone in just a single command with hot reload enabled. I guess it makes it easier even than expo as you don't have to scan anything on your phone :)

I mostly spend my days writing Go (previously Python) and when I tried Dart I really liked it. Could basically start coding and be productive without even looking at language documentation (VSCode has a nice Dart plugin which tells you what to do and what not to do).

In my case, I was trying out Dart because of a Flutter (probably majority of people are now looking at Dart because of Flutter) and I found it really fantastic. I love the tooling where you can just use their CLI to build/test the application without complex IDEs like XCode or Android Studio.

If you want to try building a mobile app then definitely go for Flutter+Dart, even if you don't need to support both Android and iOS I think it's just much more easy to start with than alternatives (RN/Swift/Android Java).

So the war for enterprise on-prem Kubernetes just intensified :) RedHat vs Google? :] I wonder how is Rancher doing? I guess life will be harder too?

Timing seems to be important, just before OpenShift finishes absorbing Tectonic (or maybe Tectonic is absorbing OpenShift) with their installer, UI and billing services. I guess there's still time for Google to land some big deals :)

I have been using this for several years now. Great stuff! :) The only part that was missing from this was something that can update your deployments on image build. That's when I built Keel https://github.com/keel-hq/keel.

Basically, I have one trigger to always build from master but the rest are triggered by tag, for example, "1.2.5" and it builds the same image, then Keel updates affected workloads. So far I have never had to pay for it, apparently managing to stay in the free tier :)

Works way faster than automated Docker cloud builds either.

Moved to London, started several side projects, joined a startup that was actually paying very well and was doing an interesting technology.

What would I change? Probably nothing, but I would want to change what I was doing at ~21, where computer games were dominating my spare time, I wish I started working on side projects early on. Nowadays I find building things more rewarding.

Hi guys, this weekend I had to connect and check some data in my running Redis instance which was deployed in GKE. With pretty much no effort I deployed Redis Commander and decided to write a blog post about it. Hopefully, it will be helpful if you find yourself in a similar situation.

I have recently built a machine with Ryzen 2700X & geforce gtx 1050ti (GPU is required as Ryzen doesn't have an internal one but there are plenty of cheaper ones like mine), running Ubuntu and it's just fantastic. Docker builds, compilation takes seconds as compared to my macbook which has i7. Plus there's no overheating issues when I am running Kubernetes all the time and I can still code.

TL;DR Ryzen 2700X is great value for money, would recommend it any day :)

I use Go, Vue.js, Postgres, NATS, Redis, Keel, and deploy everything Kubernetes.

So far I am super happy with the stack, runs cheaply and requires pretty much no maintenance. Just tag a release on GitHub, Google Cloud Builder builds the image, Keel updates deployments and in a few seconds I have updated production with zero downtime.

While some people are happy with their copy/paste binaries/code to remote servers, I think a good pipeline to release and run your workloads makes working on side projects a lot more pleasure where you can focus on code and features. It also provides you with a valuable experience that can make you more money than the side project itself :)

Hi there!

Since there are plenty of articles on how to consume webhooks, I thought it would make sense to write one on how to start producing webhooks as it seems like the best way to illustrate the difference :)

Did you encounter any problems with NBD caching when it acknowledges the write to the application but doesn't pass it to your "backend" therefore leaving no room for error handling if that backend goes away?

Hey, I found this tool very useful https://mholt.github.io/json-to-go/ when working with large JSON structs :)

Hi, if you would want Keel to support Docker Swarm, please create an issue here: https://github.com/keel-hq/keel/issues.

I planned to add Docker Swarm support from the beginning but a lot of people said that it's unnecessary. It's quite simple to add new providers, they need to implement this interface:

  // Provider - generic provider interface
  type Provider interface {
 	Submit(event types.Event) error  // <- this is where new image event comes in
	TrackedImages() ([]*types.TrackedImage, error) // <- provider needs to tell some triggers which images to track (registry watcher)
	GetName() string
	Stop()
  }

Even though Keel was created for Kubernetes, later on Helm was added where Keel talks directly to Tiller and doesn't really use K8s API.

Thanks for the shout-out! Keel author here. I have created Keel exactly for these workflows where something (Travis CI, Docker cloud, Google Cloud Builder - my favourite due to the pricing and proper speed) builds an image and then we would want to trigger a deployment update.

I was running workloads on GKE and I found that while it's easy to get images being built, there was no straightforward way to automate deployment updates. My goal was to tag a release on Github and get a new version deployed in my environment. After searching for similar tools and couldn't find anything lightweight (spinnaker or jenkins were way too big!) I ended up building Keel.

Here's an example if anyone has this problem https://keel.sh/v1/examples/enabling-auto-updates.html.

This looks great, building and running it seems straightforward. Helm chart or K8s deployment.yaml template would be handy too :)

As a backend developer I find flutter great. Recently created an app that uses Go compiled with gomobile as a backend for flutter UI. Widgets are great, Dart lang is easy to learn and understand :)

Another option is webrelay ingress controller for k8s, also tunnel based :) https://webhookrelay.com/v1/examples/relay-ingress.html

I have two projects that talk directly with k8s, it's keel (CI tool for kube) https://github.com/keel-hq/keel and ingress controller for webhookrelay.com so I need a working cluster locally. However, other services are also tested on local minikube as it's easier to make sure they are interacting as intended when running in K8s :)

Yep, for local development it's the same, a lot easier to just rebuild and run. Haven't thought about `gcloud docker pull`, thanks!

I guess this is also quite important with any other registry such as jfrog, quay, etc. And it's good that credentials are safer (I hope so) in the osx keychain rather than Minikube.

I also had a look at Docker for Mac. It's now my default k8s dev environment, I must admit that even if their high CPU usage issue it's still a lot more CPU friendly than minikube.

What's great for development is that you can also build images on Mac and run them inside k8s environment, no need to change daemons. Which was sometimes a bit annoying with Minikube and I usually found myself just pushing them to the dockerhub and then pulling to minikube :) However, not sure why the dashboard is not enabled by default, it's quite handy.

If you are interested in ingress controllers and demoing your apps directly from your mac, have a look at my recent blog post: https://webhookrelay.com/blog/2018/01/08/ingress-with-docker...

Hello, Webhook Relay founder here. Pretty much all different cloud providers offer different types of load balancers (probably due to their existing, pre-container infrastructure). I believe there is a need to have a simple, cloud-agnostic ingress controller that can be used both in local environment, self-hosted Kubernetes cluster or any existing managed k8s service. Currently I would recommend to use it mostly for development purposes as we sort out any arising problems and add TLS support into the ingress controller itself (so you can define HTTPS hosts in the ingress.yml), however you can already enable HTTPS for your ingresses via CLI or UI.

Amazing game! fun fact - works a lot smoother on mobile nexus 6P than MB Pro 2015 :)

Yep, same here. Bought a bonsai, fertiliser and tiny scissors for the little fella. Didn't even last a month under my management. I wonder what kind of care those trees require. Now I just opted for a few cactuses, they seem fine.

VPN would also do the job

when visiting Austin, US I went for a burger in Fridays near a highway and cashier was like "Oh my god, I have never seen this thing working!!!" after my contactless worked on their terminal :D Apparently it's too much magic and people just stopped trying to use chip, contactless or anything else. Just cash and swipe :)

Looks like these guys (Tendermint team) actually care about design, testing and scalability in their project compared to Ethereum where people are concentrating on hype rather than product (I am not rude, used Ethereum from the client's perspective) :)

It would be interesting to hear from people who actually use (if there are any) Tendermint: * How easy/hard is it to create bindings to the blockchain from your own backend application (as I can see there is a GRPC option). * How many nodes you are running? * What's the use case?

This is totally not true. It depends on how you structure your project. Vue is good for simple things but it scales way better for large complex apps than React. Why? Less boilerplate. And less boilerplate = less code to maintain. Vue HTML template functions are really well designed with just enough functionality to make your life easier but also encouraging you to build custom components when you need something custom :)

My only suggestion for people starting with Vue is to not be afraid of directives (Vue directives are nice and have nothing to do with Angular directives), group your .vue components into directories and don't jump into Vuex right away (same goes for React beginners, don't force yourself to learn Redux for your 1 page app).

Go is a good example - I have several services that consume ~20MB of RAM so no need for beefy boxes. Although that's why I also chose to use Kubernetes - extremely easy to pack a bunch of services.

Hi HN,

I have been using k8s for a while on Google Container Engine and what I found missing was a tool to automatically update my deployments. Cloudbuild is great to build images and Kubernetes on f1-micro nodes is very cheap to run therefore I decided to build a lightweight service to fully automate my delivery workflow.

Currently I need only to tag an image on Github and after few minutes I get an updated k8s deployment. Feedback is welcome!