Skip to content

docs(procfile): mention the 24 characters name limit #3865

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
EtienneM merged 1 commit into from
Jul 16, 2026
+5 −4
Merged

docs(procfile): mention the 24 characters name limit #3865

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions src/_posts/platform/app/2000-01-01-procfile.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
index: 11
title: Procfile
tags: internals process types procfile heroku
modified_at: 2026-04-29 00:00:00
modified_at: 2026-07-16 00:00:00
---

Procfile support is one of our
Expand Down Expand Up @@ -130,9 +130,10 @@ with the following format:
```

- `<process_type>` designates the name of the process type. It can only contain
alphanumerics (`[A-Za-z0-9]+`). Except this rule, you are free to name your
process type how you want: `heavyProcess`, `synchronizer`, `scheduler`,
`console`, `trex`... These are all examples of valid process type names.
alphanumerics (`[A-Za-z0-9]+`) and must be no longer than 24 characters.
Except these two rules, you are free to name your process type how you want:
`heavyProcess`, `synchronizer`, `scheduler`, `console`, `trex`... These are
all examples of valid process type names.
- `<command>` designates the command to run when a container of the specified
type is booted up. It can be any Bash command. Using environment variables in
the command is allowed, and even encouraged.
Expand Down