fabiocruzcoelho

# Enviroment variables echo $'\uf303'
export ZSH=/home/fabio/.oh-my-zsh
export SSH_KEY_PATH="~/.ssh/rsa_id"
export LANG=en_US.UTF-8
export TERMINAL=terminator
export PAGER=less
export VISUAL=vim
export TERM="xterm-256color"

# Preferred editor for local and remote sessions

fabiocruzcoelho

Passos para controlar windows server via ansible - Passos executados no windows server

PS > mkdir C:\work
PS > cd C:\work
PS > Invoke-WebRequest -Uri \
https://raw.githubusercontent.com/ansible/ansible/devel/examples/scripts/ConfigureRemotingForAnsible.ps1 \
-OutFile ConfigureRemotingForAnsible.ps1
PS > powershell -ExecutionPolicy RemoteSigned .\ConfigureRemotingForAnsible.ps1 -SkipNetworkProfileCheck

Passos executados no Linux

fabiocruzcoelho

Inicia Cluster com volume persistente

$ oc cluster up --routing-suffix=35.184.212.240.nip.io \
--public-hostname=openshift.dominio.com.br \
--host-data-dir=/data/openshift --metrics=true

fabiocruzcoelho

# Link com comandos (desfazendo as coisas)
https://git-scm.com/book/pt-br/v1/Git-Essencial-Desfazendo-Coisas

# Comandos basicos
git clone git@github.com:wedsonlima/git-presentation.git
git remote -v # pra onde o respositório está apontando
git branch # listar os branchs existentes
git branch tarefa1
git checkout tarefa1
echo 'arquivo 1' > file1.txt

fabiocruzcoelho

Ideas for improvements to git log --graph

I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.

Make the graph for --topo-order less wiggly

Imagine a long-running development branch periodically merges from master. The git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.

It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.

fabiocruzcoelho

proxy_cache_valid     1h; # 200, 301 and 302 will be cached.
proxy_cache_use_stale error
    timeout
    invalid_header
    http_500
    http_502
    http_504
    http_404;

proxy_buffering           on;

fabiocruzcoelho

# Size Limits
client_body_buffer_size         200M;
server_names_hash_bucket_size 128;
client_header_buffer_size       128K;
client_max_body_size            200M;    # php's upload_max_filesize
large_client_header_buffers     8 8k;
output_buffers                  1 32k;
postpone_output                 1460;
proxy_buffers                   8 16k;
proxy_buffer_size               32k;

fabiocruzcoelho

Passos para configurar um resgitry private em um cluster kubernetes

# Gerando os certificados para o registry private
$ openssl genrsa -out "/etc/pki/tls/private/regitry.key" 4096
$ openssl req -x509 -sha512 -nodes -newkey rsa:4096 -days 730 -keyout /etc/pki/tls/private/registry.key \
 -out /etc/pki/tls/certs/registry.crt
$ openssl req -new -x509 -text -key registry.key -out gitlab-registry.cert

fabiocruzcoelho

# resources.xml windows user local

<node name="app05" 
   connectionType="WINRM_NATIVE"
     node-executor="overthere-winrm"
     winrm-password-option="winrmPassword" 
     winrm-protocol="http" 
     winrm-auth-type="basic" 
     username="administrator" 
     winrm-password-storage-path="keys/admin.password"

fabiocruzcoelho

<?xml version="1.0" encoding="UTF-8"?>

<project>
  <node name="btu-appservers01" 
     description="Tomcat Applications Server01"
   	 tags="" 
   	 hostname="btu-appservers01"
   	 osArch="amd64" 
   	 osFamily="unix" 
   	 osName="Linux"