Developer guide
The application and website have separate repositories.
| Repository | Purpose | Build tools |
|---|---|---|
| MyServerManager | Local SSH dashboard | .NET 10 SDK |
| myservermanagerwebsite (private, maintainer access) | This website, documentation and journal | Node.js 24 and npm |
Application source
The app uses ASP.NET Core MVC. Controllers call dedicated services for registration, service management, metrics, logs and website probes. The SSH adapter formats fixed commands with validated arguments.
Source directories, the internal namespace, assembly name and saved-state identity retain their original MyServerManager naming for compatibility.
From the application source root:
dotnet restore ServerAppManager.slnx --locked-mode
dotnet build ServerAppManager.slnx -c Release --no-restore
dotnet test ServerAppManager.slnx -c Release --no-build --no-restore
Automated tests use simulated commands, SSH sessions and HTTP probes with temporary state. Real service operations belong in an explicitly authorized disposable lab.
Website source
From the separate website checkout:
npm ci
npm start -- --host localhost
The development server prints its local address. For production checks:
npm run verify
The website builds static HTML, CSS, JavaScript, feeds, sitemap and a browser-side search index. Hosting serves the built output without an application server or database.
Content editing
Guides live in docs/, public pages in src/pages/ and articles in blog/. Keep product behavior aligned with the current application source. Each of the eight launch guides has a 1,200–2,000 word body and primary references.
The editorial folder holds the 50-topic queue and optional SQLite setup scripts. Editorial databases and drafts stay private; the public website uses reviewed Markdown.
Reviews and publication
The repositories currently keep main as the only branch. Review the diff and run the relevant checks before pushing. GitHub Actions verifies website builds and content, then saves a downloadable static build. The website source remains private while the generated pages can be hosted publicly.
Read the website README for first deployment, domain configuration and rollback. Use an explicit prior commit when restoring a known good website version.