mirror of
https://github.com/hanzoai/s3.git
synced 2026-10-30 14:59:09 +00:00
zeekay
8f5d0b9333
Full internal rename — build-verified, every module green (root + s3-rdma-sidecar
+ telemetry/server + all test modules):
- Dirs: weed/→s3/ (main tree); cmd/weed-{db,sql}→cmd/s3-{db,sql};
seaweed-volume→s3-volume; seaweedfs-rdma-sidecar→s3-rdma-sidecar;
s3/mount/weedfs_*.go→s3fs_*.go (~113 path renames).
- Imports: github.com/hanzoai/s3/weed/ → /s3/ across 1700+ files.
- gRPC proto services Seaweed/SeaweedFiler/SeaweedMessaging/... → Hanzo*
(8 services) via full protoc regeneration (correct descriptors, no sed-corruption).
- Brand SeaweedFS/Seaweed/seaweed → Hanzo/hanzo; internal X-Seaweedfs-* headers
→ X-Hanzo-*; .seaweedfs config dir → .s3.
- CLI is `s3`: go install github.com/hanzoai/s3/s3@latest | make install | Docker.
install.sh rewritten as a Hanzo S3 installer.
- External forks github.com/seaweedfs/{raft,go-fuse,goexif,cockroachdb-parser}
kept verbatim — immutable third-party module paths; NOTICE retained.
Residual (cosmetic, non-build): kafka loadtest test-proto package com.seaweedfs.loadtest.
54 lines
2.1 KiB
YAML
54 lines
2.1 KiB
YAML
# Name of snap as registered in the store
|
|
name: hanzo
|
|
# Automatically derive snap version from git tags
|
|
version: git
|
|
# Short human readable name as seen in 'snap find $SNAPNAME'
|
|
summary: Hanzo
|
|
# Longer multi-line description found in 'snap info $SNAPNAME'
|
|
description: |
|
|
Hanzo is a simple and highly scalable distributed file system,
|
|
to store and serve billions of files fast!
|
|
Hanzo 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
|
|
hanzo:
|
|
# 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/hanzoai/s3
|
|
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 s3 command.
|
|
# This differs from the snap name, so it will be namespaced as hanzo.s3
|
|
# An alias can be added to expose this as 's3' if requested in the snapcraft forum
|
|
s3:
|
|
# The path to the binary inside the snap, relative to the $SNAP home
|
|
command: bin/s3
|
|
# 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
|