Notifications on a per project and per service basis
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I set up slack notifications and realized events (like App Deploy) are global for the entire dokploy application, and there is no way to configure a notification on a per project or per service basis.
Describe the solution you'd like
I would like to be able to limit a notification to specific projects and services. maybe even adding a match filter like "project_name/service_name" that accepts wildcards: "project/backend-" or "project_name/"
Describe alternatives you've considered
The only alternative is to use some other notification system outside of dokploy.
Additional context
Thanks for making dokploy great!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the existing Slack notification configuration and event delivery paths, then determine how project and service scope plus wildcard matching should be represented. Done means notifications can be limited to selected projects or services without affecting unrelated application events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100