You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ckb-capsule leverage ckb-cli and docker to manage pks and build environment, but sometimes those tools block users' experience.
In #77 , the new version of ckb-cli brokes the capsule's feature. In the end, we need to release a new version to be compatible with the new version ckb-cli. What if a user upgrades the capsule to the latest version but stays with an old version of ckb-cli? The capsule command is still broken!
Capsule requires docker to build binaries. It is for the reproducible build. But when the docker image is x86, you cannot build it on a non-x86 device. To improve the developer's UX, we should support build without docker.
Due to the above reasons, I suggest the following feature/refactoring.
Build improvement
Support non-docker mode. Remove the dependency of docker.
Allow customized build commands.
Support multi-language by separated binaries, such as ckb-capsule-rust, ckb-capsule-c, and ckb-capsule-lua.
We can release a new version of language build support without releasing a new capsule.
Deployment improvement
capsule should output a hexed encoded transaction. Let ckb-cli handle the signing and sending.
ckb-capsule
leverageckb-cli
anddocker
to manage pks and build environment, but sometimes those tools block users' experience.In #77 , the new version of ckb-cli brokes the capsule's feature. In the end, we need to release a new version to be compatible with the new version
ckb-cli
. What if a user upgrades the capsule to the latest version but stays with an old version of ckb-cli? The capsule command is still broken!Capsule requires
docker
to build binaries. It is for the reproducible build. But when the docker image is x86, you cannot build it on a non-x86 device. To improve the developer's UX, we should support build without docker.Due to the above reasons, I suggest the following feature/refactoring.
docker
.ckb-capsule-rust
,ckb-capsule-c
, andckb-capsule-lua
.Deployment improvementcapsule should output a hexed encoded transaction. Letckb-cli
handle the signing and sending.The text was updated successfully, but these errors were encountered: