Proposal: Create Official APT Repository for Caido Desktop Releases#1
Proposal: Create Official APT Repository for Caido Desktop Releases#1ebauger wants to merge 2 commits intocaido:mainfrom
Conversation
- Introduced `aptify.yml` to define the APT repository for Caido desktop packages. - Created GitHub Actions workflow `update-apt-repo.yml` to automate the update process, including package downloads and repository synchronization. - Added `download_deb_packages.sh` script to fetch and manage .deb packages from the Caido API, with error handling and logging features.
|
Thanks for providing the basis for this. I agree we should do that. It might look. A bit different since we will likely publish from our internal tooling, but I really appreciate the contribution :) |
This is a suggested implementation, but I expect it will vary depending on your internal tools. I used Cloudflare's R2 to run an S3 instance and rclone and aptify. Another question @Sytten: I have another proposal to amend the .deb packages. Where I should put the proposal ? |
|
Yeah cloudflare is great, we already use it for caido.download. For the deb improvements can you open an issue on the caido/caido repo. FYI we us electron-builder v25 to build them at the moment. |
|
Sorry this was not prioritized, still planned but we have more urgent things to do right now. |
Hey Caido Team!
@Sytten , @Corb3nik
I've got a suggestion for you: let's set up an official
pkg.caido.ioordeb.caido.iorepository for Debian and its friends. This would make installing Caido super easy for tons of users!How Caido Installs Now (via zbranch.io)
Right now, folks can install Caido using the pkg.zbranch.io repository with these commands:
What to do if you like the idea?
If you're on board with creating your own official repo, here's what you'd need to do:
Add Your GPG Private Key to GitHub Actions: You'll need to set this up as a secret. You can generate the key using
aptify init-keys.Add Your RCLONE_CONFIG to GitHub Actions: This also needs to be a secret. Here's an example of what that configuration might look like:
Tweak your Github Workflow: You'll want to adapt your
.github/workflows/update-apt-repo.ymlworkflow to work with your new rclone configuration.What do you think? I'm happy to help if you have any questions!