vonc + stack   66

Deploy the Voting App on a Docker Swarm using Compose version 3 – @lucjuggery – Medium
With Docker 1.13, it’s now possible to deploy a stack from a docker-compose file. Let’s test that and deploy the Voting App on a 3 nodes swarm. Using Docker Machine, we will start by creating the…
docker  compose  swarm  stack  mesh  important 
february 2017 by vonc
The Distributed Developer Stack Field Guide
The definitive source for mainstream technology practitioners to discover and understand the tools and concepts prominent in the shift to the distributed development stack (DDS).
distributed  development  stack  guide  list  reference  oreilly 
february 2015 by vonc
Docker GitLab by sameersbn
Zero to GitLab in 5 seconds or less* docker run --name='gitlab' -i -t --rm \ -p 127.0.0.1:10022:22 -p 127.0.0.1:10080:80 \ -e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" \ sameersbn/gitlab:latest oint your browser to http://localhost:10080 and login using the default username and password: username: admin@local.host password: 5iveL!fe
docker  nginx  mysql  installation  stack 
june 2014 by vonc
Quotes of the week [LWN.net]
I'm sure that works great with the GO error handling model... hope they're not forgetting to check every close() for an error status.
Quotes of the week
Posted Jul 3, 2012 22:31 UTC (Tue) by twm (subscriber, #67436) [Link]

As a Python programmer, I find Go's lack of exceptions to be one of its many attractive features. You only have to be bitten by an uncaught exception in production so many times to start questioning the whole concept.
Quotes of the week
Posted Jul 4, 2012 0:27 UTC (Wed) by Cyberax (subscriber, #52523) [Link]

Try writing any non-trivial code in Go and you'll be bitten by ignored error code values.
That's even worse, exceptions are at least visible.
Quotes of the week
Posted Jul 4, 2012 4:11 UTC (Wed) by twm (subscriber, #67436) [Link]

So don't ignore error code return values. You wrote buggy code that doesn't handle errors; it's not like Ruby or Python prevents the same. At the very least, it's a problem you can take measure of via static analysis---try doing that
stack  handling  exception  error  golang  go 
august 2012 by vonc

related tags

1.12  ack  adt  akka  algorithms  alternative  analysis  answer  architecture  article  bag  benchmark  BestPractices  blackbox  bundle  c  callstack  careers  cli  cloud  cobra  coffeescript  comparison  compilation  compose  concept  concurrency  configuration  container  contiguous  continuous  copy  criticisms  cube  culture  curl  dab  database  deployment  developer  development  devops  diagnostic  diagram  distributed  docker  dockerfile  ecs  elasticsearch  embedded  english  enterprise  err  error  errors  escape  esl  evaluation  example  exception  forum  frame  full  fullstack  game  generics  Git  go  golang  goroutine  grafana  grpc  guide  handler  handling  haskell  heap  http  hyperv  immutable  import  important  information  ingeneer  inlining  installation  interface  java  june  kernel  kibana  kubernetes  lamp  language  learning  library  line  linker  linux  list  logstash  lowlevel  map  mean  memory  mesh  method  middleware  monitoring  mysql  native  net  network  networking  nginx  notion  nuc  observability  operating  operator  oreilly  os  overload  packets  paper  performance  php  pods  pointer  postmortem  presentation  programation  programming  prometheus  promotheus  proposal  protocol  question  questions  queue  ranking  recursion  redis  reference  resolution  review  runtime  rust  scala  scaling  schema  screen  Security  segmented  server  service  set  sgment  size  slides  so  split  sql  ssd  stack  stackexchange  stackoverflow  stacktrace  swarm  sysadmin  System  tcp  tcpip  test  testing  thread  tls  travel  tuning  tutorial  uber  unwinding  webserver  whitebox  Windows  wrap  wrapper  xml 

Copy this bookmark:



description:


tags: