-
Notifications
You must be signed in to change notification settings - Fork 50
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
Looking for maintainers #11
Comments
Did you ever find someone to do it for you? Quick question: Is a local copy of node necessary to build the package, and should the cockpit-docker container be running? Thanks |
…ash-4.17.21 Bump lodash from 4.17.19 to 4.17.21
Hi would like to take up as a maintainer. Using cockpit for Linux Server management, and would like to keep this up to date. |
I'm now maintaining a port of cockpit-podman for Docker. I'm doing this for my employer, so it should be active for the foreseeable future. |
Hey @chabad360 I have tested it on Manjaro Linux Arm. Submitted a PKGBUILD to AUR lets shop it gets accepted. |
Sorry for the late reply. If you’re still willing to do it, feel free to fork. I’ll redirect this repo to yours :) |
Hi Xantios,
looks like https://github.com/chabad360/cockpit-docker is already
maintaining it - see https://github.com/chabad360/cockpit-docker . I see no
value in duplicating the effort, you can redirect there.
Regards
Il giorno dom 28 gen 2024 alle ore 16:11 Xantios Krugor <
***@***.***> ha scritto:
… Hi
would like to take up as a maintainer.
Using cockpit for Linux Server management, and would like to keep this up
to date.
Sorry for the late reply. If you’re still willing to do it, feel free to
fork. I’ll redirect this repo to yours :)
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACT2MISULEUPZYDRNHQ3YLYQZTBRAVCNFSM5ECZYXT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJRGM3DEOBUG42Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I don't use cockpit anymore, if anyone is interesting in fixing this repo up feel free to do so.
The text was updated successfully, but these errors were encountered: