devops

Redirect an app running at 127.0.0.1:8000 to 443
default.conf

server {
    listen 80;

    location / {
        proxy_pass http://127.0.0.1:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

server {
    listen 443 ssl;

    ssl_certificate /etc/nginx/cert.pem;
    ssl_certificate_key /etc/nginx/key.pem;

    location / {
        proxy_pass http://127.0.0.1:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes
docker run --name nginx-proxy -p 80:80 -p 443:443 -v $(pwd)/default.conf:/etc/nginx/conf.d/default.conf -v $(pwd)/cert.pem:/etc/nginx/cert.pem -v $(pwd)/key.pem:/etc/nginx/key.pem nginx

  filter (por defecto)
    * INPUT
    * FORWARD
    * OUTPUT
  nat
    * PREROUTING
    * OUTPUT
    * POSTROUTING
  mangle
    tiene todos los chains de filter y nat
    se usa para alteracion especializada del paquete (modifica TCP)
  raw (alta prioridad, modifica antes que todos)
    * PREROUTING
    * INPUT
  security (SELnux)
    * INPUT
    * FORWARD
    * OUTPUT

-j, –jump <target> ACCEPT DROP (no devuelve nada por defecto) REJECT
(devuelve ICMP unreachable/prohibited) REDIRECT DNAT SNAT

1. Ski patrol spends every morning marking and re-marking trail
   boundaries, difficulties, trees, stumps, cliffs and more(“Unmarked
   Obstacles Exist” signs). Solid documentation is essential for
   successful IT operations and breaking down DevOps silos
   
2. Ski with a buddy: Where does cross-training and pairing rank on your
   team’s priority list?
   
3. You can’t force your users to act wisely, but you can certainly help
   push them in the right direction -> a variety of seasonal and
   year-round safety awareness programs. When’s the last time your
   organization has had a meaningful security education campaign for
   ops, developers, or end-users?
   

1. Communications: Equipped with two-way radios, the Lift Operations
   team was able to notify Ski Patrol within moments of the incident.
   Does your incident escalation system (Slack/PagerDuty/email/etc.)
   allow you to get the right stakeholders involved, immediately? Do you
   truly communicate honestly with end-users during an incident?
   
2. Life Safety Skills: Ski Patrol are all trained EMTs, and most have
   decades of emergency medical, avalanche, and mountaineering
   experience. Does your on-call team have the training and access to
   production they truly need to mitigate real-time issues?
   
3. Lift Evacuation: If a tree falls in the woods, on a lift cable, can
   you hear it? No matter why the lift is disabled, Ski Patrol has
   several methods to get guests to the ground safely. In the Teller
   incident, Does your team know how to handle rollbacks? What about
   dealing with data corruption?
   
4. Today’s lift systems are loaded with sensors that can automatically
   stop the lift in case of critical component failure or tower
   derailment. Newer lifts have four independent braking systems and
   hundreds of safety sensors and controls. What unexpected single
   points of failure exist in your critical environment? DNS, TLS
   Certificates, and even “HA” databases are often a surprise.
   

1. Do you have the observability necessary to know when things start to
   go wrong in production before it impacts your users? Is time spent on
   non-production environments impacting what gets done in production?
   Does your team understand the risk that various production
   experiments pose?
   

https://faun.dev/ -> Chat/Foro con gente devops

https://github.com/mingrammer/diagrams

“7 Great Websites to Learn New Tech Skills” por Michael Vinh Xuan Thanh
https://link.medium.com/6XGAFMClf5

https://blog.pragmaticengineer.com/advice-to-myself-when-starting-as-a-software-developer/

Fábulas sobre código http://thecodelesscode.com/contents