russellmacshane/quick-wordpress

Quick WordPress Installation using Docker

Quick WordPress

Quick WordPress Installation using Docker

The goal of this project is to create a quick virtual machine setup with a WordPress installation for testing purposes. The following technologies are automatically installed for you:

• Ubuntu
• Apache
• MariaDB
• PHP
• phpMyAdmin
• WPCli
• WordPress

Pre-Installation

1. Install Docker
2. Install Docker Compose

Installation Instructions

1. Find a directory on your computer that you'd like to install this repo
2. $ git clone [email protected]:russellmacshane/quick-wordpress.git or git clone https://github.com/russellmacshane/quick-wordpress.git if you don't have your ssh keys setup
3. $ cd quick-wordpress
4. Your are strongly encouraged to modify the default passwords and WordPress setup information in the config file
5. $ docker-compose up -d
6. Grab some ☕️ coffee, it'll take a bit to install all the necessary dependencies

Usage

1. Make sure the container is up and running with $ docker-compose ps
2. Point your web browser over to http://localhost/ to view your WordPress site
3. You can also get to phpMyAdmin by going to http://localhost/phpmyadmin/
4. If you'd like to login into the container - $ docker-compose exec qwp /bin/bash
5. WordPress files are located in /var/www/html and you can run WPCli commands from there
6. This repo is mirrored from your local machine over to /home/docker/quick-wordpress on your container

Backup and Restores

1. In order to do backup and restores:
2. $ docker-compose exec qwp qwcli backup and follow the on screen instructions
3. If you'd like to restore from a previous backup - $ docker-compose exec qwp qwcli restore and follow the on screen instructions

Start and Stopping

1. $ docker-compose stop to stop the container
2. $ docker-compose start to bring it back up again

Cleanup

1. If you are ready to delete your WordPress Container - $ docker-compose down

quick-wordpress's Issues

Installation is failing

The installation hangs with this output:

    default: Preparing to unpack .../libsqlite3-0_3.22.0-1ubuntu0.1_amd64.deb ...
    default: Unpacking libsqlite3-0:amd64 (3.22.0-1ubuntu0.1) over (3.22.0-1) ...
    default: Preparing to unpack .../libpython3.6-stdlib_3.6.8-1~18.04.3_amd64.deb ...
    default: Package configuration┌──────────────────────┤ Configuring libssl1.1:amd64 ├──────────────────────┐│││ There are services installed on your system which need to be restarted    ││ when certain libraries, such as libpam, libc, and libssl, are upgraded.   ││ Since these restarts may cause interruptions of service for the system,   ││ you will normally be prompted on each upgrade for the list of services    ││ you wish to restart.  You can choose this option to avoid being││ prompted; instead, all necessary restarts will be done for you││ automatically so you can avoid being asked questions on each library││ upgrade.││││ Restart services during package upgrades without asking?││││<Yes><No>│││└───────────────────────────────────────────────────────────────────────────┘
    default: Checking for services that may need to be restarted...
    default: done.
    default: Checking init scripts...
    default: ```

Seems to be an issue with the Debian noninteractive env variable on the `apt-get upgrade` step

Convert Vagrant/Virtualbox setup to Docker

Currently, quick-wordpress uses Vagrant/Virtualbox. As a hacktoberfest challenge, convert this to use Docker!!