odac 0.9.0

package/CHANGELOG.md

@@ -0,0 +1,181 @@
+### ⚙️ Engine Tuning
+
+- Modular Config
+- New default web template
+
+### ✨ What's New
+
+- add <candy:login> component for zero-config registration
+- add <candy:register> component for zero-config registration
+- Environment variable support
+- **Framework:** Support multiple validation checks per field
+- HTTP2 & Server-Sent Events (SSE) Support
+- Modernize view template syntax with <candy> tags
+- No-Code AJAX Navigation
+
+### 📚 Documentation
+
+- Add examples for complex MySQL where conditions
+- Expand and update view system documentation
+- Revamp database docs: connection and queries
+
+### 🛠️ Fixes & Improvements
+
+- Added config module to candy debug
+- Improve config force save and migration verification
+
+
+
+---
+
+Powered by [🍭 CandyPack](https://candypack.dev)
+
+### ⚙️ Engine Tuning
+
+- Refactor SSL certificate generation and error handling
+
+### ✨ What's New
+
+- Development Server Mode
+- **Framework:** Custom Cron Jobs
+
+### 📚 Documentation
+
+- Simplify and standardize documentation titles
+
+### 🛠️ Fixes & Improvements
+
+- Add CAA record support and default Let's Encrypt CAA
+- Enhance system DNS config to use public resolvers
+- Handle systemd-resolved conflict on DNS port 53
+- Improve external IP detection with multiple fallbacks
+- Log stderr output to log buffer with timestamp
+- Make husky prepare script non-failing
+- Skip rate limiting for localhost in DNS requests
+
+
+
+---
+
+Powered by [🍭 CandyPack](https://candypack.dev)
+
+### 🛠️ Fixes & Improvements
+
+- Server Startup
+
+
+
+---
+
+Powered by [🍭 CandyPack](https://candypack.dev)
+
+### Refactor
+
+- Improve IMAP and SMTP authentication and TLS handling
+
+### ⚙️ Engine Tuning
+
+- Improve error handling for HTTP/HTTPS server startup
+- Refactor documentation files
+
+### ✨ What's New
+
+- Added 'candy service delete' command.
+- Added 'candy subdomain delete' command.
+- Added CLI prefix arguments support
+- CLI Mouse Support
+- **cli:** Add Progress-Based Output
+
+### 🛠️ Fixes & Improvements
+
+- Fix module instantiation and nullish services handling
+- Limit log and error buffer sizes in Web and Watchdog
+
+---
+
+Powered by [🍭 CandyPack](https://candypack.dev)
+
+**v**
+
+### ✨ What's New
+
+- Added 'candy web delete' command.
+- Added German, Spanish, French, Portuguese, Russian, and Chinese language support for CLI
+
+### 🛠️ Fixes & Improvements
+
+- DNS Server Improvements
+- Fixed website creation problem
+- **Framework:** Add error handling for config file parsing
+- IMAP Server Improvements
+- Refactor website creation and config handling
+- **Server:** Logs fixed
+- SMTP Server Improvements
+- Web Server Improvements
+
+---
+
+Powered by [🍭 CandyPack](https://candypack.dev)
+
+**v**
+
+## [0.5.0](https://github.com/CandyPack/CandyPack/compare/v0.4.1...v0.5.0) (2025-09-02)
+
+- add view helper to page and authPage methods [#20](https://https://github.com/CandyPack/CandyPack/pull/20) ([](https://github.com/CandyPack/CandyPack/commit/863eaf35950831dd1166b6b2d0a50f48c19af508)), closes [#20](https://github.com/CandyPack/CandyPack/issues/20)
+- merge branch 'main' into dev-1 ([](https://github.com/CandyPack/CandyPack/commit/5c96b1e0e5e0a3a86172ef6ad047cdf6f0c5c029))
+- merge pull request #14 from CandyPack/doc/update-contribution-guidelines ([](https://github.com/CandyPack/CandyPack/commit/eb92bdf66537c5a973629b99762424e31d8fa3a1)), closes [#14](https://github.com/CandyPack/CandyPack/issues/14)
+- merge pull request #16 from CandyPack/feat/custom-semantic-release-notes ([](https://github.com/CandyPack/CandyPack/commit/3ea998e24c27e03878258ac0de8563223dced2f8)), closes [#16](https://github.com/CandyPack/CandyPack/issues/16)
+- merge pull request #21 from CandyPack/dev-1 ([](https://github.com/CandyPack/CandyPack/commit/ae87fd8d50a226d854a8b85345558d7d5b7e81f9)), closes [#21](https://github.com/CandyPack/CandyPack/issues/21)
+- merge pull request #23 from CandyPack/dev ([](https://github.com/CandyPack/CandyPack/commit/b28a237ea070bc66f9ea3dbc2efa967e4d73ab27)), closes [#23](https://github.com/CandyPack/CandyPack/issues/23)
+- merge pull request #25 from CandyPack/dev ([](https://github.com/CandyPack/CandyPack/commit/b9cb9127d64c80d03c407052124b40da86b7caec)), closes [#25](https://github.com/CandyPack/CandyPack/issues/25)
+- refactor server restart and initialization logic ([](https://github.com/CandyPack/CandyPack/commit/2e7a23fce515b6a6e6fdfb58e91810d558001c66))
+
+### ⚡️ Performance Upgrades
+
+- core Process Module ([](https://github.com/CandyPack/CandyPack/commit/59ece15756bfb80a3ce8a430d60106ec8b9cea7e))
+
+### ✨ What's New
+
+- **release:** customize semantic-release notes generation ([](https://github.com/CandyPack/CandyPack/commit/70ba94ef010c10609cce69d2dd7fc32eb8ddd157))
+- **server:** new Logging Module ([](https://github.com/CandyPack/CandyPack/commit/70699006a36dbcce1f8de3ad549ee6000cd6e3a1))
+- synchronize main with dev branch ([](https://github.com/CandyPack/CandyPack/commit/654ecd33e9296f3753b95f11568f9d289f0d5a23))
+
+### 🎨 Style
+
+- add PR and author attribution to release notes [#17](https://https://github.com/CandyPack/CandyPack/pull/17) ([](https://github.com/CandyPack/CandyPack/commit/8ef3e77edb3fc3f6de4582bacf8c3088f5941b76)), closes [#17](https://github.com/CandyPack/CandyPack/issues/17) [#1234](https://github.com/CandyPack/CandyPack/issues/1234) [#1234](https://github.com/CandyPack/CandyPack/issues/1234)
+
+### 📚 Documentation
+
+- add AGENTS.md and update contribution guidelines ([](https://github.com/CandyPack/CandyPack/commit/2ef7dcb125eb9b341ecf209cd6f87dc6e0873389))
+- framework Docs ([](https://github.com/CandyPack/CandyPack/commit/cd7a1cec6ebecc5748bae3ccd0dd934ddf77c3fa))
+- server documentation ([](https://github.com/CandyPack/CandyPack/commit/27eb89a0f9c5d17c0364112743f3a032d2999195))
+- update AGENTS.md with detailed developer guide [#18](https://https://github.com/CandyPack/CandyPack/pull/18) ([](https://github.com/CandyPack/CandyPack/commit/65a05649ea61ac1d29ae73e3f27dabe0d82425cd)), closes [#18](https://github.com/CandyPack/CandyPack/issues/18)
+
+### 🛠️ Fixes & Improvements
+
+- add missing conventional-changelog-conventionalcommits dependency [#22](https://https://github.com/CandyPack/CandyPack/pull/22) ([](https://github.com/CandyPack/CandyPack/commit/8f8a64fe3a81a5c9015e62755013d141571e5f0d)), closes [#22](https://github.com/CandyPack/CandyPack/issues/22)
+- **CLI:** fixed CLI Commands ([](https://github.com/CandyPack/CandyPack/commit/44c8ef7a2aca9ebdf82317b20dc3c39728cf2676))
+- **Framework:** no Controller View ([](https://github.com/CandyPack/CandyPack/commit/ae73ae793be0e3b6b6d95eaeb75ba981f0eb49f5))
+- rebooting ([](https://github.com/CandyPack/CandyPack/commit/9ab17df2a39621be0429cc3ffd52f0326dc8c64a))
+- resolve semantic-release configuration and dependency errors [#24](https://https://github.com/CandyPack/CandyPack/pull/24) ([](https://github.com/CandyPack/CandyPack/commit/b6359b4687f1f15cbb1847e82d49a998e74f5dde)), closes [#24](https://github.com/CandyPack/CandyPack/issues/24)
+
+## [0.4.1](https://github.com/CandyPack/CandyPack/compare/v0.4.0...v0.4.1) (2025-08-31)
+
+### Bug Fixes
+
+- **server:** Refactor server restart and initialization logic ([#15](https://github.com/CandyPack/CandyPack/issues/15)) ([6cc688e](https://github.com/CandyPack/CandyPack/commit/6cc688ed95212fa73d022e3f2d8e773a17fe299e))
+
+# [0.4.0](https://github.com/CandyPack/CandyPack/compare/v0.3.1...v0.4.0) (2025-08-28)
+
+### Bug Fixes
+
+- Correct license and supported version in docs ([1af458e](https://github.com/CandyPack/CandyPack/commit/1af458ead8a1a577e8e4c6c45d8cae4ee1432d5c))
+- Update auto-generated PR text to English ([27bab61](https://github.com/CandyPack/CandyPack/commit/27bab61461d65737f95e89737bda06753de3bfc5))
+
+### Features
+
+- Add Jest for testing ([4e51bbb](https://github.com/CandyPack/CandyPack/commit/4e51bbb1295d44b14f64e661019ac7a526fa96bb))
+- Add Jest for unit testing and code coverage ([1bfe78e](https://github.com/CandyPack/CandyPack/commit/1bfe78eeabc0af1178ba9bc678ab8a2eaa7d9bf8))
+- add semantic-release ([7a88e9e](https://github.com/CandyPack/CandyPack/commit/7a88e9eb3cee12d6d316c776e7d88e8de6b26c55))
+- add semantic-release with npm publishing ([5c2568d](https://github.com/CandyPack/CandyPack/commit/5c2568dac9ca6284718e087ce67a519a21bfe1c5))
+- Complete project refactor and feature enhancement ([d3bcc19](https://github.com/CandyPack/CandyPack/commit/d3bcc1995af8f0548a0bbd8c0396db6775d4b5cf))

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible 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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at security@candypack.dev. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,63 @@
+# Contributing to CandyPack
+
+First off, thank you for considering contributing to CandyPack! It's people like you that make CandyPack such a great tool.
+
+This project and everyone participating in it is governed by the [CandyPack Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to security@candypack.dev.
+
+## How Can I Contribute?
+
+There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into CandyPack itself.
+
+### Reporting Bugs
+
+Before creating a bug report, please check the [issues list](https://github.com/CandyPack/CandyPack/issues) to see if the bug has already been reported. If it has, please add a comment to the existing issue instead of creating a new one.
+
+When you are creating a bug report, please include as many details as possible. Fill out the required template, the information it asks for helps us resolve issues faster.
+
+### Suggesting Enhancements
+
+If you have an idea for a new feature or an improvement to an existing one, please open an issue with the "feature request" label. Provide a clear and detailed explanation of the feature, why it's needed, and how it should work.
+
+### Your First Code Contribution
+
+Unsure where to begin contributing to CandyPack? You can start by looking through `good first issue` and `help wanted` issues:
+
+*   [Good first issues](https://github.com/CandyPack/CandyPack/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) - issues which should only require a few lines of code, and a test or two.
+*   [Help wanted issues](https://github.com/CandyPack/CandyPack/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) - issues which should be a bit more involved than `good first issue` issues.
+
+### Development Workflow
+
+Our development process follows a branching model similar to Git Flow. This helps us keep the `main` branch stable and ready for release at all times.
+
+1.  **Branching:**
+    *   All new features or bug fixes should be developed on a feature branch.
+    *   Create your feature branch from the `dev` branch: `git checkout -b your-feature-name dev`.
+    *   Never create a feature branch directly from `main`.
+
+2.  **Making Changes:**
+    *   Make your code changes, ensuring you follow the project's coding standards.
+    *   Add tests for any new code.
+    *   Ensure all tests pass (`npm test`) and the code lints correctly.
+
+3.  **Committing Changes:**
+    *   This project uses **Conventional Commits**. This is a requirement for our automated release process.
+    *   Your commit messages must be in the format: `<type>(<scope>): <subject>`.
+        *   **type:** `feat` (new feature), `fix` (bug fix), `docs`, `style`, `refactor`, `test`, `chore`.
+        *   **scope:** (Optional) The part of the project you're working on (e.g., `server`, `framework`).
+    *   Example: `feat(server): add rate limiting to API endpoints`
+
+4.  **Submitting a Pull Request:**
+    *   Once your feature is complete, push your branch to your fork.
+    *   Open a Pull Request (PR) from your feature branch to the `dev` branch of the main repository.
+    *   Provide a clear description of the changes in your PR.
+    *   After your PR is reviewed and merged, you can safely delete your feature branch.
+
+The `main` branch is only updated by merging `dev` into it during a new release. Direct pushes or PRs to `main` are not permitted.
+
+## Code Style
+
+All JavaScript must adhere to the style defined in the `.prettierrc` file. The linter will automatically check this.
+
+---
+
+We look forward to your contributions!