You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,19 +21,19 @@ Please read through the [project documentation](docs/README.md) for details abou
21
21
1. Run the local development environment:
22
22
23
23
```
24
-
docker-compose up -d
24
+
dockercompose up -d
25
25
```
26
26
27
-
(Wait for the environment to come up—you can monitor the logs with `docker-compose logs -f`).
27
+
(Wait for the environment to come up—you can monitor the logs with `dockercompose logs -f`).
28
28
29
29
1. Once the container is running, install Dependencies and install Drupal. You can either access http://localhost/ and install using the UI, or install via Drush:
30
30
31
31
```
32
32
# Install dependencies.
33
-
docker-compose exec drupal composer install
33
+
dockercompose exec drupal composer install
34
34
35
35
# Install Drupal.
36
-
docker-compose exec drupal bash -c 'drush site:install minimal --db-url="mysql://drupal:$DRUPAL_DATABASE_PASSWORD@$DRUPAL_DATABASE_HOST/drupal" --site-name="Drupal Example Site for Kubernetes" --existing-config -y'
36
+
dockercompose exec drupal bash -c 'drush site:install minimal --db-url="mysql://drupal:$DRUPAL_DATABASE_PASSWORD@$DRUPAL_DATABASE_HOST/drupal" --site-name="Drupal Example Site for Kubernetes" --existing-config -y'
37
37
```
38
38
39
39
1. Visit http://localhost/ in your browser, and login as `admin` using the password Drush printed in the 'Installation complete' message.
@@ -44,24 +44,24 @@ Please read through the [project documentation](docs/README.md) for details abou
44
44
45
45
After making any configuration changes on the website, you can export the configuration to disk so it can be preserved in the codebase and deployed to the production site:
For more on the way this project's configuration changes are handled, and the general site development process, see the [project documentation](docs/README.md).
50
50
51
51
### Exporting Content
52
52
53
53
After making any content changes on the website, you can export the changes to disk so it is preserved in the codebase and installable on the production site:
For more on the way this project's content changes are handled, see the [pidramble_default_content README](web/modules/custom/pidramble_default_content/README.md).
58
58
59
59
### Upgrading Core (and Contrib)
60
60
61
61
1. Set up the site like normal, make sure it's installed.
62
-
2. Run `docker-compose exec drupal composer update` (to update everything).
63
-
3. Run `docker-compose exec drupal bash -c 'drush updb -y'`
64
-
4. Run `docker-compose exec drupal bash -c 'drush config:export -y'`
62
+
2. Run `dockercompose exec drupal composer update` (to update everything).
63
+
3. Run `dockercompose exec drupal bash -c 'drush updb -y'`
64
+
4. Run `dockercompose exec drupal bash -c 'drush config:export -y'`
Copy file name to clipboardExpand all lines: docs/configure-and-reproduce.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,11 @@ For Drupal 8+, that means using _configuration_ to synchronize changes between a
6
6
7
7
Before we can start doing this work, we need to make sure we have our local environment set up to allow us to work in the Docker environment, but also have our codebase changes reflected locally (outside of the running Docker container), so we can commit any changes to our Git codebase.
8
8
9
-
## Local Development with `docker-compose`
9
+
## Local Development with `dockercompose`
10
10
11
11
The first step is to modify the `docker-compose.yml` file so it has a `volume` which shares the local codebase into the Drupal container:
12
12
13
-
1. If you already have the Docker environment running from the previous guide, make sure it is completely removed using `docker-compose down -v`.
13
+
1. If you already have the Docker environment running from the previous guide, make sure it is completely removed using `dockercompose down -v`.
14
14
1. Since we'll be using the local codebase to drive the Drupal site (instead of the Drupal codebase only available inside the Drupal container), we need to install Composer dependencies locally:
15
15
16
16
```
@@ -22,7 +22,7 @@ The first step is to modify the `docker-compose.yml` file so it has a `volume` w
22
22
1. Start the local development environment:
23
23
24
24
```
25
-
docker-compose up -d
25
+
dockercompose up -d
26
26
```
27
27
28
28
1. Install Drupal using the same Drush command used in the previous guide, [Starting a new Drupal Project](starting-new-project.md).
@@ -52,15 +52,15 @@ So let's do something I do for all my Drupal sites: install the [Admin Toolbar](
52
52
1. Now run the following command to tell Drupal to dump its current configuration into the 'config sync' directory:
1. If you look inside the `config/sync` folder you should now see lots of YAML files (ending with `.yml`), containing all the details of your Drupal site's configuration.
59
59
1. Now is where this gets interesting; let's say you then make some other changes to your site configuration, but you want to ditch them because you weren't happy with them. For example, go to the Basic site settings page (`/admin/config/system/site-information`) and change the Slogan to "The best website ever" and save it.
60
60
1. You can now _reinstall_ the site from scratch, but using the configuration you previously exported (so it will have the Admin Toolbar module and everything else, but not this silly slogan you don't like), by adding the flag `--existing-config` to the install command:
1. A minute or so later, if you log into the site using the `admin` user and the new password Drush prints to the command line, you'll see that the Slogan was reverted to being blank, as it was before you changed it.
Copy file name to clipboardExpand all lines: docs/create-default-content.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ Anyways, let's get started with Default Content:
49
49
1. Once you're satisfied things worked correctly, go ahead and export the site configuration so the Default Content module and your site's default content module are enabled:
1. Reinstall Drupal from scratch, and you _should_ see that not only is the Drupal site back the same way you had configured it, there are also entities that are recreated after an install which should be helpful for local development and theming.
0 commit comments