Simple enough. Finally, this is all tied together with a file called fig.yml. It describes the services that our app comprises of (a web server and database), what Docker images they use, how they link together, what volumes will be mounted inside the containers and what ports they expose.
db:
image: orchardup/postgresql
- ports:
- - "5432"
web:
build: .
command: python manage.py runserver 0.0.0.0:8000
diff --git a/env.html b/env.html
index 9cce65fb..215f2977 100644
--- a/env.html
+++ b/env.html
@@ -6,7 +6,7 @@
-
+
diff --git a/index.html b/index.html
index fa0df7a8..259287f7 100644
--- a/index.html
+++ b/index.html
@@ -6,7 +6,7 @@
-
+
diff --git a/install.html b/install.html
index 5369838b..45c3c49f 100644
--- a/install.html
+++ b/install.html
@@ -6,7 +6,7 @@
-
+
@@ -27,11 +27,11 @@ $ docker-osx shell
Docker has guides for Ubuntu and other platforms in their documentation.
Next, install Fig. On OS X:
-$ curl -L https://github.com/orchardup/fig/releases/download/0.3.1/darwin > /usr/local/bin/fig
+$ curl -L https://github.com/orchardup/fig/releases/download/0.3.2/darwin > /usr/local/bin/fig
$ chmod +x /usr/local/bin/fig
On 64-bit Linux:
-$ curl -L https://github.com/orchardup/fig/releases/download/0.3.1/linux > /usr/local/bin/fig
+$ curl -L https://github.com/orchardup/fig/releases/download/0.3.2/linux > /usr/local/bin/fig
$ chmod +x /usr/local/bin/fig
Fig is also available as a Python package if you're on another platform (or if you prefer that sort of thing):
diff --git a/rails.html b/rails.html
index a32ca23b..b276422b 100644
--- a/rails.html
+++ b/rails.html
@@ -6,7 +6,7 @@
-
+
diff --git a/wordpress.html b/wordpress.html
index 1492d698..c679abf8 100644
--- a/wordpress.html
+++ b/wordpress.html
@@ -6,7 +6,7 @@
-
+
@@ -40,8 +40,6 @@ ADD . /code
- .:/code
db:
image: orchardup/mysql
- ports:
- - "3306:3306"
environment:
MYSQL_DATABASE: wordpress
diff --git a/yml.html b/yml.html
index e0e6b01e..5a964cea 100644
--- a/yml.html
+++ b/yml.html
@@ -6,7 +6,7 @@
-
+
@@ -55,6 +55,12 @@
- "8000:8000"
- "49100:22"
+-- Expose ports without publishing them to the host machine - they'll only be
+-- accessible to linked services. Only the internal port can be specified.
+expose:
+ - "3000"
+ - "8000"
+
-- Map volumes from the host machine (HOST:CONTAINER).
volumes:
- cache/:/tmp/cache