MoDPR hub

Push with modpr

Placeholders: YOUR_USER is the username you register, your-image is the name you choose, v1 is the tag. Do not put the registry host in -t — the CLI adds it.

1. Register

Create an account on this site. The same username and password are used for modpr login.

2. Install the CLI (once)

mkdir -p ~/.local/bin
curl -fsSL -o ~/.local/bin/modpr \
  this Hub/download/cli
chmod +x ~/.local/bin/modpr
export PATH="$HOME/.local/bin:$PATH"

Or download from /download/cli. Windows: use WSL or Git Bash. modpr is a Python CLI (needs python3 on PATH).

3. Point at this registry

export MODPR_URL=this Hub

On a laptop running the local stack, omit MODPR_URL so the CLI uses http://localhost:8080.

4. Login, build, push

Run modpr login by itself, then type the password at the hidden prompt. Do not paste the next commands into that prompt.

modpr login YOUR_USER
cd /path/to/app
modpr build -t YOUR_USER/your-image:v1 .
modpr push YOUR_USER/your-image:v1

5. Deploy the digest (Projects)

Use a long-running image such as nginx. CMD echo exits and fails health.

modpr deploy YOUR_USER default staging web YOUR_USER/web:v1
modpr paas ps YOUR_USER default staging

6. Confirm

Sign in as YOUR_USER, open Registry. You should see the tag. Tags shows the name and modpr pull. Image management shows digest, size, and the filesystem layer stack. Developers see Push origin for images they own; admins see every owner. Administrators also have Kubernetes and Admin in the sidebar — developers do not.

If it fails

  • modpr: command not found — install step + PATH
  • Push went to localhost — set MODPR_URL to this Hub
  • denied — modpr login; -t must start with your username