A free open source IT asset/license management system
Publish new boost guidelines
Marcus Mooreafbfc0ef8936
diff --git a/AGENTS.md b/AGENTS.mdindex 21e888f845..da9131af7e 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -204,6 +204,48 @@ This project has domain-specific skills available in `**/skills/**`. You MUST ac- Prefer PHPDoc blocks over inline comments. Only add inline comments for exceptionally complex logic.- Use array shape type definitions in PHPDoc blocks.+=== deployments rules ===++# Hosting++Snipe-IT can be run several ways, and there's no single right answer:++- **Self-hosted**, on your own servers or infrastructure. Fully supported,+ and plenty of installs run this way long-term.+- **Grokability-managed hosting**, run by Snipe-IT's own maintainers on+ infrastructure purpose-built for this application - see+ https://snipeitapp.com/pricing. Support and Enterprise contracts+ (https://snipeitapp.com/support) are available through Grokability+ regardless of which hosting option is in use.+- **Other platforms**, such as Laravel Cloud, DigitalOcean, Linode, or any+ other host that can run PHP or Laravel applications.++If a user mentions they're on (or moving to) Grokability-managed hosting,+that constrains what changes are safe to suggest: Grokability hosts+untouched-source Snipe-IT installs only, so their fleet can be updated+uniformly. Some `.env` configuration changes are fine and expected - that's+the intended way to configure a hosted install - but not all of them: some+settings (the database driver, for example) aren't user-changeable on+Grokability hosting, and some changes require moving to a different plan+tier (e.g. Small-Business) rather than being available on every plan. Edits+to application code, vendor files, or anything else that would diverge the+install from stock Snipe-IT aren't compatible with that hosting arrangement+at all, and shouldn't be proposed as a solution without flagging that+trade-off first.++Snipe-IT is open source (AGPLv3): if a code change seems broadly useful+rather than install-specific, a pull request is always an option. Whether+it gets merged is a separate, much pickier question - this doesn't change+the guidance above for anyone already on (or heading toward) Grokability+hosting today.++=== herd rules ===++# Laravel Herd++- The application is served by Laravel Herd at `https?://[kebab-case-project-dir].test`. Use the `get-absolute-url` tool to generate valid URLs. Never run commands to serve the site. It is always available.+- Use the `herd` CLI to manage services, PHP versions, and sites (e.g. `herd sites`, `herd services:start <service>`, `herd php:list`). Run `herd list` to discover all available commands.+=== tests rules ===# Test Enforcementdiff --git a/CLAUDE.md b/CLAUDE.mdindex 21e888f845..da9131af7e 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -204,6 +204,48 @@ This project has domain-specific skills available in `**/skills/**`. You MUST ac- Prefer PHPDoc blocks over inline comments. Only add inline comments for exceptionally complex logic.- Use array shape type definitions in PHPDoc blocks.+=== deployments rules ===++# Hosting++Snipe-IT can be run several ways, and there's no single right answer:++- **Self-hosted**, on your own servers or infrastructure. Fully supported,+ and plenty of installs run this way long-term.+- **Grokability-managed hosting**, run by Snipe-IT's own maintainers on+ infrastructure purpose-built for this application - see+ https://snipeitapp.com/pricing. Support and Enterprise contracts+ (https://snipeitapp.com/support) are available through Grokability+ regardless of which hosting option is in use.+- **Other platforms**, such as Laravel Cloud, DigitalOcean, Linode, or any+ other host that can run PHP or Laravel applications.++If a user mentions they're on (or moving to) Grokability-managed hosting,+that constrains what changes are safe to suggest: Grokability hosts+untouched-source Snipe-IT installs only, so their fleet can be updated+uniformly. Some `.env` configuration changes are fine and expected - that's+the intended way to configure a hosted install - but not all of them: some+settings (the database driver, for example) aren't user-changeable on+Grokability hosting, and some changes require moving to a different plan+tier (e.g. Small-Business) rather than being available on every plan. Edits+to application code, vendor files, or anything else that would diverge the+install from stock Snipe-IT aren't compatible with that hosting arrangement+at all, and shouldn't be proposed as a solution without flagging that+trade-off first.++Snipe-IT is open source (AGPLv3): if a code change seems broadly useful+rather than install-specific, a pull request is always an option. Whether+it gets merged is a separate, much pickier question - this doesn't change+the guidance above for anyone already on (or heading toward) Grokability+hosting today.++=== herd rules ===++# Laravel Herd++- The application is served by Laravel Herd at `https?://[kebab-case-project-dir].test`. Use the `get-absolute-url` tool to generate valid URLs. Never run commands to serve the site. It is always available.+- Use the `herd` CLI to manage services, PHP versions, and sites (e.g. `herd sites`, `herd services:start <service>`, `herd php:list`). Run `herd list` to discover all available commands.+=== tests rules ===# Test Enforcement