[PR #922] [CLOSED] WIP: Add AppImage workflow #1292

New issue

Closed

opened 2026-03-01 14:49:12 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 14:49:12 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/ArchiveBox/ArchiveBox/pull/922
Author: @noctux
Created: 2/3/2022
Status: ❌ Closed

Base: dev ← Head: dev

📝 Commits (1)

d88202d Add AppImage workflow

📊 Changes

2 files changed (+120 additions, -0 deletions)

View changed files

➕ .github/workflows/appimage.yml (+76 -0)
➕ appimage_dist/archivebox.yml (+44 -0)

📄 Description

Summary

As discussed in #916, I see value in a release of ArchiveBox as an AppImage along with the other releases.
Therefore, this commit adds a github workflow for automatically building an AppImage on pushes.

Please consider this PR as work in progress. The AppImage building works, but I'm not 100% sure as to how you wish to exactly integrate this workflow into the repository and how uploading to the releases page works. Currently, the AppImage is uploaded as an artifact of the CI-run to show that working artifacts are produced. Currently, you seem to have factored out all distribution-methods into their own submodules. Should I do the same for the appimage_dist?

Furthermore, I plan to write a short bit of documentation on the specifics of the AppImage (i.e.: what is packaged, what is not, that there is no sandboxing and that other distribution methods are preferred and potentially better supported). I'd probably put that into docs/Install.md. Does that sound like the correct location?

Any other comments/requests/*?

Thanks for your efforts!

#916

Changes these areas

Bugfixes
Feature behavior
Command line interface
Configuration options
Internal architecture
Snapshot data layout on disk

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/ArchiveBox/ArchiveBox/pull/922 **Author:** [@noctux](https://github.com/noctux) **Created:** 2/3/2022 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `dev` --- ### 📝 Commits (1) - [`d88202d`](https://github.com/ArchiveBox/ArchiveBox/commit/d88202d6eee79b13ce7883f465892b6235c7996f) Add AppImage workflow ### 📊 Changes **2 files changed** (+120 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/appimage.yml` (+76 -0) ➕ `appimage_dist/archivebox.yml` (+44 -0) </details> ### 📄 Description # Summary As discussed in #916, I see value in a release of ArchiveBox as an AppImage along with the other releases. Therefore, this commit adds a github workflow for automatically building an AppImage on pushes. Please consider this PR as work in progress. The AppImage building works, but I'm not 100% sure as to how you wish to exactly integrate this workflow into the repository and how uploading to the releases page works. Currently, the AppImage is uploaded as an artifact of the CI-run to show that working artifacts are produced. Currently, you seem to have factored out all distribution-methods into their own submodules. Should I do the same for the appimage_dist? Furthermore, I plan to write a short bit of documentation on the specifics of the AppImage (i.e.: what is packaged, what is not, that there is no sandboxing and that other distribution methods are preferred and potentially better supported). I'd probably put that into `docs/Install.md`. Does that sound like the correct location? Any other comments/requests/*? Thanks for your efforts! # Related issues #916  # Changes these areas - [ ] Bugfixes - [ ] Feature behavior - [ ] Command line interface - [ ] Configuration options - [ ] Internal architecture - [ ] Snapshot data layout on disk --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>