Kodi Repository Bootstrapper
Many thanks to @Twilight0 and all the others who contributed code for this project before.
Installation
You can install this Python package via pip(x):
pip(x) install kodi-repo-bootstrap
Otherwise the package can be downloaded from PyPI: https://pypi.org/project/kodi-repo-bootstrap/
Usage
1. Preperations
You need two directories:
-
addons_dir: This direcotry contains the Kodi addons you want to publish. The single addons can be present as ZIP files or as a directory with the official Kodi addon structure.A valid
addons_dirwill look like this:addons_dir/ |- plugin.addon.id-versionX.zip - and / or - |- plugin.addon.id/ | |- addon.xml | |- ... | - and / or - | |- plugin.addon.id-versionX.zipIf multiple versions of the same addon (same ID) are present, only the newest version will be used by the script.
-
repo_dirwhere this script creates the necessary structure for a Kodi repository. Please do not make any manual changes to this directory.
2. Define repository settings
Create a configuration file in JSON format (e.g. config.json). An example file with the available options can be found in the root directory of this repository: config.json.example
OR
Configure the Kodi repository with CLI arguments. See
kodi-repo-bootstrap -h
for the available settings.
3. Run the script
kodi-repo-bootstrap <CONFIG_FILE>
The path to the config file is mandatory.
This will create all files and directories that are necessary for a Kodi repository. No user interaction is needed.
4. Publish the repo_dir e.g. via HTTP server (webdav)
The repo_dir contains all files and directories that are necessary for Kodi to recognize it as a valid repository. You only have to publish it via HTTP.
For a simple Webdav setup with Docker, you can have a look at my other repository: docker-webdav
5. [Optional] Change repository settings
To change any settings you can either
- adjust the config file
OR
- use a CLI argument. The script will then save the changes to the config file for you.
Troubleshooting
If you encounter any errors, please clear the repo_dir first and run the script again. This will recreate the Kodi repository file structure.
If the error is still present, feel free to open an issue on GitHub.
Metadata
Release files for kodi-repo-bootstrap 3.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kodi_repo_bootstrap-3.0.3.tar.gz | 17.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kodi_repo_bootstrap-3.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.6 kB
Release files / kodi_repo_bootstrap-3.0.3.tar.gz
| Download URL | kodi_repo_bootstrap-3.0.3.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1df0a5f7a8cec3b2cfef27d1980a297c07e837440b9c7fe97d30685c86023cfa
|
|
BLAKE2b-256 checksum How to use checksums |
5ad462efb7ef9578a68d316160f1f5304ed5b3cb834614b44a328b5ed73bbd4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency logRelease files / kodi_repo_bootstrap-3.0.3-py3-none-any.whl
| Download URL | kodi_repo_bootstrap-3.0.3-py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f23144fcbfb4fc53b3c228f9179a4c4000e4b2cb02936c08b89688bab120d10d
|
|
BLAKE2b-256 checksum How to use checksums |
61b8233badfa09fb346fa6f42efe4a9b1980e3513fd51c71e8c616e6c7bf791e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency log