Documentation
Guides for installing, getting to know the system and contributing. The technical reference is kept alongside the code, in the project repository.
Build from source
The development repository is private. The technical links on this page require authorized access on GitHub. The ISOs are not available for public download yet.
If you already have access, read the build guide for the revision you intend to test. It describes the Arch Linux environment, dependencies, asset generation, validation and virtual machine tests.
Build guide (restricted access) · Development status · Talk about contributing
Read the public guides to learn about the components before preparing an installation.
Installation and usage
Service status
In the Neovanguard OS terminal, run the diagnostics panel. It shows network, Bitcoin, Lightning, Nostr and memory.
neo-statusThe output shows which services are active or stopped. A stopped service does not, by itself, mean the installation failed. Before enabling it, review its configuration and the resources it needs.
To see the available options, open the help. The command below prints usage instructions.
neo-status --helpThese commands belong to the operating system; they are not development commands for this website.
Diagnostics and bug reports
Start with the system guides. If the problem persists, open an issue with the system version, the media used, the steps to reproduce and the error message. Remove private keys, passwords and other personal information before sharing command output.
Reference for contributing
- 01
ISO images
documentation/as-isos.mdHow the Live and Install images work, the system included on the media and USB drive detection.
- 02
Building the images
documentation/COMO-CONSTRUIR.mdDependencies, building packages, generating the ISO and checks with --check.
- 03
Technical briefing
documentation/briefing-tecnico.mdArchitecture, implementation decisions, validation and known limitations.
- 04
Repository structure
documentation/estrutura.mdHow directories, source code and generated files are organized.
- 05
Live session components
documentation/heranca-do-live.mdComponents exclusive to the Live session, their removal during installation and build checks.
- 06
Security review scope
documentation/security-review-scope.mdPriority components and checks for security review.
The package repository
Neovanguard packages are distributed through this repository, with signature verification. The system already includes the public key and the following configuration in /etc/pacman.conf.
[neovanguard]
SigLevel = Required DatabaseOptional
Server = https://neovanguard.com.br/repo/$archFingerprint of the release key used to sign packages and images:
9ED7 92DC EA8D 869E CD79 CE72 5F86 3B33 9A1E 5762Command help
Use --help to check the syntax and options of the neo-* commands and of the installer.
neo-status --help
neo-zap --help
nvginstall --help