Browse GitHub/Gitea/Forgejo Actions artifacts https://codeberg.org/ThetaDev/artifactview/
Find a file
2024-05-31 02:02:53 +02:00
.forgejo/workflows ci: enable cache on failure 2024-05-31 01:48:04 +02:00
crates feat: add site aliases 2024-05-30 17:58:54 +02:00
resources feat: add default favicon 2024-05-30 21:11:19 +02:00
src fix: use default config for testing 2024-05-31 01:53:56 +02:00
templates fix: mangled filter javascript 2024-05-30 20:36:40 +02:00
.editorconfig feat: improve website design 2024-05-29 21:58:13 +02:00
.env.example feat: read config from env, add robots.txt, prevent access to .well-known 2024-05-28 12:23:49 +02:00
.gitignore ci: add Dockerfile and CI workflow 2024-05-31 01:16:15 +02:00
.pre-commit-config.yaml chore: add pre-commit 2024-05-28 12:30:14 +02:00
build.rs feat: add file listing 2024-05-29 18:59:55 +02:00
Cargo.lock ci: add Dockerfile and CI workflow 2024-05-31 01:16:15 +02:00
Cargo.toml chore: update Cargo.toml metadata 2024-05-31 01:30:38 +02:00
CHANGELOG.md chore(release): release artifactview v0.1.0 2024-05-31 02:02:53 +02:00
cliff.toml chore(release): release artifactview v0.1.0 2024-05-31 02:02:53 +02:00
Dockerfile ci: add Dockerfile and CI workflow 2024-05-31 01:16:15 +02:00
Justfile chore: add release script 2024-05-28 15:22:10 +02:00
LICENSE initial commit 2024-05-26 13:56:53 +02:00
README.md feat: add file size limit, zip timeout 2024-05-28 18:07:37 +02:00

Artifactview

View CI build artifacts from Forgejo/Github using your web browser.

Forgejo and GitHub's CI systems allow you to upload files and directories as artifacts. These can be downloaded as zip files. However there is no simple way to view individual files of an artifact.

Artifactview is a small web application that can fetch these CI artifacts and serve their contents. If the artifact contains a website, it is displayed normally, if it consists of other files, a file listing is shown.

There is also full support for single page applications, placing a file named 200.html in the root directory it will be returned in case no file exists for the requested path.

Alternatively, if a file named 404.html exists in the root directory, it will be returned with status code 404 if no file was found.

How to use

Artifactview accepts URLs in the given format: <HOST>--<USER>--<REPO>--<RUN>-<ARTIFACT>.example.com

Example: https://github-com--theta-dev--example-project--4-11.example.com

Security considerations

It is recommended to use the whitelist feature to limit Artifactview to access only trusted servers, users and organizations.

Since many well-known URIs are used to configure security-relevant properties of a website or are used to attest ownership of a website (like .well-known/acme-challenge for issuing TLS certificates), Artifactview will serve no files from the .well-known folder.

There is a configurable limit for both the maximum downloaded artifact size and the maximum size of individual files to be served (100MB by default). Additionally there is a configurable timeout for the zip file indexing operation. These measures should protect the server againt denial-of-service attacks like overfilling the server drive or uploading zip bombs.