Closed JesseAbram closed 4 months ago
Generally this looks great. I think it would be nice if this was a generic binary rather than needing to be compiled for every project. As in this crate should live outside of the cargo-generate template, and be installed just once with
cargo install
.In the long term, i would like it if this tool would have an option to specify whether the program is intended to be publicly available, and if it is, then make an HTTP request to the
program-metadata-web-service
, which pulls the name and description etc, fromCargo.toml
and makes that data available through a json http api. The testnet status page uses it to display names in the list of programs. And the SDK could use it to make a 'program picker' for users.But the
program-metadata-web-service
is not yet deployed. And it requires you to build the program with docker in order that it can verify that the source code matches the on-chain binary.
I like your vision here, imma take some of your suggestions, but would really like if you could make some issues with the ideas cuz most of them are fire
Adds a cli tool to the template to upload programs
This can get better when we open source core, the CLI should probably pulled in from core when we do that, but until then this should get the ball moving.