On the other hand, if part of what you're doing is scripted - then you probably just need to add a Drush alias so Drush is able to locate your installation when a command is run outside of webroot see but you haven't said how you're installing Drupal so I can't say for sure. Ideally, you should just make your own distribution profile and this would enable the theme for the user on site-install (and allow you to make all your customisations in one place). How to achieve what you desire very much depends on how you install Drupal after Docker has finished building? Ideally, you're doing this with an ENTRYPOINT script rather than manually - and if so, then after the install - enable the theme with Drush there. ![]() Now, I'm not familiar with the official Drupal Docker image but I'm sure it must be a simple PHP based container? The point being is that the last thing to happen is for PHP to actually be run, and until that point, MySQL is not running. Both of them use nodejs to abstract away most of the complexity of using docker-compose for WordPress development. The problem is that anything in the Dockerfile is part of the build process - which is used for creating an image that is finally run via CMD. Options For Docker-based Local Development From WordPress Core The WordPress open-source project has published two tools to simplify docker-based local development. In order to install a module in Drupal you need access to the database with a working installation. ![]() If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used: docker run -name some-drupal -p 8080:80 -d drupal. Let’s start by backing up the DocumentRoot for WordPress website: rootubuntu-wp-server: tar -czf wordpressback.tgz wordpress/. Installing modules with composer is very different from installing them in Drupal. The basic pattern for starting a drupal instance is: docker run -name some-drupal -d drupal. The out commented line after host > mysql is a previous attempt taken from another SO answer and illustrates the problem, drush use the command line server API which is different from whatever drupal uses. Before starting with the migration, we need to take backup of website files used by WordPress and the database used by WordPress.
0 Comments
Leave a Reply. |