ae9e2bf435
Run update.sh
2017-07-06 17:32:07 +00:00
10d67fd29f
Run update.sh
2017-06-22 18:32:00 +00:00
27a8c10dac
Run update.sh
2017-06-21 21:31:54 +00:00
54359bd26c
Migrate current compose examples to PWD capable stacks
2017-06-18 16:49:26 -03:00
7341cb67f1
Run update.sh
2017-06-12 21:32:00 +00:00
09e3a51b05
Run update.sh
2017-06-08 22:31:58 +00:00
46f3bd3985
Run update.sh
2017-05-05 13:34:07 -07:00
59a159ff4e
Run update.sh
2017-04-24 09:42:03 -07:00
7edf26875d
Run update.sh
2017-04-21 18:34:24 -07:00
0c2b9dcce8
Refactor the way information (especially links) are presented
...
This should make it much faster to find the right place to file issues, get help, find out whether upstream maintains an image, etc.
I've done my best to represent each `REPO/maintainer.md` file appropriately, but I might have missed some (or there might be something else a maintainer prefers be listed there, either more or less descriptive, for example), which would be welcome contributions following this change.
2017-04-21 17:48:19 -07:00
7d03e2198f
Run update.sh
2017-04-21 11:33:09 -07:00
ee2cd5b8cc
Fix some spacing
2017-04-21 10:14:37 -04:00
2c3e64bc03
Fix some text
2017-04-21 10:10:33 -04:00
f99e61c7dd
Explain who maintains this image
...
We either need to explain that this is maintained by the Docker community or pull the image from docker. We are getting push back on our side about this.
2017-04-21 09:55:16 -04:00
1e87dc1ca4
Run update.sh
2017-04-07 12:32:44 -07:00
c1400b5a52
Run update.sh
2017-04-06 14:32:43 -07:00
1c6e03cdac
Run update.sh
2017-04-05 19:35:02 -07:00
b4b9dd5f8f
Run update.sh
2017-03-28 07:34:30 -07:00
d566be179e
Run update.sh
2017-03-16 11:32:46 -07:00
0b653185b6
Run update.sh
2017-03-10 14:14:39 -08:00
f5bae378d3
Run update.sh
2017-03-02 17:32:49 -08:00
87d8ff4491
Run update.sh
2017-03-01 16:33:41 -08:00
28b8ec5636
Run update.sh
2017-02-17 11:32:44 -08:00
1b95db417d
Run update.sh
2017-02-08 11:33:57 -08:00
aad584904d
Run update.sh
2017-02-07 12:32:41 -08:00
cba12bf8ef
Run update.sh
2017-02-06 10:32:34 -08:00
b80927f8c4
Run update.sh
2017-01-25 16:33:13 -08:00
7f751b9041
Add some notes about volumes in Drupal, especially updating "docker-compose.yml"
...
I tested this by using `docker-compose up -d`, going through Drupal's web-based setup process to get Drupal fully configured and operational, then used `docker-compose up -d --force-recreate` to force both containers to be re-created (which works very hard to keep the volumes), and verified that my site was still configured and working properly.
2017-01-25 15:26:01 -08:00
03f25b13dc
Run update.sh
2017-01-18 12:33:36 -08:00
2bc140abb0
Run update.sh
2017-01-11 10:33:55 -08:00
a588bd14a5
Run update.sh
2017-01-06 16:45:33 -08:00
901e0dfcaf
Add an initial docker-compose.yml for drupal
2017-01-06 15:22:37 -08:00
67dd40d846
Run update.sh
2017-01-04 13:34:06 -08:00
399b98d1cf
Run update.sh
2016-12-16 03:32:57 -08:00
e78efab82b
Run update.sh
2016-12-13 02:32:56 -08:00
48abe94b6d
Run update.sh
2016-12-09 10:33:06 -08:00
47cc57b767
Run update.sh
2016-12-08 13:52:55 -08:00
f7fdbadff5
Run update.sh
2016-11-17 13:33:12 -08:00
840faf21b0
Run update.sh
2016-11-08 11:33:04 -08:00
c6445a12d7
Run update.sh
2016-10-27 15:32:55 -07:00
b4d17bce7d
Run update.sh
2016-10-14 11:32:52 -07:00
98598b4e35
Run update.sh
2016-10-14 10:38:03 -07:00
2718d75d1d
Run update.sh
2016-10-12 09:32:55 -07:00
297901ae56
Run update.sh
2016-10-06 12:32:47 -07:00
e2f0767cc4
Run update.sh
2016-10-05 12:32:51 -07:00
b75010921d
Run update.sh
2016-09-23 16:32:33 -07:00
c8529c9eb7
Run update.sh
2016-09-21 16:32:52 -07:00
7b23d551df
Run update.sh
2016-09-08 10:53:52 -07:00
9e402b81e0
Run update.sh
2016-08-31 10:01:56 -07:00
3458061fb1
Run update.sh
2016-08-26 16:01:58 -07:00
Docker Library Bot