sudo apt install zsh-autosuggestions zsh-syntax-highlighting zsh
Resumo da playlist de gerenciamento de projetos de software com gitlab
Representam os marcos de entrega do projeto. Devem ser associadas à sprints. Uma milestone por sprint.
image: nikolaik/python-nodejs:latest | |
stages: | |
- install | |
- test | |
- deploy | |
prodInstall: | |
stage: install | |
script: |
On GKE, there's an interesting overlap between what the IAM roles grant you for Kubernetes clusters. In general, the roles in the tables below line up with each other, but there are some strange exceptions. In each of the tables below are the results of a diff between related IAM roles (only the container.*
permissions are included in these results).
Project Owner | GKE Admin |
---|---|
container.hostServiceAgent.use |
Project Editor | GKE Developer |
---|
You should install VirtualBox and Vagrant before you start.
You should create a Vagrantfile
in an empty directory with the following content:
image: docker:latest | |
services: | |
- docker:dind | |
stages: | |
- build | |
- deploy | |
variables: | |
CONTAINER_DEV_IMAGE: registry.gitlab.com/brunomacf/kube-test:$CI_COMMIT_SHA |
See this issue.
Docker best practise to Control and configure Docker with systemd.
Create daemon.json
file in /etc/docker
:
{"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]}
In this post, we are going to see how to monitor docker logs from AWS Cloudwatch logs. Docker supports different logging drivers one of which is awslogs
For this excersice, Docker container need NOT be running on EC2. We can send docker logs from anywhere to AWS.
curl --include \ | |
--no-buffer \ | |
--header "Connection: Upgrade" \ | |
--header "Upgrade: websocket" \ | |
--header "Host: example.com:80" \ | |
--header "Origin: http://example.com:80" \ | |
--header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" \ | |
--header "Sec-WebSocket-Version: 13" \ | |
http://example.com:80/ |