Add Specifying The Digest Directory as a phoenix til

README.md

@@ -10,7 +10,7 @@ smart people at [Hashrocket](http://hashrocket.com/).
 For a steady stream of TILs from a variety of rocketeers, checkout
 [til.hashrocket.com](https://til.hashrocket.com/).
 
-_556 TILs and counting..._
+_557 TILs and counting..._
 
 ---
 
@@ -252,6 +252,7 @@ _556 TILs and counting..._
 - [Bypass Template Rendering](phoenix/bypass-template-rendering.md)
 - [Check The Installed Version](phoenix/check-the-installed-version.md)
 - [Render A Template To A String](phoenix/render-a-template-to-a-string.md)
+- [Specifying The Digest Directory](phoenix/specifying-the-digest-directory.md)
 - [Specifying The Server Port](phoenix/specifying-the-server-port.md)
 
 ### PostgreSQL

phoenix/specifying-the-digest-directory.md

@@ -0,0 +1,19 @@
+# Specifying The Digest Directory
+
+By default, Phoenix targets `priv/static` when preparing digested assets for
+production. This process happens when running `mix phx.digest`.
+
+If you are doing some custom work with your assets such that they are in a
+different location, you'll need to tell Phoenix where to look. To do this,
+just include an optional path argument.
+
+```bash
+$ mix phx.digest path/to/my/assets
+```
+
+The digests will be put in that target directory. If you'd like to specify a
+different output directory, such as `priv/static`, include the `-o` flag.
+
+```bash
+$ mix phx.digest path/to/my/assets -o priv/static
+```