Pup Configuration

[elusiveshiba]

Yesterday I was exploring the Remote Core Pup - A Pup which exposes Dogecoin Core functionality to other Pups running on Dogebox, but actually talks to an existing Dogecoin Core node running elsewhere.

It will require minimal configuration, fields such as RPC Server IP, RPC User and RPC Password to be configured after installation.
@patowens mentioned that there's some incomplete development for this.

So, Pup Configuration

A section where users can input basic settings and configurations, to be used by a Pup

Some questions

Firstly I'd like to ask - Is this useful to add now?

• Are there configurations for our existing Dogecoin Core Pup that would be nice to expose to the user?
• If not, do we have any other existing or soon-to-exist Pups (Remote Core for eg.) for which this would be important?

Secondly, on implementation - I believe there's been some previous ideas about how to best do this?

• How and where are the configurations saved (glob files? db?)
• Need to review how much of the configuration form builder is working, does it build from a Pup manifest file correctly?
• There's a 'needs config' install setp, need to see how much of that is implemented and what needs further work

It may be that this just isn't very needed at the moment, if so we can park this for a later date.

[SomeoneWeird]

copy/paste from discord:

Yeah we had originally planned a very large configuration option set for pups - we never got around to actually implementing it though. A bunch of stuff already exists in the frontend and backend for it, but it's not wired up. It's a little tricky with nix.

There's a bunch of complexities we need to figure out how to deal with: if we're wrapping upstream software and want to expose configuration options to that, we might need to build a shim that reads those config options and wraps the upstream binary so they end up in the right place etc

We wanted configuration options to be completely template-able, and then also have the ability for smart-ness with like "generate this once on boot" etc.

Configuration options may also need to be exposed to other, dependant pups. For example, dogecoin core may have an RPC user/password set. For other pups to use this dogecoin pup interface, they'd need those credentials.

[elusiveshiba]

Dogebox-WG/dpanel#174
Dogebox-WG/dogeboxd#166