![]() ![]() Notice the web address is not in the local subnet. We see the logs of apache running in the terminal and if we click the red highlighted web preview area we get our backup opened in the default browser. We can restart apache if need be, run a drush registry rebuild, make a snapshot of the mysql database, enter the mysql CLI in the container, or open a shell at the site directory location to run additional drush commands in the container. We can make modifications to the makefile in our extracted directory and rebuild from it. Really for kitematic users the only part we care about this is the task menu portion. Now we are greeted with a fun interactive menu. ![]() The only real time you’d want to say no to this is if you’d like to run multiple backups at the same time and you don’t care about https. Here we want to start the container and normally we will say yes to binding on 80,443, and 3306 because this gives us https access to the site. Install and open kitematic from current version is 0.7.2Ĭd into the drupal_docker folder we checked out earlier it should look something like this:Īnd you’re all set to get this backup up and running by running start.sh. After downloading it put it in the drupal_docker folder. Grab your from central by clicking Export and then Get. Let’s just dive in and clone the docker new-backup branch git clone -b new-backup Follow the instructions on my first blog post about how to get docker set up ![]()
0 Comments
Leave a Reply. |