aaaa

.editorconfig

@@ -3,13 +3,34 @@ root = true
 [*]
 charset = utf-8
 end_of_line = lf
-insert_final_newline = true
-indent_style = space
 indent_size = 4
+indent_style = space
+insert_final_newline = true
 trim_trailing_whitespace = true
 
 [*.md]
 trim_trailing_whitespace = false
 
 [*.{yml,yaml}]
 indent_size = 2
+
+[docker-compose.yml]
+indent_size = 2
+
+[*.php]
+indent_size = 4
+
+[*.blade.php]
+indent_size = 2
+
+[*.js]
+indent_size = 4
+
+[*.jsx]
+indent_size = 2
+
+[*.tsx]
+indent_size = 2
+
+[*.json]
+indent_size = 4

.env.example

@@ -1,9 +1,16 @@
-APP_NAME=Dashboard
+# This file (.env) stores sensitive environment variables.
+# Modifying these values can significantly impact your application's behavior.
+#
+# Proceed with caution:
+#  - Only edit if you have a clear understanding of the specific variable and its purpose.
+#  - Use the CtrlPanel or installer for most configuration changes whenever possible.
+#  - Keep a backup of this file before making any modifications.
+
+APP_NAME=CtrlPanel.gg
 APP_ENV=production
 APP_KEY=
 APP_DEBUG=false
 APP_URL=http://localhost
-#list with timezones https://www.php.net/manual/en/timezones.php
 APP_TIMEZONE=UTC
 
 DB_CONNECTION=mysql
@@ -13,59 +20,20 @@ DB_DATABASE=dashboard
 DB_USERNAME=dashboarduser
 DB_PASSWORD=
 
-#without a pterodactyl api token, this panel won't work!
-PTERODACTYL_TOKEN=
-
-#paypal details, you only need sandbox for testing! you can do this by setting the APP_ENV to local
-PAYPAL_SANDBOX_SECRET=
-PAYPAL_SANDBOX_CLIENT_ID=
-PAYPAL_SECRET=
-PAYPAL_CLIENT_ID=
-PAYPAL_EMAIL=
-
-#set-up for extra discord verification
-DISCORD_CLIENT_ID=
-DISCORD_CLIENT_SECRET=
-#set-up will join users automaticly to your discord
-DISCORD_BOT_TOKEN=
-DISCORD_GUILD_ID=
-#set-up will give the verified user the given role
-DISCORD_ROLE_ID=
-
-#nesseary URL's
-PTERODACTYL_URL=https://panel.controlpanel.gg
-PHPMYADMIN_URL=https://mysql.controlpanel.gg #optional. remove to remove database button
-DISCORD_INVITE_URL=https://discord.gg/vrUYdxG4wZ
-
-#GOOGLE RECAPTCHA
-RECAPTCHA_SITE_KEY=6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI
-RECAPTCHA_SECRET_KEY=6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe
-
-MAIL_MAILER=smtp
-MAIL_HOST=mailhog
-MAIL_PORT=1025
-MAIL_USERNAME=null
-MAIL_PASSWORD=null
-MAIL_ENCRYPTION=null
-MAIL_FROM_ADDRESS=null
-MAIL_FROM_NAME="${APP_NAME}"
+MEMCACHED_HOST=127.0.0.1
 
+REDIS_HOST=127.0.0.1
+REDIS_PASSWORD=null
+REDIS_PORT=6379
 
-#you can leave everything below the way it is
 LOG_CHANNEL=stack
-LOG_LEVEL=debug
+LOG_LEVEL=warning
 
-BROADCAST_DRIVER=log
 CACHE_DRIVER=file
 QUEUE_CONNECTION=database
 SESSION_DRIVER=file
 SESSION_LIFETIME=120
-
-MEMCACHED_HOST=127.0.0.1
-
-REDIS_HOST=127.0.0.1
-REDIS_PASSWORD=null
-REDIS_PORT=6379
+SETTINGS_CACHE_ENABLED=true
 
 AWS_ACCESS_KEY_ID=
 AWS_SECRET_ACCESS_KEY=
@@ -79,3 +47,23 @@ PUSHER_APP_CLUSTER=mt1
 
 MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
 MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"
+
+# Changing these settings after installation will have
+# no effect. They can only be applied during the first
+# database migration. If you need to change these settings,
+# go to the Settings page of your CtrlPanel.
+
+RECAPTCHA_SITE_KEY=6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI
+RECAPTCHA_SECRET_KEY=6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe
+
+DISCORD_CLIENT_ID=
+DISCORD_CLIENT_SECRET=
+
+MAIL_MAILER=smtp
+MAIL_HOST=null
+MAIL_PORT=465
+MAIL_ENCRYPTION=null
+MAIL_USERNAME=null
+MAIL_PASSWORD=null
+MAIL_FROM_ADDRESS=null
+MAIL_FROM_NAME="${APP_NAME}"

.gitattributes

@@ -1,5 +1,10 @@
+# Automatically detect text files
 * text=auto
+
+# Vendored files for specific languages
 *.css linguist-vendored
 *.scss linguist-vendored
 *.js linguist-vendored
+
+# Ignore CHANGELOG.md when exporting
 CHANGELOG.md export-ignore

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,81 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as contributors and maintainers of CtrlPanel.gg pledge to make
+participation in our project 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,
+caste, color, 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:
+
+- 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:
+
+- 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 electronic
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Scope
+
+This Code of Conduct applies within all GitHub spaces of this project,
+including issues, pull requests, discussions, and commit messages. It applies
+when an individual is officially representing the project in any capacity.
+
+## Reporting
+
+**Bugs and feature requests:** Open a [GitHub Issue][issues].
+
+**Security vulnerabilities:** Report privately via
+[GitHub Security Advisories][advisories] and send a direct message
+to the project owner `1day2die` on Discord. Do **not** open a public issue,
+comment, or discussion - and do **not** discuss the vulnerability publicly
+anywhere until an official writeup has been published by the maintainers.
+
+**Code of Conduct violations:** Send a direct message to the project owner
+`1day2die` on Discord, briefly describing the incident. Do not open a public
+issue for conduct-related matters.
+
+All reports will be reviewed and investigated promptly and fairly. The
+privacy and security of the reporter will be respected.
+
+[issues]: https://github.com/CtrlPanel-gg/panel/issues
+[advisories]: https://github.com/CtrlPanel-gg/panel/security/advisories/new
+
+## Enforcement
+
+Maintainers are responsible for clarifying and enforcing this Code of Conduct.
+
+Enforcement follows a two-step process:
+
+1. **Warning** - A private written warning is issued, with clarification of
+   the violation and a request to change the behavior.
+2. **Ban** - A permanent ban from all GitHub spaces of the project if the
+   behavior continues or if the initial violation is severe enough to warrant
+   immediate action.
+
+## Attribution
+
+This Code of Conduct is adapted from the
+[Contributor Covenant, version 2.1][covenant].
+
+[covenant]: https://www.contributor-covenant.org/version/2/1/code_of_conduct/

.github/CONTRIBUTING.md

@@ -0,0 +1,154 @@
+# Contributing to CtrlPanel.gg
+
+Thank you for your interest in contributing to CtrlPanel.gg. This document
+outlines the process and standards we expect contributors to follow.
+
+## Code of Conduct
+
+Please adhere to our [Code of Conduct](https://github.com/Ctrlpanel-gg/panel/blob/development/.github/CODE_OF_CONDUCT.md)
+and our [Contributor License](https://github.com/Ctrlpanel-gg/panel/blob/development/CONTRIBUTOR_LICENSE_AGREEMENT)
+in all your interactions with the project.
+
+## Contributor License Agreement
+
+All contributions require a signed CLA. When you open a pull request for
+the first time, a GitHub Action will automatically prompt you to sign it.
+Your PR cannot be merged until the CLA is signed.
+
+You can review the full agreement here:
+[Contributor License Agreement](https://github.com/Ctrlpanel-gg/panel/blob/development/CONTRIBUTOR_LICENSE_AGREEMENT).
+
+## Branches
+
+| Branch        | Purpose                                      |
+|---------------|----------------------------------------------|
+| `main`        | Stable releases only - **never push here**   |
+| `development` | All active work targets this branch          |
+
+> [!CAUTION]
+> Direct pushes to `main` are not allowed under any circumstances,
+> including for maintainers.
+
+External contributors work via fork. Maintainers may work directly in the
+repository, but all changes must go through a pull request targeting
+`development`.
+
+## Reporting Bugs
+
+Before opening a bug report, please check existing issues to avoid
+duplicates. When ready, open a [GitHub Issue][issues] using the bug report
+template. Include as much detail as possible: steps to reproduce, expected
+behavior, actual behavior, and your environment.
+
+## Suggesting Features
+
+Open a [GitHub Issue][issues] using the feature request template. Describe
+the problem you are trying to solve and your proposed solution. For larger
+changes, it is strongly recommended to discuss the idea in an issue before
+investing time in implementation.
+
+## Submitting a Pull Request
+
+### For bug fixes
+
+You may open a pull request directly without a prior issue, though linking
+to an existing issue is appreciated if one exists.
+
+### For new features or significant changes
+
+Open an issue first and wait for feedback from maintainers before starting
+work. This avoids the risk of your PR being rejected due to misaligned
+goals.
+
+### PR checklist
+
+Before submitting, make sure your pull request:
+
+- [ ] Targets the `development` branch, not `main`
+- [ ] Follows the commit message format described below
+- [ ] Adheres to PSR-12 coding standards
+- [ ] Includes a clear description of what was changed and why
+- [ ] Does not introduce unnecessary dependencies
+
+### Pull request template
+
+All PRs use the repository's pull request template. Fill it out completely -
+incomplete submissions may be closed without review.
+
+## Commit Messages
+
+This project follows the [Conventional Commits][conventional] specification.
+
+Format: `<type>(<optional scope>): <description>`
+
+| Type       | When to use                                      |
+|------------|--------------------------------------------------|
+| `feat`     | A new feature                                    |
+| `fix`      | A bug fix                                        |
+| `docs`     | Documentation changes only                       |
+| `style`    | Formatting, missing semicolons, etc.             |
+| `refactor` | Code change that is neither a fix nor a feature  |
+| `chore`    | Build process, dependency updates, tooling       |
+| `revert`   | Reverts a previous commit                        |
+
+Examples:
+
+```
+feat(billing): add invoice PDF export
+fix(auth): resolve session expiry on password reset
+chore: update composer dependencies
+```
+
+Breaking changes must include a `!` after the type and a `BREAKING CHANGE:`
+footer:
+
+```
+feat!: drop support for PHP 7.x
+
+BREAKING CHANGE: minimum required PHP version is now 8.1
+```
+
+## Coding Standards
+
+All PHP code must follow [PSR-12][psr12]. Run your code through a compatible
+linter before submitting. PRs that violate PSR-12 will be requested to
+make changes before merging.
+
+## Use of AI Tools
+
+AI-assisted development is permitted, but subject to the following rules:
+
+- **Disclosure is required.** If any part of your contribution was written
+  or significantly influenced by an AI tool, you must state this in your
+  pull request description.
+- **You are responsible for the output.** AI-generated code must be
+  reviewed, understood, and tested by you before submission. Do not submit
+  code you cannot explain or vouch for.
+- **AI is an assistant, not a contributor.** Submitting AI-generated code
+  without meaningful human oversight and validation is not acceptable.
+- **Verify affected functionality.** Any code touched or generated by an AI
+  tool must be manually verified by you to ensure nothing is broken,
+  including edge cases and related features.
+
+Pull requests that appear to be entirely AI-generated with no meaningful
+human review may be closed without merging.
+
+## Tests
+
+There are currently no tests in the project. Test coverage is planned for
+a future release. You are not required to write tests with your PR at
+this time.
+
+## Localization
+
+Please read our [Localization Guide](https://github.com/Ctrlpanel-gg/panel/blob/development/lang/README.md)
+on how to manage and add localization to the project.
+
+## Security Vulnerabilities
+
+Do not open a public issue for security vulnerabilities. See
+[SECURITY.md](SECURITY.md) for the responsible disclosure process.
+
+[issues]: https://github.com/ctrlpanel-gg/panel/issues
+[conventional]: https://www.conventionalcommits.org/
+[psr12]: https://www.php-fig.org/psr/psr-12/

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+github: CtrlPanel-gg
+patreon: 1day2die
+ko_fi: 1day2die