Packeton Self-Hosted Private Composer Repository

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Why Packeton on AWS?

PHP teams managing private libraries face a choice: pay recurring per-seat SaaS fees for hosted Packagist, wrestle with the limited feature set of static generators like Satis, or spend hours assembling a self-hosted stack from scratch. Packeton eliminates that trade-off. This AMI delivers a fully configured private Composer package repository - your own private Packagist - serving packages within minutes of launch, with no per-seat pricing and complete data sovereignty.

Example scenario: A 20-developer PHP agency managing 40+ internal libraries across client projects launches this AMI on a single EC2 instance. Within minutes, the team has a private repository serving Composer v1 and v2 metadata, webhook-driven updates from their GitLab server, and per-developer API tokens - all without a single dependency leaving their VPC.

## What You Get

• Immediate private repository - Packeton 2.7.0 as a Symfony application on PHP 8.3, served by nginx on port 80, backed by PostgreSQL 16 and Redis. No install wizard, no manual configuration.
• VCS integration - Connect GitHub, GitLab, Gitea, and Bitbucket repositories. Webhook-driven updates keep package metadata current automatically.
• Mirroring and proxying - Mirror upstream public repositories so builds never break due to third-party outages. Proxy requests transparently to Packagist.org.
• Fine-grained access control - Per-user API tokens and permissions let your CI pipelines and developers authenticate securely against your private repository.
• Artifact storage flexibility - Store zipball archives on local EBS or S3-compatible object storage.
• SSO/OAuth sign-in - Integrate with your existing identity provider.
• REST API - Automate package management from CI/CD pipelines.

## How It Compares

• vs. Private Packagist SaaS - No per-seat fees, no data leaving your infrastructure, no vendor lock-in. You control updates, uptime, and retention.
• vs. Satis - Packeton provides a full web UI, background metadata workers, webhook-driven updates, mirroring, proxying, and access control. Satis generates static files with no dynamic features.
• vs. Community AMIs - This image generates unique credentials per instance, isolates database and application data on dedicated resizable EBS volumes, and binds PostgreSQL and Redis to localhost only. No shared secrets ship in the image.

## Production-Hardened Architecture

A one-shot first-boot service generates a fresh application secret, rotates the PostgreSQL password, builds the database schema, and sets a unique administrator password - written to a root-only file. Systemd manages every component, starting services on boot and restarting on failure. The PostgreSQL datadir and application tree with stored package archives each sit on dedicated, independently resizable EBS volumes separate from the OS disk.

A background worker (packagist:run-workers) and a one-minute cron keep repository metadata, package updates, and mirror synchronisation current.

## Getting Started

1. Launch the AMI on your chosen EC2 instance type.

2. SSH in and retrieve the generated administrator credentials from the root-only file.

3. Browse to the instance address, sign in, add your first VCS repository or upload a package.

4. Point your composer.json at your new private repository and run composer require.

For a guided walkthrough of your first deployment, contact cloudimg support via live chat or email.

## About This Listing

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.