add images to docs

gigalixir · Apr 30, 2017 · 2e0f1de · 2e0f1de
1 parent 6686026
commit 2e0f1de
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 1 deletion.
diff --git a/docs/source/config.png b/docs/source/config.png
diff --git a/docs/source/deploy.png b/docs/source/deploy.png
diff --git a/docs/source/main.rst b/docs/source/main.rst
@@ -186,7 +186,8 @@ How Does GIGALIXIR Work?
 
 We use Kubernetes and Docker to run your apps. We use a git server with pre-receive hooks to build your apps. We use Google Cloud Storage to store your compiled app tarball, also called a slug. We built an API server which orchestrates everything together. 
 
-TODO: insert diagram of components
+.. image:: deploy.png
+.. image:: config.png
 
 Components
 ----------
@@ -300,6 +301,8 @@ Frequently Asked Questions
 
   - *How is GIGALIXIR different from Heroku and Deis Workflow?*
 
+    .. image:: venn.png
+
     Heroku is a really great platform to run you Elixir apps and much of GIGALIXIR was designed based on their excellent `twelve-factor methodology`_. Heroku made design decisions that prioritize simplicity and they make it difficult to shoot yourself in the foot. As a consequence, it is difficult to run Elixir and Phoenix on Heroku unless you are willing to sacrifice many of the greatest advantages Elixir and Phoenix provide like node clustering, hot upgrades, and remote observer.
 
     Deis Workflow is also really great platform and is very similar to Heroku, except you run it your own infrastructure. Because Deis is open source and runs on Kubernetes, you could conceivably make modifications to support node clustering and remote observer, but hot upgrades would require some fundamental changes to the way Deis was designed to work. Even if all this was possible, you'd still have to spend quite a bit of timing solving problems that GIGALIXIR has already figured out for you.

diff --git a/docs/source/venn.png b/docs/source/venn.png