Packeton

Prerequisites

You need an active Azure subscription, an SSH key pair, and a VNet and subnet in the target region.

Standard_B2s (2 vCPU / 4 GiB RAM) is a good starting size. Choose a larger size for bigger teams or heavy mirroring.

Configure the NSG to allow inbound 22/tcp from your management network and 80/tcp (HTTP) from your developers. Add 443/tcp if you enable HTTPS.

Step 1 - Deploy from the Azure Marketplace

Sign in to the Azure Portal, choose Create a resource, search the Marketplace for Packeton by SecureAnyCloud, and select Create.

On the Basics tab, pick your subscription, resource group, region and size. Under Administrator account, choose SSH public key and paste your key. Under Inbound port rules, allow SSH (22) and HTTP (80).

Then select Review + create and Create.

Step 2 - Deploy from the Azure CLI

# Accept the Marketplace terms once per subscription (required before the first CLI deploy)
az vm image terms accept --urn sac1647283583153:packeton-ubuntu-24-04:default:latest
az vm create \
  --resource-group <your-rg> \
  --name packeton \
  --image sac1647283583153:packeton-ubuntu-24-04:default:latest \
  --size Standard_B2s \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard

Open HTTP to reach the web UI and Composer endpoints:

az vm open-port --resource-group <your-rg> --name packeton --port 80 --priority 900

Step 3 - Connect to your VM

Connect over SSH:

ssh azureuser@<vm-public-ip>

Step 4 - Confirm the Packeton stack is running

nginx serves Packeton on port 80, in front of php8.3-fpm. A local PostgreSQL database and a local Redis instance back it. Both are bound to 127.0.0.1, so no database or cache port is exposed to the network. A background worker keeps repository metadata current.

for u in postgresql redis-server php8.3-fpm nginx packeton-worker; do printf '%-22s %s\n' "$u:" "$(systemctl is-active $u)" done

All five units report active, and only nginx listens on a public port.

Step 5 - Retrieve the first-boot administrator credentials

On the first boot of your instance, a one-shot service generates a fresh application secret and rotates the PostgreSQL password. It then builds the database schema, sets a fresh administrator password, and writes the credentials to a root-only file. Read them with:

sudo cat /root/packeton-credentials.txt

The file is mode 0600 and owned by root. The administrator password is unique to this VM.

Step 6 - Sign in to the web UI

Browse to http://<vm-public-ip>/login and sign in as the generated administrator, username admin. Packeton presents its Packagist-style package browser.

Step 7 - Host a private Composer package

Choose Submit to add a package from a version control repository. Packeton supports git, subversion and mercurial.

Paste a repository URL and select Check. Packeton reads the package name from the composer.json on the default branch and begins tracking it.

Step 8 - Issue an API token for Composer

Each user has API tokens on the profile page. A token authenticates composer against your private repository over HTTP basic auth (username:token).

The repository serves standard Composer v2 metadata. Confirm this from the VM with the administrator's API token:

TOKEN=$(sudo -u postgres psql -tAc "SELECT apitoken FROM fos_user WHERE username='admin'" packeton | tr -d ' ')
curl -s -o /dev/null -w 'GET /api/healthz: HTTP %{http_code}\n' http://127.0.0.1/api/healthz
curl -s -u "admin:$TOKEN" http://127.0.0.1/packages.json | head -c 400; echo

Packeton returns the Composer repository descriptor, which includes the metadata URL, mirrors and dist URLs.

To consume the repository from a developer workstation, add it to your project composer.json and provide the token when prompted:

composer config repositories.packeton composer http://<vm-public-ip>/ composer require your-vendor/your-package

Step 9 - Check the version and stack

The image ships Packeton 2.7.0 on PHP 8.3, PostgreSQL 16, Redis 7 and nginx, with the first-boot secret-rotation service enabled:

echo -n 'Packeton version: '; grep -oE '"version": *"[0-9.]+"' /var/www/packeton/composer.json | head -1 | grep -oE '[0-9.]+' || echo 2.7.0 php -v | head -1 sudo -u postgres psql -tAc 'SHOW server_version'

Step 10 - Review the first-boot security model

No shared or default credentials ship in the image. On first boot, packeton-firstboot.service does the following:

• Generates a fresh per-VM APP_SECRET.
• Rotates the PostgreSQL packeton role password to a fresh per-VM value and writes it into /var/www/packeton/.env.local.
• Builds the database schema.
• Sets a fresh per-VM administrator password.
• Writes the credentials to /root/packeton-credentials.txt (root only, 0600).

Confirm that first boot completed and the credentials are protected:

sudo systemctl is-active packeton-firstboot.service
sudo stat -c '%a %U:%G' /root/packeton-credentials.txt

Step 11 - Enable HTTPS with a custom domain (recommended)

Point a DNS A record at your VM's public IP address. Open 443/tcp in your NSG, then install a Let's Encrypt certificate with certbot:

sudo apt-get update && sudo apt-get install -y certbot python3-certbot-nginx
sudo certbot --nginx -d packages.your-domain.com

Certbot obtains the certificate and reconfigures nginx to serve Packeton over HTTPS and redirect HTTP to HTTPS. Packeton detects the request host automatically, so no application configuration change is needed.

Step 12 - Maintenance

• Change the administrator password in the web UI (profile, then change password), or from the CLI:

  sudo -u www-data php /var/www/packeton/bin/console packagist:user:manager admin --password

• Add more users in the web UI under Settings, then Users, or with packagist:user:manager <username> --email=<email> --password.
• Security updates are applied automatically by Ubuntu's unattended-upgrades. The Packeton application, PHP, PostgreSQL, Redis and nginx are managed by systemd and restart on failure.
• Back up the PostgreSQL packeton database and the stored zipballs under /var/www/packeton/var/zipball.

Support

SecureAnyCloud provides 24/7 support for this image by email (sales@secureanycloud.com) and live chat. Support covers deployment, first-boot credential retrieval, VCS integration, API tokens, mirroring, HTTPS and custom domains, upgrades and troubleshooting.

For billing or subscription changes, contact sales@secureanycloud.com.

Deploy on Azure

Launch Packeton on Ubuntu 24.04 LTS on Azure with 24/7 support from SecureAnyCloud.

View this image

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com

Architecture at a glance

Component Detail

Application Packeton 2.7.0 (Symfony), served from /var/www/packeton/public

Web server nginx, listening on port 80

PHP PHP 8.3 (php8.3-fpm) with OPcache

Database PostgreSQL 16, datadir on a dedicated EBS volume at /var/lib/postgresql

Application storage Code and stored package zipballs on a dedicated EBS volume at /var/www

Cache / queue Redis, bound to 127.0.0.1

Health endpoint http://<instance-public-ip>/login (returns HTTP 200 when healthy)

The database tier and the application tier each live on their own independently resizable EBS volume, separate from the operating-system disk. You can grow the storage for either tier without disturbing the other. Both PostgreSQL and Redis are bound to 127.0.0.1, so no database or cache port is exposed to the network.

Connecting to your instance

Connect over SSH on port 22 as the default login user for your operating-system variant.

OS variant SSH login user

Ubuntu 24.04 ubuntu

ssh -i /path/to/your-key.pem ubuntu@<instance-public-ip>

Replace <instance-public-ip> with the public IPv4 address of your instance, which the EC2 console shows. Replace /path/to/your-key.pem with the private key you launched the instance with.

In the instance's security group, open 80/tcp to your developers, and also 443/tcp if you enable HTTPS. Allow 22/tcp from your management network.

Confirm the Packeton stack is running

nginx serves Packeton on port 80, in front of php8.3-fpm. A local PostgreSQL database and a local Redis instance back it. A background worker keeps repository metadata current.

for u in postgresql redis-server php8.3-fpm nginx packeton-worker; do printf '%-22s %s\n' "$u:" "$(systemctl is-active $u)" done

All five units report active, and only nginx listens on a public port.

Retrieve the first-boot administrator credentials

On the first boot of your instance, a one-shot service generates a fresh application secret and rotates the PostgreSQL password. It then builds the database schema, sets a fresh administrator password, and writes the credentials to a root-only file. Read them with:

sudo cat /root/packeton-credentials.txt

The file is mode 0600 and owned by root. The administrator password is unique to this instance.

Sign in to the web UI

Browse to http://<instance-public-ip>/login and sign in as the generated administrator, username admin. Packeton presents its Packagist-style package browser.

Host a private Composer package

Choose Submit to add a package from a version control repository. Packeton supports git, subversion and mercurial.

Paste a repository URL and select Check. Packeton reads the package name from the composer.json on the default branch and begins tracking it.

Once a package is indexed, it gets its own page with its composer require line, its published versions and update controls. The repository serves this to Composer clients as standard Composer v2 (p2) metadata and zipball dists.

Manage users and issue API tokens

Manage users, roles and access under Settings, then Users. Each user has API tokens on their profile page. A token authenticates composer against your private repository over HTTP basic auth (username:token).

Confirm that the repository serves Composer metadata from the instance, using the administrator's API token:

TOKEN=$(sudo -u postgres psql -tAc "SELECT apitoken FROM fos_user WHERE username='admin'" packeton | tr -d '[:space:]')
curl -s -o /dev/null -w 'GET /api/healthz: HTTP %{http_code}\n' http://127.0.0.1/api/healthz
curl -s -u "admin:$TOKEN" http://127.0.0.1/packages.json | head -c 400; echo

Packeton returns the Composer repository descriptor, which includes the metadata URL, mirrors and dist URLs.

To consume the repository from a developer workstation, add it to your project composer.json and provide the token when prompted:

composer config repositories.packeton composer http://<instance-public-ip>/ composer require your-vendor/your-package

Check the version and stack

The image ships Packeton 2.7.0 on PHP 8.3, PostgreSQL 16, Redis and nginx, with the first-boot secret-rotation service enabled:

echo -n 'Packeton version: '; grep -oE '"version": *"[0-9.]+"' /var/www/packeton/composer.json | head -1 | grep -oE '[0-9.]+' || echo 2.7.0 php -v | head -1 sudo -u postgres psql -tAc 'SHOW server_version'

The first-boot security model

No shared or default credentials ship in the image. On first boot, packeton-firstboot.service does the following:

• Generates a fresh per-instance APP_SECRET.
• Rotates the PostgreSQL packeton role password to a fresh per-instance value and writes it into /var/www/packeton/.env.local.
• Builds the database schema.
• Sets a fresh per-instance administrator password.
• Writes the credentials to /root/packeton-credentials.txt (root only, 0600).

Confirm that first boot completed and the credentials are protected:

sudo systemctl is-active packeton-firstboot.service
sudo stat -c '%a %U:%G' /root/packeton-credentials.txt

Enable HTTPS with a custom domain (recommended)

Point a DNS A record at your instance's public IP address. Open 443/tcp in your security group, then install a Let's Encrypt certificate with certbot:

sudo apt-get update && sudo apt-get install -y certbot python3-certbot-nginx
sudo certbot --nginx -d packages.your-domain.com

Certbot obtains the certificate and reconfigures nginx to serve Packeton over HTTPS and redirect HTTP to HTTPS. Packeton detects the request host automatically, so no application configuration change is needed.

Maintenance

• Change the administrator password in the web UI (profile, then change password), or from the CLI:

  sudo -u www-data php /var/www/packeton/bin/console packagist:user:manager admin --password

• Add more users in the web UI under Settings, then Users, or with packagist:user:manager <username> --email=<email> --password.
• Security updates are applied automatically by Ubuntu's unattended-upgrades. The Packeton application, PHP, PostgreSQL, Redis and nginx are managed by systemd and restart on failure.
• Back up the PostgreSQL packeton database and the stored zipballs under /var/www/packeton/var/zipball.

Support

SecureAnyCloud provides 24/7 support for this image by email (sales@secureanycloud.com) and live chat. Support covers deployment, first-boot credential retrieval, VCS integration, API tokens, mirroring, HTTPS and custom domains, upgrades and troubleshooting.

For billing or subscription changes, contact sales@secureanycloud.com.

Deploy on AWS

Launch Packeton with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com