One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
| Why coding streams/shows are interesting to me: in some livestreams, the experience is very similar to pair programming, | |
| but those people are experts. In VODs, it's more about problem solving and learning skills and approaches. The devs are really good | |
| at what they do and there is *always* a lot to learn. | |
| In no particular order: | |
| 1) Handmade Hero | |
| About the author: Casey Muratori. Worked at RAD. | |
| Description and why I like it: It kinda started the whole thing for me. Casey is coding a complete game and engine on stream, | |
| from scratch, one hour a day. He knows what he's doing on so many of the domains of game development and regular programing, |
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| readinessProbe: | |
| exec: | |
| command: ["/root/grpc_health_probe", "-addr=:6666"] | |
| initialDelaySeconds: 1 | |
| livenessProbe: | |
| exec: | |
| command: ["/root/grpc_health_probe", "-addr=:6666"] | |
| initialDelaySeconds: 2 | |
| imagePullPolicy: IfNotPresent |
A couple of code samples to show how a named pipe can be used to extend Go's channel paradigm for use between different processes running on a system.
Note that opening a write channel will return two channels -