57cbaa3571
Run update.sh
2018-02-22 21:09:04 +00:00
f8dd523e54
Run update.sh
2018-02-17 20:09:24 +00:00
656f79ef88
Run update.sh
2018-02-13 00:09:33 +00:00
c00c79cbee
Run update.sh
2018-01-24 23:09:01 +00:00
b78d49c9df
Run update.sh
2018-01-04 22:08:53 +00:00
e037d3629e
Run update.sh
2017-12-08 19:09:07 +00:00
a3d47ab9e5
Run update.sh
2017-11-03 23:32:10 +00:00
40230cffa9
Run update.sh
2017-11-02 20:31:33 +00:00
080302fb47
Run update.sh
2017-11-02 09:32:04 -07:00
6b394db53e
Run update.sh
2017-10-09 23:29:46 +00:00
25a5b70c1b
Adjust a ton of image references (especially to use %%IMAGE%%)
2017-10-09 15:30:46 -07:00
1bbd985fca
Run update.sh
2017-10-05 19:31:43 +00:00
959ade0b5a
Run update.sh
2017-10-02 20:31:46 +00:00
7318870c71
Run update.sh
2017-09-27 04:31:50 +00:00
6a0efa1c72
Run update.sh
2017-09-26 00:31:57 +00:00
8a5dcb7df2
Run update.sh
2017-09-21 17:31:42 +00:00
91d1ac6979
Run update.sh
2017-09-07 00:32:08 +00:00
2988934d73
Run update.sh
2017-09-05 23:31:52 +00:00
9ec69468c4
Run update.sh
2017-08-21 18:31:41 +00:00
d2090f0e68
Run update.sh
2017-08-04 21:36:19 +00:00
41a2306529
Run update.sh
2017-08-03 22:32:42 +00:00
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
Docker Library Bot