[PR #922] WIP: Add AppImage workflow #2802

New issue

Closed

opened 2026-03-01 18:00:47 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 18:00:47 +03:00

Owner

Original Pull Request: https://github.com/ArchiveBox/ArchiveBox/pull/922

State: closed
Merged: No

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

**Original Pull Request:** https://github.com/ArchiveBox/ArchiveBox/pull/922 **State:** closed **Merged:** No --- # 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

kerem

2026-03-01 18:00:47 +03:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ArchiveBox#2802

No description provided.

Rows
Columns