# data[].attributes.body
Integrante 1: Rodrigo Ferreira
Integrante 2: Anderson Borges
Integrante 3: João Victor Rossi
Integrante 4: Dennys Terra
Integrante 5: Thiago Freitas

# data[].attributes.body
Link da imagem do container:
https://hub.docker.com/_/python

Essa imagem é utilizada para facilitar a instalação da linguagem Python e ferramentas de desenvolvimentos associadas, como o interpretador e com diversas versões e aplicabilidades.

# data[].attributes.body
MySQL é o banco de dados de código aberto mais popular do mundo. Com seu desempenho, confiabilidade e facilidade de uso comprovados, o MySQL tornou-se a principal escolha de banco de dados para aplicativos baseados na Web, abrangendo toda a gama de projetos pessoais e sites, passando por comércio eletrônico e serviços de informação, até propriedades da web, incluindo Facebook, Twitter, YouTube, Yahoo! e muitos mais.

# data[].attributes.attachment_link.description
MySQL is a widely used, open-source relational database management system (RDBMS).

# data[].attributes.body
O MariaDB Server é um dos servidores de banco de dados mais populares do mundo. É feito pelos desenvolvedores originais do MySQL e garantido para permanecer em código aberto. Usuários notáveis ​​incluem Wikipedia, DBS Bank e ServiceNow.

A intenção também é manter alta compatibilidade com o MySQL, garantindo uma equivalência binária de biblioteca e correspondência exata com as APIs e comandos do MySQL.

# data[].attributes.attachment_link.description
MariaDB Server is a high performing open source relational databases, forked from MySQL.

# data[].attributes.body
O Ubuntu é um sistema dedicado para o desktop que permite muitas facilidades! Como resultado, ele não apenas apresenta uma interface amigável como ainda é gratuito. Além disso, seu uso permite o apoio de um suporte profissional em uma das comunidades mais robustas do Linux do mundo.

# data[].attributes.attachment_link.description
Ubuntu is a Debian-based Linux operating system based on free software.

# data[].attributes.body
O Python é uma linguagem de programação, foi desenvolvido para ser simples, fácil de aprender e muito versátil, ou seja, você vai poder utilizar essa linguagem para diversas tarefas.

Outro ponto muito importante é que o mesmo código ele funciona Windows, Linux e macOS sem que sejam necessários ajustes nos códigos (claro, as bibliotecas podem sofrer alguma alteração por conta do sistema operacional).

Nós dividimos em 3 grandes áreas as aplicações do Python para facilitar:

Automatizar tarefas chatas e repetitivas, automações, RPA…

Análise de dados e Ciência de dados;

Construção de sites, aplicativos, jogos… programas em geral.

Alguns exemplos de sites/aplicativos que foram criados em Python ou utilizam essa linguagem na construção para que você entenda que ele é bem importante e muito utilizado.

Instagram, Google, Spotify, Netflix, Uber…

# data[].attributes.attachment_link.description
Python is an interpreted, interactive, object-oriented, open-source programming language.

# data[].attributes.body
Mongo-express é uma interface de administração MongoDB baseada na web escrita em Node.js, Express.js e Bootstrap3.

# data[].attributes.attachment_link.title
mongo-express - Official Image | Docker Hub

# data[].attributes.attachment_link.description
Web-based MongoDB admin interface, written with Node.js and express

# data[].attributes.body
https://hub.docker.com/r/middlewaregruppen/kubez

Middleware é um software que fornece serviços e recursos comuns a aplicações. Gerenciamento de dados, serviços de aplicações, sistema de mensageria, autenticação e gerenciamento de APIs são recursos comumente operados por um software de middleware.

Dr. Kubez é uma ferramenta para testar, diagnosticar e carregar clusters k8s.

# data[].attributes.body
O IBM Security Guardium é uma plataforma abrangente de proteção de dados que permite que as organizações descubram dados confidenciais, protejam dados contra ameaças internas e externas e automatizem a conformidade. O Guardium Data Protection oferece visibilidade e controle centralizados em ambientes de dados heterogêneos, como bancos de dados, data warehouses, plataformas de big data, sistemas de arquivos e ambientes de nuvem para ajudar a garantir a integridade dos dados, não importa onde eles residam.

# data[].attributes.body
https://hub.docker.com/_/alpine

Alpine Linux é uma distribuição Linux construída em torno de musl libc e BusyBox . A imagem tem apenas 5 MB de tamanho e tem acesso a um repositório de pacotes que é muito mais completo do que outras imagens baseadas em BusyBox.

# data[].attributes.body
OpenJDK (Open Java Development Kit) é uma implementação gratuita e de código aberto da Plataforma Java, Standard Edition (Java SE). OpenJDK é a implementação de referência oficial do Java SE desde a versão 7.

# data[].attributes.attachment_link.description
"Vanilla" builds of OpenJDK (an open-source implementation of the Java Platform, Standard Edition)

# data[].attributes.body
https://hub.docker.com/_/openjdk

O Java oferece a funcionalidade de uma linguagem bastante potente, derivada de C e C ++, porém, sem os recursos confusos e pouco utilizados desses.

Orientado a objetos. ...

Distribuído. ...

Independente da plataforma. ...

Coletor de lixo. ...

Seguro e sólido. ...

Multi-thread.

# data[].attributes.attachment_link.description
"Vanilla" builds of OpenJDK (an open-source implementation of the Java Platform, Standard Edition)

# data[].attributes.body
O WordPress é uma ferramenta de blog gratuita e de código aberto e um sistema de gerenciamento de conteúdo (CMS) baseado em PHP e MySQL, que é executado em um serviço de hospedagem na web. Os recursos incluem uma arquitetura de plugins e um sistema de templates. O WordPress é usado por mais de 22,0% dos 10 milhões de sites mais importantes em agosto de 2013. O WordPress é o sistema de blogs mais popular em uso na Web, em mais de 60 milhões de sites.

# data[].attributes.attachment_link.readable_text
WordPress is a free and open source blogging tool and a content management system (CMS) based on PHP and MySQL, which runs on a web hosting service. Features include a plugin architecture and a template system. WordPress is used by more than 22.0% of the top 10 million websites as of August 2013. WordPress is the most popular blogging system in use on the Web, at more than 60 million websites. The most popular languages used are English, Spanish and Bahasa Indonesia.

wikipedia.org/wiki/WordPress

$ docker run --name some-wordpress --network some-network -d wordpress

The following environment variables are also honored for configuring your WordPress instance (by a custom wp-config.php implementation):

-e WORDPRESS_DB_HOST=...

-e WORDPRESS_DB_USER=...

-e WORDPRESS_DB_PASSWORD=...

-e WORDPRESS_DB_NAME=...

-e WORDPRESS_TABLE_PREFIX=...

-e WORDPRESS_AUTH_KEY=..., -e WORDPRESS_SECURE_AUTH_KEY=..., -e WORDPRESS_LOGGED_IN_KEY=..., -e WORDPRESS_NONCE_KEY=..., -e WORDPRESS_AUTH_SALT=..., -e WORDPRESS_SECURE_AUTH_SALT=..., -e WORDPRESS_LOGGED_IN_SALT=..., -e WORDPRESS_NONCE_SALT=... (default to unique random SHA1s, but only if other environment variable configuration is provided)

-e WORDPRESS_DEBUG=1 (defaults to disabled, non-empty value will enable WP_DEBUG in wp-config.php)

-e WORDPRESS_CONFIG_EXTRA=... (defaults to nothing, non-empty value will be embedded verbatim inside wp-config.php -- especially useful for applying extra configuration values this image does not provide by default such as WP_ALLOW_MULTISITE; see docker-library/wordpress#142 for more details)

The WORDPRESS_DB_NAME needs to already exist on the given MySQL server; it will not be created by the wordpress container.

If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:

$ docker run --name some-wordpress -p 8080:80 -d wordpress

Then, access it via http://localhost:8080 or http://host-ip:8080 in a browser.

When running WordPress with TLS behind a reverse proxy such as NGINX which is responsible for doing TLS termination, be sure to set X-Forwarded-Proto appropriately (see "Using a Reverse Proxy" in "Administration Over SSL" in upstream's documentation). No additional environment variables or configuration should be necessary (this image automatically adds the noted HTTP_X_FORWARDED_PROTO code to wp-config.php if any of the above-noted environment variables are specified).

If your database requires SSL, WordPress ticket #28625 has the relevant details regarding support for that with WordPress upstream. As a workaround, the "Secure DB Connection" plugin can be extracted into the WordPress directory and the appropriate values described in the configuration of that plugin added in wp-config.php.

Docker Secrets

As an alternative to passing sensitive information via environment variables, _FILE may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in /run/secrets/<secret_name> files. For example:

$ docker run --name some-wordpress -e WORDPRESS_DB_PASSWORD_FILE=/run/secrets/mysql-root ... -d wordpress:tag

Currently, this is supported for WORDPRESS_DB_HOST, WORDPRESS_DB_USER, WORDPRESS_DB_PASSWORD, WORDPRESS_DB_NAME, WORDPRESS_AUTH_KEY, WORDPRESS_SECURE_AUTH_KEY, WORDPRESS_LOGGED_IN_KEY, WORDPRESS_NONCE_KEY, WORDPRESS_AUTH_SALT, WORDPRESS_SECURE_AUTH_SALT, WORDPRESS_LOGGED_IN_SALT, WORDPRESS_NONCE_SALT, WORDPRESS_TABLE_PREFIX, and WORDPRESS_DEBUG.

Example docker-compose.yml for wordpress:

version: '3.1' services: wordpress: image: wordpress restart: always ports: - 8080:80 environment: WORDPRESS_DB_HOST: db WORDPRESS_DB_USER: exampleuser WORDPRESS_DB_PASSWORD: examplepass WORDPRESS_DB_NAME: exampledb volumes: - wordpress:/var/www/html db: image: mysql:8.0 restart: always environment: MYSQL_DATABASE: exampledb MYSQL_USER: exampleuser MYSQL_PASSWORD: examplepass MYSQL_RANDOM_ROOT_PASSWORD: '1' volumes: - db:/var/lib/mysql volumes: wordpress: db:

Run docker stack deploy -c stack.yml wordpress (or docker-compose -f stack.yml up), wait for it to initialize completely, and visit http://swarm-ip:8080, http://localhost:8080, or http://host-ip:8080 (as appropriate).

Adding additional libraries / extensions

This image does not provide any additional PHP extensions or other libraries, even if they are required by popular plugins (e.g. it cannot send e-mails). There are an infinite number of possible plugins, and they potentially require any extension PHP supports. Including every PHP extension that exists would dramatically increase the image size.

If you need additional PHP extensions, you'll need to create your own image FROM this one. The documentation of the php image explains how to compile additional extensions. Additionally, an older Dockerfile for wordpress has a simplified example of doing this and a newer version of that same Dockerfile has a much more thorough example.

Include pre-installed themes / plugins

Mount the volume containing your themes or plugins to the proper directory; and then apply them through the "wp-admin" UI. Ensure read/write/execute permissions are in place for the user:

Themes go in a subdirectory in /var/www/html/wp-content/themes/

Plugins go in a subdirectory in /var/www/html/wp-content/plugins/

If you wish to provide additional content in an image for deploying in multiple installations, place it in the same directories under /usr/src/wordpress/ instead (which gets copied to /var/www/html/ on the container's initial startup).

Static image / updates-via-redeploy

The default configuration for this image matches the official WordPress defaults in which automatic updates are enabled (so the initial install comes from the image, but after that it becomes self-managing within the /var/www/html/ data volume).

If you wish to have a more static deployment (similar to other containerized applications) and deploy new containers to update WordPress + themes/plugins, then you'll want to use something like the following (and run the resulting image read-only):

FROM wordpress:apache WORKDIR /usr/src/wordpress RUN set -eux; \ find /etc/apache2 -name '*.conf' -type f -exec sed -ri -e "s!/var/www/html!$PWD!g" -e "s!Directory /var/www/!Directory $PWD!g" '{}' +; \ cp -s wp-config-docker.php wp-config.php COPY custom-theme/ ./wp-content/themes/custom-theme/ COPY custom-plugin/ ./wp-content/plugins/custom-plugin/

For FPM-based images, remove the find instruction and adjust the SCRIPT_FILENAME paths in your reverse proxy from /var/www/html to /usr/src/wordpress.

Run the result read-only, providing writeable storage for /tmp, /run, and (optionally) wp-content/uploads:

$ docker run ... \ --read-only \ --tmpfs /tmp \ --tmpfs /run \ --mount type=...,src=...,dst=/usr/src/wordpress/wp-content/uploads \ ... \ --env WORDPRESS_DB_HOST=... \ --env WORDPRESS_AUTH_KEY=... \ --env ... \ custom-wordpress:tag

Note: be sure to rebuild and redeploy regularly to ensure you get all the latest WordPress security updates.

Running as an arbitrary user

See the "Running as an arbitrary user" section of the php image documentation.

When running WP-CLI via the cli variants of this image, it is important to note that they're based on Alpine, and have a default USER of Alpine's www-data, whose UID is 82 (compared to the Debian-based WordPress variants whose default effective UID is 33), so when running wordpress:cli against an existing Debian-based WordPress install, something like --user 33:33 is likely going to be necessary (possibly also something like -e HOME=/tmp depending on the wp command invoked and whether it tries to use ~/.wp-cli). See docker-library/wordpress#256 for more discussion around this.

Configuring PHP directives

See the "Configuration" section of the php image documentation.

For example, to adjust common php.ini flags like upload_max_filesize, you could create a custom.ini with the desired parameters and place it in the $PHP_INI_DIR/conf.d/ directory:

FROM wordpress:tag COPY custom.ini $PHP_INI_DIR/conf.d/

The wordpress images come in many flavors, each designed for a specific use case.

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

wordpress:<version>-fpm

This variant contains PHP-FPM, which is a FastCGI implementation for PHP. See the PHP-FPM website for more information about PHP-FPM.

In order to use this image variant, some kind of reverse proxy (such as NGINX, Apache, or other tool which speaks the FastCGI protocol) will be required.

Some potentially helpful resources:

WARNING: the FastCGI protocol is inherently trusting, and thus extremely insecure to expose outside of a private container network -- unless you know exactly what you are doing (and are willing to accept the extreme risk), do not use Docker's --publish (-p) flag with this image variant.

wordpress:cli

This image variant does not contain WordPress itself, but instead contains WP-CLI.

The simplest way to use it with an existing WordPress container would be something similar to the following:

$ docker run -it --rm \ --volumes-from some-wordpress \ --network container:some-wordpress \ -e WORDPRESS_DB_USER=... \ -e WORDPRESS_DB_PASSWORD=... \ # [and other used environment variables] wordpress:cli user list

Generally speaking, for WP-CLI to interact with a WordPress install, it needs access to the on-disk files of the WordPress install, and access to the database (and the easiest way to accomplish that such that wp-config.php does not require changes is to simply join the networking context of the existing and presumably working WordPress container, but there are many other ways to accomplish that which will be left as an exercise for the reader).

NOTE: Since March 2021, WordPress images use a customized wp-config.php that pulls the values directly from the environment variables defined above (see wp-config-docker.php in docker-library/wordpress#572 and docker-library/wordpress#577). As a result of reading environment variables directly, the cli container also needs the same set of environment variables to properly evaluate wp-config.php.

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's wordpress/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

# data[].attributes.attachment_link.description
The WordPress rich content management system can utilize plugins, widgets, and themes.

# data[].attributes.body
O Amazon Linux é fornecido pela Amazon Web Services (AWS). Ele foi projetado para fornecer um ambiente de execução estável, seguro e de alto desempenho para aplicativos executados no Amazon EC2. A distribuição completa inclui pacotes que permitem fácil integração com a AWS, incluindo ferramentas de configuração de inicialização e muitas bibliotecas e ferramentas populares da AWS. A AWS fornece atualizações contínuas de segurança e manutenção para todas as instâncias que executam o Amazon Linux.

A imagem de contêiner do Amazon Linux contém um conjunto mínimo de pacotes. Para instalar pacotes adicionais, useyum .

A AWS fornece duas versões do Amazon Linux: Amazon Linux 2 e Amazon Linux AMI .

# data[].attributes.attachment_link.title
Amazonlinux - Official Image | Docker Hub

# data[].attributes.attachment_link.description
Amazon Linux provides a stable, secure, and high-performance execution environment for applications.

# data[].attributes.body
https://hub.docker.com/r/blacklabelops/virtualbox

VirtualBox é um produto de virtualização da Oracle para expandir os recursos de utilização do seu computador. Virtualização trata-se da criação de um ou mais ambientes virtuais dentro de um mesmo computador físico, que funcionam de maneiras independentes.

Este exemplo que selecionamos aqui é um container com Hashicorp Otto, Vagrant e Packer com Virtualbox.

# data[].attributes.body
https://hub.docker.com/r/microsoft/azure-cosmos-emulator-linux

O Microsoft Azure Storage Emulator é uma ferramenta que emula os serviços Azure Blob, Queue e Table para fins de desenvolvimento local .