chore: enable snap home interface
Without the home interface the user is unable to add files to ipfs from their home dir. Also explicitly sets the build architectures, to skip some esoteric ones and save some cpu cycles. License: MIT Signed-off-by: Oli Evans <oli@tableflip.io>
Oli Evans committed
Jul 10, 2020 at 16:30 UTC
ba0b4154083032d243115f8e2e67317f184cab53
1 file changed
+6
-2
snap/snapcraft.yaml
+6
-2
@@ -1,5 +1,4 @@
1
# This snap will build go-ipfs from source.
2
-# See: https://github.com/ipfs-shipyard/ipfs-snap for more details
2
name: ipfs
3
summary: global, versioned, peer-to-peer filesystem # 79 char long summary
4
description: |
@@ -15,10 +14,15 @@ base: core18
14
grade: stable
15
confinement: strict
16
17
+# skip building on `ppc64el` and `s390x` to save some cpu cycles.
18
+architectures:
19
+ - build-on: [amd64, arm64, armhf, i386]
20
+
21
apps:
22
ipfs:
23
command: ipfs
21
- plugs: [network, network-bind, removable-media]
24
+ # the home plug is included so the user can `ipfs add` files from their home dir without a permission error.
25
+ plugs: [home, network, network-bind, removable-media]
26
environment:
27
# Snaps versions are isolated by default. This keeps the same ipfs repo across upgrades.
28
IPFS_PATH: "$SNAP_USER_COMMON"