Server Help

[shiralitech]

Hello, I appreciate this repository! Extremely informative & helpful! I was wondering if you could point me in the right direction in building a utility: a go written server which will accept an authentication api request to execute a command line utility(example parameters metaboss update uri -k ~/.config/solana/devnet.json -a CQNKXw1rw2eWwi812Exk4cKUjKuomZ2156STGRyXd2Mp -u https://arweave.net/N36gZYJ6PEH8OE11i0MppIbPG4VXKV4iuQw1zaq3rls from https://metaboss.rs/overview.html) with the variables(token mint account and fqdn like mint-api.foobar.com/json/xxxx.json) reply to the api request the command line output. No worries if not thank you for your time!

[gilcrest]

Hi @shiralitech - I really appreciate the comments on the repo - thanks! Sorry I was AFK this weekend.

If I follow correctly, you're trying to run a webserver that will take some form of authentication and then, if user is authenticated, execute a command line utility (CLI) and send the response from the CLI back to the user - is that correct?

[shiralitech]

no worries, Yes exactly! Thank you for the response

[gilcrest]

It should be possible! If you were to use the construct I've built here, in your clone or fork, I would create a new service with a route something like /api/v1/metaboss:

• Create MetabossService struct and Update method to in service package at ./service/metaboss.go
• Create metabossgateway package and put logic for calling CLI. See notes below
• Create MetabossService interface and Update method in server package at ./server/services.go
• Add MetabossService to Services struct in server package at ./server/services.go
• Create handleMetabossUpdate handler in server package at ./server/handlers.go
• Add /api/v1/metaboss route pointing to handleMetabossUpdate handler and appropriate middleware to Server.registerRoutes method in ./server/routes.go
• Add new MetabossService service to Server.Services initialization in Run function as part of command package in ./command/command.go`

Calling CLI from Gateway

I would encapsulate calling out to the CLI somewhere in a gateway package. In my mind Gateways are for any traffic external from my server/infrastructure. I imagine this CLI is making external calls and I think it's best to think of it as an external entity even if it just stays on your machine.

You can then execute a shell command with the os/exec package. I'm not sure what output this CLI is producing, but if it's directly sending output to stdout that you want to capture, you can then take that, parse it to json, and send that back in your response. If the cli creates a file, you can load and parse that and send that back in your response...

Does that make sense?

[shiralitech]

Absolutely!! The response will be a "success" or "failure" message with some error checking for now as the needed metaboss package command should handle everything. Appreciate the detail and Will get back to you!