feat: initial release

Author: frugan-dev

.env.dist

@@ -0,0 +1,48 @@
+DB_HOST=
+DB_NAME=
+DB_USER=
+DB_PASSWORD=''
+DB_CHARSET=utf8mb4
+DB_COLLATE=
+DB_PREFIX=
+
+WP_ENV=production
+
+WP_DEBUG=false
+WP_DEBUG_LOG=false
+WP_DEBUG_DISPLAY=false
+SCRIPT_DEBUG=false
+
+# NOTE: This will have a performance impact on your site, so make sure to turn this off when you aren’t debugging.
+SAVEQUERIES=false
+
+# Generate your keys here: https://roots.io/salts.html
+AUTH_KEY=''
+SECURE_AUTH_KEY=''
+LOGGED_IN_KEY=''
+NONCE_KEY=''
+AUTH_SALT=''
+SECURE_AUTH_SALT=''
+LOGGED_IN_SALT=''
+NONCE_SALT=''
+
+# disallows installation/updating of any theme or plugin
+DISALLOW_FILE_MODS=false
+DISALLOW_FILE_EDIT=true
+
+DISABLE_WP_CRON=false
+
+# false, true, minor
+WP_AUTO_UPDATE_CORE=true
+
+# https://elementor.com/help/requirements/
+# WP Memory limit of 256 MB (Elementor and Elementor Pro only), 512 MB recommended, 768 MB for best performance.
+# default = 40M (single site), 64M (multisite)
+WP_MEMORY_LIMIT=512M
+
+# default = 256M
+WP_MAX_MEMORY_LIMIT=512M
+
+# https://wordpress.org/support/article/editing-wp-config-php/
+# 'direct', 'ssh2', 'ftpext', 'ftpsockets' or false
+FS_METHOD=false

.gitattributes

@@ -0,0 +1,5 @@
+# Exclude files from Composer package archives
+/.github export-ignore
+/.releaserc.json export-ignore
+/codecov.yml export-ignore
+/commitlint.config.mjs export-ignore

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project maintainer using any of the [private contact addresses](https://github.com/frugan-dev). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
+
+For answers to common questions about this code of conduct, see <https://www.contributor-covenant.org/faq>

.github/CONTRIBUTING.md

@@ -0,0 +1,234 @@
+# Contributing
+
+Thank you for considering contributing! This document outlines the process for contributing to this project.
+
+When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
+
+Please note we have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Development Workflow
+
+We use [git-flow workflow](https://danielkummer.github.io/git-flow-cheatsheet/) and [conventional commits](https://www.conventionalcommits.org).
+
+### Branch Structure
+- `main` - Production-ready code
+- `develop` - Development branch
+- `feature/*` - New features
+- `bugfix/*` - Bug fixes
+- `hotfix/*` - Critical production fixes
+
+### Getting Started
+
+1. Fork the repository
+2. Clone your fork: `git clone https://github.com/your-username/wp-boot.git`
+3. Create a feature branch: `git checkout -b feature/your-feature-name`
+4. Install dependencies: `composer install`
+5. Make your changes
+6. Run tests: `composer test`
+7. Run quality checks: `composer qa`
+8. Commit using conventional commits
+9. Push and create a pull request
+
+## Development Setup
+
+### Requirements
+- PHP 8.0 or higher
+- Composer
+- Git
+
+### Installation
+```bash
+git clone https://github.com/wp-spaghetti/wp-boot.git
+cd wp-boot
+composer install
+```
+
+### Running Tests
+```bash
+# Run all tests
+composer test
+
+# Run specific test suite
+vendor/bin/phpunit tests/FooTest.php
+
+# Run with coverage
+vendor/bin/phpunit --coverage-html coverage/
+```
+
+### Code Quality
+```bash
+# Run all quality checks
+composer quality
+
+# Individual tools
+composer lint          # Linters
+composer analysis      # Static analysis
+composer security      # Security check
+composer quality       # Code quality
+```
+
+## Coding Standards
+
+### PHP Standards
+- Follow PSR-12 coding standard
+- Use strict typing: `declare(strict_types=1);`
+- Document all public methods with PHPDoc
+- Use meaningful variable and method names
+
+### Commit Messages
+We use [Conventional Commits](https://www.conventionalcommits.org/):
+
+```
+type(scope): description
+
+[optional body]
+
+[optional footer]
+```
+
+**Types:**
+- `feat:` New features
+- `fix:` Bug fixes
+- `docs:` Documentation changes
+- `style:` Code style changes (no logic changes)
+- `refactor:` Code refactoring
+- `test:` Adding or updating tests
+- `chore:` Maintenance tasks
+
+**Examples:**
+```
+feat(environment): add support for custom environment detection
+fix(docker): improve container detection accuracy
+docs(readme): update installation instructions
+test(hooks): add comprehensive hook testing
+```
+
+### Code Style
+```php
+<?php
+
+declare(strict_types=1);
+
+namespace WpSpaghetti\ExampleNamespace;
+
+/**
+ * Class documentation.
+ */
+class ExampleClass
+{
+    /**
+     * Method documentation.
+     */
+    public function exampleMethod(string $param): bool
+    {
+        // Method implementation
+        return true;
+    }
+}
+```
+
+## Testing Guidelines
+
+### Test Structure
+- Unit tests in `tests/` directory
+- Test files should end with `Test.php`
+- Use descriptive test method names
+- Include both positive and negative test cases
+
+### Test Example
+```php
+public function testMethodReturnsExpectedValue(): void
+{
+    $result = ExampleClass::get('TEST_VAR', 'default');
+    self::assertSame('expected', $result);
+}
+```
+
+### Mock Data
+Use the provided mock functions for testing:
+- `set_mock_*()`
+
+## Documentation
+
+### Code Documentation
+- All public methods must have PHPDoc blocks
+- Include `@param` and `@return` annotations
+- Document complex logic with inline comments
+- Use clear, concise language
+
+### README Updates
+When adding new features:
+- Update the feature list
+- Add usage examples
+- Update the API reference if needed
+
+## Pull Request Process
+
+1. **Create Feature Branch**
+   ```bash
+   git checkout develop
+   git checkout -b feature/your-feature
+   ```
+
+2. **Make Changes**
+   - Write code following the standards above
+   - Add/update tests for your changes
+   - Update documentation if needed
+
+3. **Test Your Changes**
+   ```bash
+   composer quality  # Run all quality checks
+   composer test     # Run all tests
+   ```
+
+4. **Commit Changes**
+   ```bash
+   git add .
+   git commit -m "feat: add new feature description"
+   ```
+
+5. **Push and Create PR**
+   ```bash
+   git push origin feature/your-feature
+   ```
+   Then create a pull request against the `develop` branch.
+
+### PR Requirements
+- All tests must pass
+- Code coverage should not decrease
+- Follow the PR template
+- Link to related issues
+- Use conventional commit messages
+
+## Release Process
+
+Releases are automated through GitHub Actions:
+
+1. Merge to `main` triggers release workflow
+2. Conventional commits determine version bump
+3. Changelog is automatically updated
+4. GitHub release is created
+5. Packagist is notified
+
+## Security
+
+If you discover a security vulnerability, please follow our [Security Policy](SECURITY.md).
+
+## Questions?
+
+- Create an issue for questions about usage
+- Join discussions for feature planning
+- Contact maintainers for sensitive issues
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the GPL-3.0-or-later license.
+
+## Recognition
+
+Contributors will be recognized in:
+- GitHub contributors list
+- Release notes for significant contributions
+- README acknowledgments for major features
+
+Thank you for contributing! 🎉

.github/CONTRIBUTORS.md

@@ -0,0 +1,3 @@
+# Contributors
+
+- [Frugan](https://github.com/frugan-dev) - Creator and main maintainer

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# These are supported funding model platforms
+
+github: [frugan-dev]
+buy_me_a_coffee: frugan

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: 'bug'
+assignees: ''
+---
+
+## Bug Description
+A clear and concise description of what the bug is.
+
+## To Reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected Behavior
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+A clear and concise description of what actually happened.
+
+## Environment
+- PHP Version: [e.g. 8.1]
+- WordPress Version: [e.g. 6.4]
+- WP Env Version: [e.g. 1.0.0]
+- Environment Type: [e.g. Docker, local, production]
+
+## Configuration
+```php
+// Any relevant configuration or code snippets
+```
+
+## Error Messages
+```
+Any error messages or logs
+```
+
+## Screenshots
+If applicable, add screenshots to help explain your problem.
+
+## Additional Context
+Add any other context about the problem here.