Latest Docker Images

Running the latest build

Self-hosted MakinForU Panel pins its container images in self-hosting/docker-compose.yml. Stable releases are pinned by major tag (for example :2), but you can also run images built from the newest commits on main.

Where the images come from

Commit builds are produced by the GitHub Actions workflow in .github/workflows/docker-build.yml and pushed to ghcr.io/<your-org>. Tagged releases are built by sh/docker-build and pushed to Docker Hub as makinforu/makinforu-panel-*. The self-hosting scripts read that registry from the MAKINFORU_REGISTRY environment variable:

export MAKINFORU_REGISTRY=ghcr.io/your-org   # default: ghcr.io/makinforu

The resulting image names look like:

$MAKINFORU_REGISTRY/api:main-<sha>
$MAKINFORU_REGISTRY/dashboard:main-<sha>
$MAKINFORU_REGISTRY/worker:main-<sha>

If your registry is private, log in on the server first:

echo "your_token" | docker login ghcr.io -u <user> --password-stdin

Updating

Navigate to your self-hosting folder and run:

./get_latest_images apply

This script will:

• Check that you're authenticated with the configured registry
• Fetch the latest Git tags from the repository
• Back up your docker-compose.yml, then update it with the new image tags

You can also inspect what's available without applying anything:

./get_latest_images           # Show latest tags
./get_latest_images --list    # List all available tags

Then restart your services:

./restart

Quick update workflow

cd /path/to/self-hosting
export MAKINFORU_REGISTRY=ghcr.io/your-org
./get_latest_images apply
./restart

Important notes

• Stability: builds from main are tested but may contain undiscovered bugs. Keep a backup strategy.
• Breaking changes: check the changelog before updating.
• Support: open an issue or a thread in GitHub Discussions.

Need help?

• GitHub Discussions
• Email hello@makinforu.com
• GitHub repository