LaraEnv logo LaraEnv
On this page
Reporting bugs Feature requests Pull requests Building from source Code style Release process Community

Contributing

LaraEnv is an open project — the desktop app, the website and the CLI all live in public on GitHub. Bug reports, feature ideas and pull requests are welcome. This page covers what to do where.

Reporting bugs

  1. Search existing issues first — chances are it's already tracked.
  2. If not, open a new issue with: LaraEnv version (Help → About), Windows version, the exact steps to reproduce, and the relevant log slice from %APPDATA%\LaraEnv\logs\app.log.
  3. For service-specific issues (Nginx crashing, MySQL refusing to start, …), include the matching log from C:\laraenv\\logs\.

Feature requests

Open a GitHub Discussion under Ideas rather than an issue. That way other users can chime in before we commit to scope. Include: the problem you're hitting, why existing features don't solve it, and a rough sketch of how you'd like it to work.

Pull requests

  • Fork the repo and create a topic branch — feat/short-name or fix/short-name.
  • Keep PRs small and focused. One feature or one fix per PR.
  • Add or update tests when you touch logic. CI runs on every push.
  • Reference the issue in the PR description (Closes #123).
  • Be patient on review — this is a small team.

Building from source

  1. Clone git clone https://github.com/thayronarrais/laraenv.git.
  2. Install Rust (stable) and Node.js LTS.
  3. cd laraenv && cargo build for the CLI; cd ui && npm install && npm run dev for the dashboard.
  4. See README.md in the repo for the full dev-environment setup.

Code style

  • Rust — cargo fmt + cargo clippy -- -D warnings. No suppressions without a comment explaining why.
  • JS/TS — Prettier + ESLint, configs in repo. No any in new code.
  • PHP (this site) — Laravel Pint, PSR-12.
  • Commit messages follow Conventional Commits — feat(scope):, fix(scope):, …

Release process

Releases follow SemVer. The full process is documented in RELEASING.md. Roughly: tag vX.Y.Z → GitHub Actions builds the signed installer → release notes get published to the changelog automatically.

Community

  • GitHub Discussions — the primary place for questions, ideas and showcases.
  • Issues — bugs and concrete actionable work only.
  • Email — hello@laraenv.com for security disclosures or anything you'd rather not file publicly.