tezvyn:

Deploying to Heroku via Git

Source: interviewbeginner

WHAT IT TESTS: the git-push PaaS deploy flow and build manifests. OUTLINE: push to the remote, a buildpack detects the language, builds a slug, and runs the Procfile process. RED FLAG: confusing what declares dependencies versus the start command.

WHAT IT TESTS: how a git-based PaaS turns a push into a running app. ANSWER OUTLINE: you commit code plus manifest files, add the platform git remote, and push; the buildpack detects the language from files like requirements.txt or package.json, installs dependencies, compiles a slug, and starts the process named in the Procfile. Mention config vars for secrets and a runtime version file. RED FLAG: not knowing which file declares dependencies versus the start command, or putting credentials in the repo instead of config vars.

Read the original → interview

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

Deploying to Heroku via Git · Tezvyn