In addition, the volumes parameter under wordpress is what tells Docker to surface the wp-content directory in the local file system. So we now have persistent storage for parts of our WordPress site, such as the wp-content directory. The wp-content contains all user-supplied content. So basically, anything you can upload to your site ends up here. However, as long as you have both the database and your wp-content folder, you can always get your site back, even if everything else was lost. Now you are ready to run the Docker command to build your local environment. Run the following command: sudo docker-compose up -d Make sure you are still in the wordpress directory. The WordPress installation with a MySQL container and a WordPress container has been successful. Let me now explain why we made the contents of the wp-content directory permanent, i.e., available outside of the Docker container. When you install new themes or upload media files like images to your WordPress installation, they are saved in directories under the wp-content directory.īecause, as previously stated, containers do not retain the information stored in them after a restart, these files would be lost if the Docker container is relaunched. LINK TO SPECIFIC NODE IN DOCEAR FROM A DOCUMENT WORD INSTALL This is something we would never want to happen. So, by moving the wp-content directory out of the Docker container, we ensure that the files contained within it will remain accessible once the container is restarted. LINK TO SPECIFIC NODE IN DOCEAR FROM A DOCUMENT WORD INSTALL.LINK TO SPECIFIC NODE IN DOCEAR FROM A DOCUMENT WORD HOW TO.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |