Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’m running a MERN application with separate frontend and backend components on DigitalOcean App Platform. I’ve set up a post-deploy job to notify a Discord channel about successful and unsuccessful deployments using a shell script running in a Docker container that triggers a webhook.
This part is working fine - I receive the notifications. However, since my app consists of both frontend and backend components, I get two notifications per deploy attempt (because both components are deployed automatically right after each other).
What I Need Help With
I would like to pass information about which component triggered the post-deploy job, so my notifications can specify:
✅ “Backend deploy successful” or “Frontend deploy successful” instead of just “Deploy successful” (twice).
✨ Nice-to-have: Include the commit hash of the deployed component (frontend/backend) in the notification.
What I Tried
So far, I was able to retrieve the app URL, but regarding the commit hash, I only managed to get the commit hash of the post-deploy job itself, not the commit of the actual deployed component.
In my post-deploy job configuration, I defined the following environment variables:
jobs:
- dockerfile_path: dockerfile
envs:
- key: URL
scope: RUN_AND_BUILD_TIME
value: ${APP_URL}
- key: COMMIT_HASH
scope: RUN_AND_BUILD_TIME
value: ${_self.COMMIT_HASH}
And I use them in the shell script like this:
URL=${URL}
COMMIT_HASH=${COMMIT_HASH}
What I Researched So Far
I’ve checked the following DigitalOcean documentation pages:
• Managing Jobs in App Platform
• Using Environment Variables in App Platform
However, I couldn’t find a clear way to pass the name of the app component triggering the post-deploy job or retrieve the commit hash of the deployed frontend/backend component instead of the post-deploy job’s commit hash.
Questions
How can I pass the name of the app component that triggered the post-deploy job?
How can I pass the commit hash of the deployed component (frontend/backend) instead of just the commit hash of the post-deploy job?
Thanks in advance for any insights! 🚀
9b4fd2e206f94883807d342760949f
Aron Gebregziabher
28d127198204464a8122522bc579c6
hackman.christine
Drillgon200
micktdj
micktdj
TTTTT TTTTT
TTTTT TTTTT
6f30e8e3d7df40c7ae6efdb0ea0058