CHANGELOG: note which commands the offline flag doesn't yet support
License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
Steven Allen committed
Feb 18, 2019 at 14:07 UTC
e043d515dd690508df31f724cb1f983b7710ab82
1 file changed
+6
-3
CHANGELOG.md
+6
-3
@@ -18,10 +18,10 @@ TODO: WRITE THIS
18
There are two new "offline" features in this release: a global `--offline` flag
19
and an option to configure the gateway to not fetch files.
20
21
-All go-ipfs commands now support the `--offline` flag. This causes IPFS to avoid
21
+Most go-ipfs commands now support the `--offline` flag. This causes IPFS to avoid
22
network operations when performing the requested operation. If you've ever used
23
-the `--local` flag, the `--offline` flag is the universally supported
24
-replacement (it works everywhere).
23
+the `--local` flag, the `--offline` flag is the (almost) universally supported
24
+replacement.
25
26
For example:
27
@@ -32,6 +32,9 @@ For example:
32
* `ipfs block stat --offline Qm...` is a great way to tell if a block is locally
33
available.
34
35
+Note: It doesn't _yet_ work with the `refs`, `urlstore`, or `tar` commands
36
+([#6002](https://github.com/ipfs/go-ipfs/issues/6002)).
37
+
38
On to the gateway, there's a new `Gateway.NoFetch` option to configure the
39
gateway to only serve locally present files. This makes it possible to run an
40
IPFS node as a gateway to serve content of _your_ choosing without acting like a