Ola, Hoje irei falar sobre um Dockerfile criado para rodar um Docker do spider/Scrapy criado nesse post (link)A ideia do post nao e explicar como funciona ou o que e o Docker, pois ha inumeros tutorias e conteudos na internet explicando muito bem o que e o Docker. Sendo assim, para rodar o Dockerfile apresentado abaixo em sua maquina, sera preciso ter o Docker instalado previamente em seu ambiente.DockerfileCriando imagem a partir do Dockerfile:Parametro -t informa o nome da imagem que sera gerada (no caso 'scrapy').Saida do comando de build:Rodando nosso Docker:Parametro -d e o nome da imagemVerificando log de saida do scrapy Primeiro vamos rodar o comando "ps" para pegar o id do nosso Docker:Com o id em maos (cac0e1987b5d) vamos visualizar o log de saida do scrapy que esta rodando em nosso Docker.:Saida do comando "log"Ate a proxima! Acesso SSH com KeysAbaixo sera descrito como acessar um servidor remoto com par de chaves privada/publica. Alem de nao precisar inserir a senha a cada acesso, acessar um servidor atraves de chaves torna o acesso mais seguro.1 - Criando RSA Key Pairssh-keygen -t rsaVoce pode optar por deixar o passphrase vazio.2 - para copiar chave publica para o servidor remoto vamos utilizar o ssh-copy-id;ssh-copy-id -i ~/.ssh/id_rsa.pub "user@192.168.0.2"Definindo alguma porta diferente da padrao (22)ssh-copy-id -i ~/.ssh/id_rsa.pub -p 25 "user@192.168.0.2"3 - Acessar a maquina remota;ssh user@192.168.0.2Obs: Caso o servidor ainda pergunte a senha de acesso. Entre no servidor remoto e conceda permissao para pasta .ssh:chmod 700 ~/.sshchmod 600 ~/.ssh/authorized_keysFontes:https://www.digitalocean.com/community/tutorials/how-to-set-up-ssh-keys--2http://stackoverflow.com/questions/6377009/adding-public-key-to-ssh-authorized-keys-does-not-log-me-in-automatically Informational100 - ContinueA status code of 100 indicates that (usually the first) part of a request has been received without any problems, and that the rest of the request should now be sent.101 - Switching ProtocolsHTTP 1.1 is just one type of protocol for transferring data on the web, and a status code of 101 indicates that the server is changing to the protocol it defines in the "Upgrade" header it returns to the client. For example, when requesting a page, a browser might receive a statis code of 101, followed by an "Upgrade" header showing that the server is changing to a different version of HTTP.Successful200 - OKThe 200 status code is by far the most common returned. It means, simply, that the request was received and understood and is being processed.201 - CreatedA 201 status code indicates that a request was successful and as a result, a resource has been created (for example a new page).202 - AcceptedThe status code 202 indicates that server has received and understood the request, and that it has been accepted for processing, although it may not be processed immediately.203 - Non-Authoritative InformationA 203 status code means that the request was received and understood, and that information sent back about the response is from a third party, rather than the original server. This is virtually identical in meaning to a 200 status code.204 - No ContentThe 204 status code means that the request was received and understood, but that there is no need to send any data back.205 - Reset ContentThe 205 status code is a request from