Repman - PHP Repository Manager: packagist proxy and host for private packages
Repman - PHP Repository Manager: packagist proxy and host for private packages
Repman is a PHP repository manager. Main features:
Documentation: https://repman.io/docs/
var dir must be writeablehttps://repman.io/docs/standalone/#docker-installation
https://repman.io/docs/standalone/#ansible-playbooks-installation
git clone [email protected]:repman-io/repman.git
cd repman
composer installSetup database:
bin/console doctrine:migrations:migrate #for postgres
bin/console doctrine:schema:create #for sqlite init as migrations are only postgres-compatible
bin/console messenger:setup-transportsTo configure mailer transport, enter connection details in the MAILER_DSN environment variable
MAILER_DSN=smtp://user:[email protected]Read more: transport setup
In addition, setup also MAILER_SENDER environment variable
To process messages asynchronously you must run worker:
bin/console messenger:consume asyncRead more: deploying to production
Navigate your browser to instance address, you will see home page with usage instructions.
On dev env you may want to enable proxy to allow to create subdomains and tests composer organizations:
composer proxy-setupThis will create repman.wip domain. Then you can add other domains with:
symfony proxy:domain:attach your-organization.repmanbin/console repman:metadata:clear-cache - clear packages metadata cache (json files)bin/console repman:create:admin [] - create a new user with admin privilegesbin/console repman:create:user [] - create a new (normal) userbin/console repman:proxy:sync-releases - sync proxy releases with packagist.orgbin/console repman:security:scan-all - scan all synchronized packagesbin/console repman:security:update-db - update security advisories database, scan all packages if updatedbin/console repman:package:synchronize - synchronize given packagebin/console repman:package:clear-old-dists - clear old private dev distributions filesCallbacks:
/auth/{provider}/check/register/{provider}/check/user/token/{provider}/checkScopes:
user:emailread:org, repoScopes:
read_userapiScopes:
emailrepository, webhookTo integrate with self-hosted GitLab, enter the instance url in the APP_GITLAB_API_URL environment variable
APP_GITLAB_API_URL='https://gitlab.organization.lan'By default, Repman stores packages locally on disk. For production deployments, you can use S3-compatible storage.
STORAGE_SOURCE=storage.local
PROXY_DIST_DIR=%kernel.project_dir%/var/proxy
PACKAGES_DIST_DIR=%kernel.project_dir%/var/repoTo use AWS S3 or S3-compatible storage (MinIO, Ceph, etc.):
STORAGE_SOURCE=storage.s3
STORAGE_AWS_BUCKET=my-bucket-name
STORAGE_AWS_REGION=eu-west-1
# When using S3, use relative paths:
PROXY_DIST_DIR=var/proxy
PACKAGES_DIST_DIR=var/repoOption 1: AWS Credential Chain (Recommended for AWS/EKS)
Uses the AWS SDK's default credential provider chain, which supports:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)STORAGE_AWS_OPAQUE_AUTH=false
# No key/secret needed - credentials obtained automaticallyOption 2: Explicit Credentials
For environments where you need to provide credentials directly:
STORAGE_AWS_OPAQUE_AUTH=true
STORAGE_AWS_KEY=your_access_key_id
STORAGE_AWS_SECRET=your_secret_access_keyFor self-hosted S3-compatible storage:
STORAGE_AWS_ENDPOINT=https://s3.myhost.com
STORAGE_AWS_PATH_STYLE_ENDPOINT=truedocker-compose.override.yml if needed.APP_HOST) in .env.docker.If you wish to use your own certificate put key and certificate in:
docker/nginx/ssl/private/server.keydocker/nginx/ssl/certs/server.crtOtherwise self-sign certificate will be generated.
To start all containers run:
docker-compose upIn case of any problems, you can use:
The Repman project is licensed under the terms of the MIT.
However, Repman includes several third-party Open-Source libraries, which are licensed under their own respective Open-Source licenses.
composer license to get the latest licensing info about all dependencies.made with ❤️ by Buddy
No open issues yet, or sync has not completed.