Cardinal-Cryptography / Cardinal-Cryptography/aleph-node-issues
Node documentation.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 2
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Did you read the documentation and guides?
- [X] I have inspected the documentation.
### Is there an existing issue?
- [X] I have searched the existing issues.
### Description of the problem
Aleph node needed to have documentation on details around docker deployment. If proper documentation exists, everyone can deploy according to their needs and have a better experience in general through updates and everything since if they add some extra flag, they would know why they added it.
At the current state, script changes some files, mostly that's pulling chainspec file and rarely making other adjustments. There are more reliable ways to do this than script. Not to mention one of our servers 10.2 not recognized as an update, so the script updated the directory but kept pulling 10.1 instead of 10.2. Anyone could miss that and assume it's updated. This is problematic, considering the network might have problems and a fast response is required. Typically something like docker run aleph 10.1 --some flags command or directly latest tag here on docker-compose. We use the script, and when issues like this happen, we need to go through the script's code see what exactly sends as a command to fix the problem etc. If documentation exists, everyone can do their deployment and streamline their deployment process without relying on an unreliable scrip that could fail for various reasons.
### Information on your setup.
While issue is with script I open this issue to make script a secondary option for docker deployments.
### Steps to reproduce
_No response_
### Did you attach relevant logs?
- [X] I have attached logs (if relevant).
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia esaminando lo script di deployment attuale e qualsiasi riferimento esistente a Docker o docker-compose nel repository. Documenta i comandi diretti di deployment con Docker, i flag rilevanti, il comportamento della versione o di chainspec e il ruolo dello script come opzione secondaria; il lavoro è completato quando gli operatori possono eseguire il deployment senza ispezionare lo script.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, docker-compose
- Ambito
- devops, documentation
- Tipo di issue
- Documentazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 32/100