feat(services): add Hi.Events one-click service

[vianmora]

Changes

• Added a new Hi.Events one-click service template

Issues

• fixes: Hi.Events: event management and ticket selling platform #5712

Category

• Adding new one click service

Screenshots or Video (if applicable)

AI Usage

• AI is used in the process of creating this PR

Steps to Test

Step 1 - Open Coolify dashboard.
Step 2 - Go to One-Click Services.
Step 3 - Search for Hi.Events.
Step 4 - Select the service and deploy it with default settings.
Step 5 - Wait for the deployment to complete.

Verify:

• The container is running.
• The service is accessible via the generated URL.
• Persistent data remains after container restart.
• Restart the service from the Coolify dashboard and confirm it comes back online correctly.

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have tested the changes thoroughly and am confident that they will work as expected without issues when the maintainer tests them

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
27064484	Triggered	Laravel APP_KEY	bdc73fb	.env.testing	View secret
26963785	Triggered	Company Email Password	548dc51	.claude/skills/pest-testing/SKILL.md	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[vianmora]

I think i'm a bit new, and don't really understand why there files from git workflow that came to my PR ^^
But here my contribution for adding Hi.Events in Coolify ;)

[ShadowArcanist]

I think i'm a bit new, and don't really understand why there files from git workflow that came to my PR ^^ But here my contribution for adding Hi.Events in Coolify ;)

Thanks for the PR!

The core maintainers pushed few commits directly to the v4.x branch and you have forked that v4.x branch, but the next branch doesn't have those commits so they were included on your PR.

[github-actions]

Hi @vianmora! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation

[vianmora]

And here's for the doc : coollabsio/coolify-docs#525