snapcraft.yaml 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. # Name of snap as registered in the store
  2. name: seaweedfs
  3. # Automatically derive snap version from git tags
  4. version: git
  5. # Short human readable name as seen in 'snap find $SNAPNAME'
  6. summary: SeaweedFS
  7. # Longer multi-line description found in 'snap info $SNAPNAME'
  8. description: |
  9. SeaweedFS is a simple and highly scalable distributed file system,
  10. to store and serve billions of files fast!
  11. SeaweedFS implements an object store with O(1) disk seek,
  12. transparent cloud integration, and an optional Filer with POSIX interface,
  13. supporting S3 API, Rack-Aware Erasure Coding for warm storage,
  14. FUSE mount, Hadoop compatible, WebDAV.
  15. # Grade is stable for snaps expected to land in the stable channel
  16. grade: stable
  17. # Uses the strict confinement model and uses interfaces to open up access to
  18. # resources on the target host
  19. confinement: strict
  20. # List of parts which comprise the snap
  21. parts:
  22. # The main part which defines how to build the application in the snap
  23. seaweedfs:
  24. # This part needs a newer version of golang, so we use a separate part
  25. # which defines how to get a newer golang during the build
  26. after: [go]
  27. # The go plugin knows how to build go applications into a snap
  28. plugin: go
  29. # Snapcraft will look in this location for the source of the application
  30. source: .
  31. go-importpath: github.com/chrislusf/seaweedfs
  32. go:
  33. # Defines the version of golang which will be bootstrapped into the snap
  34. source-tag: go1.14
  35. # Apps exposes the binaries inside the snap to the host system once installed
  36. apps:
  37. # We expose the weed command.
  38. # This differs from the snap name, so it will be namespaced as seaweedfs.weed
  39. # An alias can be added to expose this as 'weed' if requested in the snapcraft forum
  40. weed:
  41. # The path to the binary inside the snap, relative to the $SNAP home
  42. command: bin/weed
  43. # Plugs connect the snap to resources on the host system. We enable network connectivity
  44. # We also add home and removable-media (latter not autoconnected by default)
  45. # so users can access files in their home or on removable disks
  46. plugs:
  47. - network
  48. - network-bind
  49. - home
  50. - removable-media