Host Our Own Version of the Jpillora Install Script for CLI (okp4d)

axone-protocol / docs

📜 Axone documentation portal (built with Docusaurus).

https://docs.axone.xyz/

BSD 3-Clause "New" or "Revised" License

40 stars 22 forks source link

Host Our Own Version of the Jpillora Install Script for CLI (okp4d) #562

Open AnjaMis opened 1 month ago

AnjaMis commented 1 month ago

The current documentation for the CLI (okp4d) references the use of the Jpillora install script. For security reasons, it is recommended that we host our own version of the install script. This will help mitigate potential risks associated with relying on third-party scripts.

Suggested Solution:

Follow the guidelines provided by Jpillora here to host our own version of the install script.
Update the documentation to reference our self-hosted script.

cc @ccamel @amimart

ccamel commented 3 weeks ago

Agree with that. I propose we self-host the Jpillora install service in our cloud. We can achieve this by:

Building our own Docker images for the installer service.
Hosting the installer service on our cloud infrastructure.
Making the installer service accessible via a dedicated URL, for example, https://i.axone.xyz.

ccamel commented 3 weeks ago

Another option could be to generate the installation script for our artifact from the installer (e.g., curl https://i.jpillora.com/axone-protocol/axoned), host it in the axoned repository, and integrate it into the release cycle to update versions, including the latest.