Weave Code
Nettt Tools Laravel Package
nettt/nettt-tools
Nettt Tools is a Laravel/PHP utility package that bundles practical helpers for everyday development. It aims to reduce boilerplate with streamlined configuration and lightweight integrations, making common tasks quicker and projects easier to maintain.
Deployment scripts and AI skills for Laravel and Statamic projects
Frequently asked questions about Nettt Tools
- What is nettt/nettt-tools used for?
- Nettt Tools is a developer-experience and delivery-tooling package that provides deployment scripts and AI skill definitions for Laravel and Statamic projects. It helps standardize deploy paths and AI-assisted workflows across similar sites. It is not a runtime library and does not ship service providers, facades, or application-facing APIs.
- How do I install nettt/nettt-tools with Composer?
- Because the package is Bitbucket-hosted and does not appear on Packagist, you add a vcs repository entry in composer.json pointing to the Bitbucket repository and require nettt/nettt-tools. You will need SSH or deploy-key credentials configured for CI. Then run composer update to pull the package.
- Does nettt/nettt-tools support Laravel 10 and Laravel 11?
- The package assumes PHP 8.x and a Laravel plus Statamic pairing, but no explicit supported version matrix is published in the overview. You should confirm supported Laravel, Statamic, and PHP versions with the maintainer before committing. Because the tooling is script-based, framework upgrades may require manual adjustments.
- Is nettt/nettt-tools available on Packagist?
- No, the repository is Bitbucket-hosted and does not appear on Packagist. Consumption likely requires a vcs repository entry in composer.json plus SSH or deploy-key credentials wired into CI. This adds a Bitbucket dependency to every consuming pipeline.
- What deploy targets does nettt/nettt-tools assume?
- The deployment scripts are environment-coupled, and specific hosting assumptions such as Forge, Ploi, Envoyer, raw VPS over SSH, or container registries are not documented in the overview. You need to review the scripts to determine hard-coded providers. This drives most of the integration effort.
- Are the AI skills in nettt/nettt-tools just prompt files or a runtime dependency?
- The overview describes AI skills but does not specify whether they are prompt or markdown assets or require a specific agent runtime. If they are files only, integration is trivial; if they assume a tool-call contract, portability is limited. Clarify this with the maintainer before adopting.
- What are the production risks of using nettt/nettt-tools?
- The main risks are provenance and maintenance: zero stars, zero dependents, and a single maintainer with no visible release cadence. Deploy scripts hold production credentials and SSH access, so pin to tags rather than branches. Unversioned AI skill definitions can also cause prompt drift that is hard to regression-test.
- How do I test nettt/nettt-tools before using it in production?
- Pilot on one low-risk project, ideally a new Statamic site with no revenue dependency, and run it in parallel with your current process for a release cycle. Review the scripts for idempotency and rollback behavior on partial failure. Do not swap an existing working pipeline until the pilot proves stable.
- What are alternatives to nettt/nettt-tools for Laravel deployment?
- Established options include GitHub Actions, Laravel Forge, Envoyer, Ploi, and Deployer. These have broader community validation and audited release histories. Nettt Tools is strongest for teams already standardized on Laravel and Statamic that want one blessed internal path.
- Who maintains nettt/nettt-tools and is it actively updated?
- It appears to be a private or internal tool with a bus factor of one and no public issue history or release cadence. There is no community to absorb breakage. You should confirm ownership and update plans, or plan to fork and own it.
Weaver
How can I help you explore Laravel packages today?