Firstly, thank you for making this MCP server! :)
Lets bikeshed the PR for https://github.com/adept/hledger-mcp-docker
I've initially opted to create a separate repo because I already maintain https://github.com/adept/hledger-docker, and I knew that I would be able to build/update/upload anoter image from time to time.
I think that if the Dockerfiles are included in your repo, there is a lazy choice and a proper choice:
- extralazy choice is not to build the image at all. I do not think that this is proper, as building is easy and providing people with prebuilt image is nice
- the lazy choice is that you (or someone) manually builds/pushes packages from time to time
- the proper choice is perhaps to set up github actions to auto-build the alpine image with prepackaged hledger (as this builds rather quickly) and auto-push it.
Now, my problem is that I wont be able to one-shot github actions that, when included in PR, will just work on merge. For starters they would need the details that only you would have (like access tokens, Dockerpub username, etc).
So... Do you have opitions on this? What do you want this PR to achieve?
Firstly, thank you for making this MCP server! :)
Lets bikeshed the PR for https://github.com/adept/hledger-mcp-docker
I've initially opted to create a separate repo because I already maintain https://github.com/adept/hledger-docker, and I knew that I would be able to build/update/upload anoter image from time to time.
I think that if the Dockerfiles are included in your repo, there is a lazy choice and a proper choice:
Now, my problem is that I wont be able to one-shot github actions that, when included in PR, will just work on merge. For starters they would need the details that only you would have (like access tokens, Dockerpub username, etc).
So... Do you have opitions on this? What do you want this PR to achieve?