Skip to content
brutassePublic

About

A private, stateless Maven repository on top of S3-compatible object storage.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

pier

Pier

A private, stateless Maven repository on top of S3-compatible object storage. One Go binary, no database, no user accounts.

  • Every request carries an OIDC token. Pier authorizes the request only after it verifies the token against the configured issuers — no deploy tokens, no shared secrets. GitHub Actions OIDC (trusted publishing) is one example of a source; so is any IdP you configure (Authentik, Keycloak, ...).
  • Authorization uses a list of CEL rules. Pier evaluates the rules per request against the verified token claims, the Maven coordinates of the path, and the action (download / upload / delete). The token source does not decide; the rules do.
  • Optional pull-through cache: Pier caches public or basic-authenticated upstreams (Maven Central, Clojars, ...) on demand, revalidates metadata with a TTL, and synthesizes metadata for private groups.
  • Stateless: all state lives in S3; the binary hot-reloads its configuration on SIGHUP.
flowchart LR
  GHA["GitHub Actions"] -- "OIDC token" --> P[pier]
  IdP["IdP (SSO, ...)"] -- "OIDC token" --> P
  P --> S3[("S3-compatible object storage")]
  P -- "per request" --> CEL["CEL policy"]
Loading

Documentation

The full documentation lives at https://brutasse.github.io/pier/: quickstart, publishing from GitHub Actions, downloading, pull-through cache, oidc-cli, policy rules, configuration, operations, development.

Quickstart

Install the binary (Linux x86_64/arm64; always the latest release):

curl -fsSL https://raw.githubusercontent.com/brutasse/pier/v0.1.2/install.sh | sh

Or pull the Docker image (multi-arch; always the latest release):

docker pull ghcr.io/brutasse/pier:v0.1.2

Fetch a config, edit it, and run it:

curl -fsSL https://raw.githubusercontent.com/brutasse/pier/main/configs/example.yaml -o pier.yaml
# edit pier.yaml, then:
pier serve --config pier.yaml

Observability endpoints are opt-in: set metrics_port: 9090 for Prometheus and/or pprof_port: 9091 for profiling in the config (operations).

Pier also reads the config path from the PIER_CONFIG environment variable when you omit --config.

docker run -p 8080:8080 -v $(pwd)/pier.yaml:/config/pier.yaml ghcr.io/brutasse/pier:v0.1.2

S3 credentials are never in the config file: the standard AWS SDK credential chain applies (environment variables, shared credentials file, instance profile). See configs/example.yaml for a fully commented example.

Development

make test               # unit tests, no network
make build              # -> bin/pier
make test-integration   # e2e: needs PIER_TEST_S3_ENDPOINT (S3Mock/rclone serve s3)

About

A private, stateless Maven repository on top of S3-compatible object storage.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages