drdogbot7 / docker-wordmove Goto Github PK

Docker image to run Wordmove.

• openssh-server
• curl
• rsync
• mysql-client
• php
• wordmove
• wp-cli
• lftp
• ruby

Additionally we install build-essential and ruby-dev in order to be able to compile gems inside the image, thus enabling it to be used as CI image in certain scenarios.

This is an updated version of weilaka/docker-wordmove with the following updates.

• update php version to 8.2
• change workpath from /html to /var/www/html
• install ed25519 and bcrypt_pbkdf for compatability with ed25519 ssh keys

docker run -it --rm -v ~/.ssh:/root/.ssh:ro drdogbot7/wordmove

This starts a shell, with wordmove available on the command-line.

If you are on a Winodws or Linux host, then you could get permission errors while trying to use your ssh keys. To work around this problem we've a trick for you:

docker run -it --rm -v ~/.ssh:/tmp/.ssh:ro drdogbot7/wordmove

Mounting .ssh/ inside /tmp/ will tell the image to automatically copy it over in /root/ and to fix permissions.

A WORDMOVE_WORKDIR environment variable is exported inside the container; since this is the container's WORKDIR path, you could use <%= ENV['WORDMOVE_WORKDIR'] %> inside a movefile.yml in order to solidly know the pwd.

For example running

docker run --rm -v ~/.ssh:/root/.ssh:ro -v ~/dev/wp-site/:/html drdogbot7/wordmove wordmove pull -d

you could configure movefile.yml like

local:
  wordpress_path: "<%= ENV['WORDMOVE_WORKDIR'] %>"
  # [...]

See Wordpress development made easy using Docker

This tutorial explains how to set up a WordPress environment, using Docker Compose, with the following four interconnected containers:

• database
• wordpress
• phpmyadmin
• wordmove

Don't forget to replace image: mfuezesi/wordmove with image: drdogbot7/wordmove to get the latest version of Wordmove.

Based on nilsglow/docker-wordmove based on welaika/docker-wordmove based on mfuezesi/docker-wordmove.

@drdogbot7 😽