mirror of
https://github.com/hanzoai/s3.git
synced 2026-11-03 03:07:41 +00:00
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.
- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
"Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
(replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
keep their upstream import paths with zero churn. Internal identifiers and
import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
help/usage/flag strings, shell autocomplete program name, and the product name
in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
(e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
`cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
updated to ignore the `s3` build output.
54 lines
2.1 KiB
YAML
54 lines
2.1 KiB
YAML
# Name of snap as registered in the store
|
|
name: seaweedfs
|
|
# Automatically derive snap version from git tags
|
|
version: git
|
|
# Short human readable name as seen in 'snap find $SNAPNAME'
|
|
summary: SeaweedFS
|
|
# Longer multi-line description found in 'snap info $SNAPNAME'
|
|
description: |
|
|
SeaweedFS is a simple and highly scalable distributed file system,
|
|
to store and serve billions of files fast!
|
|
SeaweedFS implements an object store with O(1) disk seek,
|
|
transparent cloud integration, and an optional Filer with POSIX interface,
|
|
supporting S3 API, Rack-Aware Erasure Coding for warm storage,
|
|
FUSE mount, Hadoop compatible, WebDAV.
|
|
|
|
# Grade is stable for snaps expected to land in the stable channel
|
|
grade: stable
|
|
# Uses the strict confinement model and uses interfaces to open up access to
|
|
# resources on the target host
|
|
confinement: strict
|
|
|
|
# List of parts which comprise the snap
|
|
parts:
|
|
# The main part which defines how to build the application in the snap
|
|
seaweedfs:
|
|
# This part needs a newer version of golang, so we use a separate part
|
|
# which defines how to get a newer golang during the build
|
|
after: [go]
|
|
# The go plugin knows how to build go applications into a snap
|
|
plugin: go
|
|
# Snapcraft will look in this location for the source of the application
|
|
source: .
|
|
go-importpath: github.com/seaweedfs/seaweedfs
|
|
go:
|
|
# Defines the version of golang which will be bootstrapped into the snap
|
|
source-tag: go1.14
|
|
|
|
# Apps exposes the binaries inside the snap to the host system once installed
|
|
apps:
|
|
# We expose the weed command.
|
|
# This differs from the snap name, so it will be namespaced as seaweedfs.weed
|
|
# An alias can be added to expose this as 'weed' if requested in the snapcraft forum
|
|
weed:
|
|
# The path to the binary inside the snap, relative to the $SNAP home
|
|
command: bin/weed
|
|
# Plugs connect the snap to resources on the host system. We enable network connectivity
|
|
# We also add home and removable-media (latter not autoconnected by default)
|
|
# so users can access files in their home or on removable disks
|
|
plugs:
|
|
- network
|
|
- network-bind
|
|
- home
|
|
- removable-media
|