tree: 3da722f78d34f7b3a3f50be9a452d8c32c71b87b [path history] [tgz]
  1. .bowerrc
  2. .gitignore
  3. DESIGN.md
  4. Makefile
  5. PROD.md
  6. README.md
  7. bower.json
  8. build_fiddle_release
  9. build_fiddler_release
  10. cpp/
  11. create-fiddle-sa.sh
  12. create-fiddler-pool.sh
  13. create-fiddler-sa.sh
  14. demo/
  15. elements.html
  16. fiddle/
  17. fiddler/
  18. fiddler_restart.sh
  19. go/
  20. package.json
  21. probersk.json5
  22. res/
  23. source/
  24. templates/
fiddlek/README.md

Fiddle

Allows trying out Skia code in the browser.

Running locally

To run locally:

$ make image

Then in two different shells:

$ make run_local_fiddle

$ make run_local_fiddler

Then visit http://localhost:8080

Continuous Deployment of fiddler

The fiddler image is continuously deployed as GCP Container Builder succeeds in building new gcr.io/skia-public/fiddler images. The app that does the deployment is infra/kube/go/continuous-deploy.

Node Pool

The fiddler-pool node pool is dedicated to running just fiddler pods. This was setup because fiddler latency was high for fiddle when run along with many other pods on 64 core nodes. To create a node pool that is dedicated to a certain kind of pod you need to label and taint all the nodes in the node pool, in this case with the same key,value pair:

reservedFor=fiddler

Using the same key/value pair isn't required, but it keeps it consistent.

Then add a tolerance to the pod description so it can run in the node-pool, and also add a nodeSelector so that the pods get scheduled into the pool.

spec:
  nodeSelector:
    reservedFor: fiddler
  tolerations:
    - key: "reservedFor"
      operator: "Equal"
      value: "fiddler"
      effect: "NoSchedule"