A bridge application that exposes several Minecraft-related services as a Maven repository, so that plugins can be managed as dependencies using standard Java tools.
-
Exposes Hangar resources as Maven resources, using the "io.papermc.hangar." group ID.
- Supports the following platforms: paper, velocity and waterfall.
- Supports release channels: append "." to the group ID.
-
Exposes Modrinth resources as Maven resources, using the "com.modrinth." group ID.
- Supports the following loaders: paper, velocity, waterfall, bungeecord, minecraft, fabric, forge, sponge and folia.
- Alpha versions reported according to Maven conventions as -SNAPSHOT.
Use the Docker image with port 80, or install dependencies using pip install . and run with Python app/main.py.
Running the app directly should be reserved for development usage as it only use uvicorn as web server. Place it behind
a reverse proxy, or use the Docker image for production, as it uses nginx Unit, a combined application server and
reverse proxy. You may configure nginx Unit by modifying nginx/.unit.conf.json or by overriding the included image's
configuration at /docker-entrypoint.d/.unit.conf.json.
The Maven repository is accessible at sub-path /repository/.
You can also access the API documentation with an interactive UI at /docs/.
This bridge does not have support for authentication. If you want to limit usage of your instance, please protect it with a reverse proxy, such as Docker image's nginx Unit.
Responses from backends (Hangar, Modrinth) are cached to memory for a configurable amount of time. It is not recommended to disable it as to not overwhelm them. You take responsibility to properly rate-limit your instance.
The bridge does not store artifacts (JARs, ...) by itself. Instead, it redirects to the original requested resource's URL as returned by backends. While some backends have predictable URLs, others do not: the bridge may need to retrieve metadata.
However, the bridge does not cache its output by itself. Please use a reverse proxy if you want to cache them, such as Docker image's nginx Unit. Cache-Control headers are already defined.
Configuration is done using variable environment or a .env file. All variables are prefixed with MC_MAVEN_BRIDGE__.
MC_MAVEN_BRIDGE__DEBUG: Enable debug information in output. Should NEVER be true in production!MC_MAVEN_BRIDGE__HANGAR__API_BASE_URL: Hangar's API base URL. Only supports APIv1. Defaults tohttps://hangar.papermc.io/api/v1.MC_MAVEN_BRIDGE__HANGAR__CACHE_PROJECT_EXPIRATION: How many seconds Hangar projects will be kept in cache.MC_MAVEN_BRIDGE__HANGAR__CACHE_VERSION_EXPIRATION: How many seconds Hangar resource versions will be kept in cache.MC_MAVEN_BRIDGE__HANGAR__VERSIONS_LIMIT_PER_BATCH: The number of versions to fetch in a single batch from the Hangar API.MC_MAVEN_BRIDGE__HANGAR__VERSIONS_TOTAL_TO_FETCH: The total number of versions to fetch from the Hangar API.MC_MAVEN_BRIDGE__MODRINTH__API_BASE_URL: Modrinth's API base URL. Only supports APIv2. Defaults tohttps://api.modrinth.com/v2.MC_MAVEN_BRIDGE__CACHE__POM_EXPIRATION: How many seconds computed POM for a resource should be kept in cache.MC_MAVEN_BRIDGE__CACHE__METADATA_EXPIRATION: How many seconds computed metadata (essentially version list) for a resource should be kept in cache.MC_MAVEN_BRIDGE__CACHE__JAR_EXPIRATION: How many seconds computed JAR redirections for a resource should be kept in cache.