This repository contains the package search and cataloging system for the NurOS ecosystem.
.github/workflows/- GitHub Actions automation filesupdate-list.yml- updates package list every 6 hoursbuild_frontend.yml- builds frontend after package list updatedeploy_on_pages.yml- deploys built frontend to GitHub Pagessync-gitbook.yml- syncs documentation to GitBook
listpkgs.nuros.front-end/- frontend application source codeblog/- GitBook documentation source filespackages.json- metadata file for all NurOS packages (auto-generated)CNAME- custom domain file for GitHub Pages (frontend)
-
Every 6 hours,
update-list.ymlruns to:- Scan all repositories in NurOS-Packages organization
- Collect metadata from
metadata.jsonfiles - Generate a single
packages.jsonfile
-
After successful list update,
build_frontend.ymlruns to:- Install frontend dependencies
- Build frontend using Vite
- Include up-to-date data from
packages.json - Upload result as artifact
-
After successful build,
deploy_on_pages.ymlruns to:- Download built frontend artifact
- Deploy to GitHub Pages via GitHub Actions
Note: The
gh-pagesbranch is no longer used. Deployment happens directly through GitHub Actions using artifacts.
The frontend is built with SolidJS and provides:
- Package search by name and description
- Filtering by various criteria
- Package grouping
- Detailed information display
- Full JSON representation view
See README in the frontend folder for more details.
Documentation is now hosted on GitBook for a better reading experience and separate domain.
- GitBook: Setup required - see GITBOOK_SETUP.md
- Includes:
- Getting Started Guide
- System Architecture Overview
- Frontend User Guide
- API Reference & Integration Examples
- Deployment & CI/CD Guide
- Contributing Guidelines
- FAQ
Documentation is in the blog/ directory and uses:
- GitBook for hosting and rendering
- GitHub Actions for automatic sync on push to
main - Prettier for markdown formatting
- Go to GitBook
- Create a Space
- Connect this repository (
NurOS-Linux/listpkgs.nuros.org) - Set source folder to
blog/ - Enable auto-sync
See blog/GITBOOK_SETUP.md for detailed instructions.
| File | Description |
|---|---|
blog/README.md |
Documentation home page |
blog/SUMMARY.md |
Table of contents (GitBook navigation) |
blog/book.json |
GitBook configuration |
blog/getting-started.md |
Quick start guide |
blog/architecture.md |
System architecture |
blog/frontend-guide.md |
Frontend user guide |
blog/api-reference.md |
API documentation |
blog/deployment.md |
Deployment guide |
blog/contributing.md |
Contributing guidelines |
blog/faq.md |
Frequently asked questions |
To contribute:
- Fork the repository
- Create a feature branch
- Commit your changes
- Push to the remote branch
- Create a pull request
For documentation changes, simply edit files in blog/ and they will auto-sync to GitBook.
MIT