Let's look at some basic kubectl output options.
Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).
We can start with:
kubectl get no
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
| # set the base image to Debian | |
| # https://hub.docker.com/_/debian/ | |
| FROM debian:latest | |
| # replace shell with bash so we can source files | |
| RUN rm /bin/sh && ln -s /bin/bash /bin/sh | |
| # update the repository sources list | |
| # and install dependencies | |
| RUN apt-get update \ |
git log --oneline -1 <PR-BRANCH>git push -f origin :| <VictorySharedEvents | |
| events={[ | |
| { | |
| childName: "firstBar", // if a child name is not provided, event will be attached to all children. | |
| target: "data", // what type of element to attach to. Matches the style namespaces | |
| eventKey: 1, // What event key of element to attach to. Defaults to the index in data. | |
| eventHandlers: { | |
| onClick: () => { | |
| return { | |
| childName: "secondBar", // the child to be modified |
| { | |
| "env": { | |
| "node": true, | |
| "es6": true | |
| }, | |
| "ecmaFeatures": { | |
| "arrowFunctions": true, | |
| "blockBindings": true, | |
| "classes": true, | |
| "defaultParameters": true, |
| { | |
| "env": { | |
| "browser": true, | |
| "node": true, | |
| "es6": true | |
| }, | |
| "plugins": ["react"], | |
| "ecmaFeatures": { |
Magic words:
psql -U postgresSome interesting flags (to see all, use -h or --help depending on your psql version):
-E: will describe the underlaying queries of the \ commands (cool for learning!)-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)