wordpress VS Docker Compose

#!/bin/sh set -euo pipefail # Based on wordpress:cli entrypoint # https://github.com/docker-library/wordpress/blob/master/php7.2/cli/docker-entrypoint.sh # If the first arg is `--some-option` then execute wp-cli if [ "${1#-}" != "$1" ]; then set -- wp "$@" fi # if our command is a valid wp-cli subcommand (say plugin), let's invoke it through wp-cli instead # (this allows for "docker run wordpress:cli help", etc) # documenation of the subcommand is shown if wp --path=/dev/null help "$1" > /dev/null 2>&1; then set -- wp "$@" fi # Execute aliases in the make file or directly the provided command if [ "$1" == "install" ] || [ "$1" == "configure" ]; then make -f /scripts/Makefile $1 else exec "$@" fi

You can take a look at the dockerfile here for educational purposes and you can see apache is not configured to listen on 443 at all. And if you read the "How to use this image" section on the docker hub page for wordpress you can see that they suggest you to set up TLS using a reverse proxy like nginx and there are some additional things to set up.

In the entrypoint script for Wordpress (link here), if a folder already has content, nothing new gets written in. I'm not 100% sure that this would work, but you could try:

Additional note, look an the official WordPress dockerfile. https://github.com/docker-library/wordpress/blob/97f75b51f909fbd9894d128ea6893120cfd23979/latest/php7.4/apache/Dockerfile At the bottom you are a entrypoint and a CMD. I believe it runs "$entrypoint $CMD" when started with no arguments. Your can charge these, or best to leave alone. You just need to docker run your new built container.

Which one is it here: https://github.com/docker-library/wordpress/tree/master/latest

https://github.com/docker-library/wordpress/blob/master/docker-entrypoint.sh#L71

wordpress | WARNING: environment variable "WORDPRESS_CONFIG_EXTRA" is set, but "wp-config.php" already exists wordpress | The contents of this variable will _not_ be inserted into the existing "wp-config.php" file. wordpress | (see https://github.com/docker-library/wordpress/issues/333 for more details) w ```

WordPress already provides a docker image which can be used for development, but it has a few problems that are not dealt with in the usual docker way. We never really found a configurable solution to these problems, which always meant using the docker image requiring some repeated “must know” steps for everything the containers need to be built. Or reverting to using developer machines local php/apache/mysql or another dev environment tool.

Solutions are many, and could include Docker Compose, VS Code dev containers, Telepresence, Localstack or setting up temporary AWS accounts as a development environment for serverless applications.

Using Docker Compose to run Postgres and any third-party services locally provides a streamlined and consistent development environment. Developers can define services in a docker-compose.yml file, which enables them to configure and launch an entire stack with a single command. In this case, Postgres is encapsulated within a container with predefined configurations. Docker Compose also facilitates easy scaling, updates, and isolation of services, enhancing development efficiency and reducing the setup time for new team members or transitioning between projects. It encapsulates complex configurations, such as Postgres' performance monitoring and logging settings, in a manageable, version-controlled file, simplifying and replicating the service setup across different environments.

“Compose simplifies the control of your entire application stack, making it easy to manage services, networks, and volumes in a single, comprehensible YAML configuration file. Then, with a single command, you create and start all the services from your configuration file.” - Docker documentation

curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh # Install docker compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Apply executable permissions to the binary sudo chmod +x /usr/local/bin/docker-compose # Run Project docker-compose up -d

Docker,

This foundation now opens the door to even more powerful concepts. You can explore more advanced concepts such as container networking, streamlining the management of complex applications with Docker Compose, and how to make your application data persistent using volumes.

In many projects that are containerized, especially in cases where development is also done locally with docker-compose, teams often have two Dockerfiles, 1 for Development, the other for Production. If you happen to have multiple environments like pre-prod, staging and so on, some teams could have different Dockerfiles for these environments.

sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose