thaloco/banger
1
Fork 0
Code Pull requests Releases Packages Activity Actions

Untrack todos scratch file; ignore it

Browse source 
Accidentally staged into the prior prune commit by `git add -A`.
It's a local scratch file the maintainer keeps in the repo root.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Thales Maciel 2026-04-18 15:40:46 -03:00
parent 6083e2dde5
commit ace4782fce
No known key found for this signature in database
GPG key ID: 33112E6833C34679
2 changed files with 1 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.gitignore vendored
View file

@ -17,3 +17,4 @@ wtf/*.deb
*.key
id_rsa
.env
/todos

15
todos
View file

@ -1,15 +0,0 @@
when developing, vm creation may fail, and firecracker logs need to be manually looked into, we should add a convenient way of digging through it. or perhaps log the last lines of it when vm creation fails
`banger vm run` can hang waiting for ssh if things go south with sshd inside the vm. I think we should have a timeout instead of hanging forever. And also log what the user can do in such scenario.
some commands are expected to take a while, it'd be good to at least show an indicator that banger is not hanging but rather doing something expected
perhaps add an "interactive flag"?
my computer is not the usual computer that users may have. perhaps it would be a good idea to screen the hardware we're working on so that we can set reasonable defaults for people when installing?
versioning and releasing could use some love
coverage would be somewhat nice to have
regular users have no idea how to point their machine DNS to use the banger dns server. they need a tutorial/docs for this