-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Host marvin-mk2 #24
Comments
You'll need to have a GitHub token secret, right? For that, you'll need to have a GPG key with git-crypt. Also, all the current people who have access to the secrets will need to be okay with you having access. I am okay with you having access. Then, you will need to make a PR that adds NixOS configuration for running your bot. |
Sounds good! It's built as a GitHub App now, so it will need
I haven't used git crypt before. So that would basically mean that someone with an already whitelisted key would add my gpg public key to the whitelist? Since the secrets should only be a one-time setup, I'd be okay with just letting one of the pre-existing admins set that up if that is easier. |
You also need access to the secrets to deploy to the server. If you don't care about that, I can add your secrets for you. |
Ah, I assumed it just deploys directly from github's master. Being able to deploy fixed might be useful, but I could also live without that since there are already 6 admins. I created #25 to get started with the configuration part. I modeled it after your nixpkgs-update config. |
Fixed! We're now hosting it :) |
Should I open an issue about this? Having to nag one of you every time I'd like to deploy an update is not ideal, especially since I can't control when a deploy happens :) |
Yes, it's probably best to open another issue, then I can ping all the people with access to get their okay. |
I'd like to move the marvin-mk2 bot (repo) onto nix-community infrastructure before starting to test it on nixpkgs.
It should consume very little resources. Would that be possible? If so, how should I go about it?
The text was updated successfully, but these errors were encountered: