New Maintainer for Bootleg #326
spinlock99
announced in
Announcements
Replies: 1 comment
-
|
Would it be helpful to have a build log? Bootleg is very noisy because it prints the output from each system call to the standard output. I've quieted them down but I think it would be better to log all of the details in those steps and download the log with the final tarball. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
👋 Hi Everyone!
I just wanted to take a minute and introduce myself to everyone who's interested in Bootleg. My name's Andrew and I've volunteered to be the new maintainer for Bootleg. Lab Zero is still providing the infrastructure for testing and building the codebase while I work to move this project forward toward a version 1.0 release.
📈 Progress
I don't use Docker in my workflow. I run Phoenix behind Nginx managed with SystemD. Bootleg is working great for me in this setup but I don't have the bandwidth figure out how Bootleg is using Docker.
💬 Request for Comment
Docker: I'd like to get a better idea how many people are using Bootleg with Docker and figure out a plan for supporting those users going forward.
AI/LLMs: I'm using Claude Code but don't have a lot of experience yet. Any and all feedback is welcome!
🫵 If you're using Bootleg with Docker, please leave a comment below and join the discussion.
Thanks!
Andrew
Beta Was this translation helpful? Give feedback.
All reactions