Skip to content

Instantly share code, notes, and snippets.

Avatar

Patrik Votoček Vrtak-CZ

View GitHub Profile
@Vrtak-CZ
Vrtak-CZ / live.html
Last active Sep 17, 2019
KartPlanet LIVE timing
View live.html
<iframe id="BestTimes" width="2000" height="3000" scrolling="no" frameborder="0" align="middle"
allowtransparency="true"
src="https://live.racefacer.com/kartplanet?hide_header=0&hide_sidebar=1&theme=black"></iframe>
View vault.yaml
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: vault
namespace: vault
labels:
app: vault
spec:
serviceName: vault
View keybase.md

Keybase proof

I hereby claim:

  • I am vrtak-cz on github.
  • I am vrtakcz (https://keybase.io/vrtakcz) on keybase.
  • I have a public key ASBqZzWB4Cbn2-WQtfos4MVjLSJhvINCcF888dDUO6VQfQo

To claim this, I am signing this object:

@Vrtak-CZ
Vrtak-CZ / Dockerfile
Last active Apr 11, 2017
SSH Fingerprint
View Dockerfile
FROM shipito/nodejs:6-alpine
MAINTAINER Patrik Votocek <patrik@votocek.cz>
RUN chmod -R 0700 /root/.ssh && \
touch /root/.ssh/known_hosts && \
ssh-keyscan github.com | ssh-keygen -lf /dev/stdin | grep -q "nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8" && \
ssh-keyscan github.com >> /root/.ssh/known_hosts
@Vrtak-CZ
Vrtak-CZ / gist:d62f3b45c4ad059d5b2fd7fb2770e926
Created Feb 20, 2017
CloudFormation YAML VPC CIDR error
View gist:d62f3b45c4ad059d5b2fd7fb2770e926
I'm trying to switch our template for VPC from JSON to YAML (because of better readability). Validation is OK but when i try update our stack I'm getting "CIDR block vpc-xxxxxxxx is malformed". Btw CIDR is same as is in old JSON template used for creating / updating this stack before.
{code}
Mappings:
SubnetConfig:
VPC:
CIDR: '10.13.0.0/16'
Resources:
VPC:
@Vrtak-CZ
Vrtak-CZ / crazy-ingress-controller.md
Last active Feb 17, 2017
Crazy ingress controller logs
View crazy-ingress-controller.md

We have ALB (Application Load Balancer - internet-facing) connected to Kubernetes Nodes (private subnet). Nginx ingress controller (gcr.io/google_containers/nginx-ingress-controller:0.8.3). And default http backend (gcr.io/google_containers/defaultbackend:1.2). Health check in target group is set to:

Protocol: HTTP
Path:	/healthz
Port: 80
Healthy threshold: 2
Unhealthy threshold: 10
@Vrtak-CZ
Vrtak-CZ / req.md
Last active Nov 19, 2016
AWS ECS Dotazy
View req.md

1. Porty

Zatím mám jenom jednu ECS instanci. A mám problém s portama. Task je v modu Host a container má Port mappings: Container port 80 tcp. Pokud service nastavím Number of tasks na 2. Tj chci aby běželi 2 containery tak dostanu error.

service goodbaby-test-service was unable to place a task because no container instance met all of its requirements. The closest matching container-instance bcf744e7-7ad5-xxxx-xxxx-ab277caa9c0d is already using a port required by your task. For more information, see the Troubleshooting section.

Celé to je napojené na ELB (classic protože TCP).

View README.md

Zadání pro lektory

  1. Vem kód,
  2. forkni ho,
  3. přidej 2 chyby.

Pak forky projedu a pospojuju.

Cílem je soubor o ~100 řádcích, tak přidávej metody a třídy!

View keybase.md

Keybase proof

I hereby claim:

  • I am Vrtak-CZ on github.
  • I am vrtakcz (https://keybase.io/vrtakcz) on keybase.
  • I have a public key whose fingerprint is 10B3 A28F 2CB4 7E2E B087 48DE 231E F960 7EB7 2E87

To claim this, I am signing this object:

View dynamicReturnTypeMeta.json
{
"methodCalls": [
{
"class": "\\Slevomat\\Entity\\EntityManager",
"method": "create",
"position": 0
},
{
"class": "\\Slevomat\\Entity\\EntityManager",
"method": "getByPrimary",