Skip to content
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.

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

Rework Build and Deploy page to include pre_start command #3937

Open
AnouckColson opened this issue Apr 11, 2024 · 1 comment · Fixed by #3970
Open

Rework Build and Deploy page to include pre_start command #3937

AnouckColson opened this issue Apr 11, 2024 · 1 comment · Fixed by #3970

Comments

@AnouckColson
Copy link
Collaborator

AnouckColson commented Apr 11, 2024

Where on docs.platform.sh should be changed?

https://docs.platform.sh/learn/overview/build-deploy.html

What exactly should be updated?

Further information on the pre_start command is needed (similar to the info provided on each hook in the table on https://docs.platform.sh/create-apps/hooks/hooks-comparison.html). There is confusion as to how it works and where it belongs in the whole build and deploy flow, so we need to make that clear.

Atm we only have mention of the pre_start command on https://docs.platform.sh/create-apps/hooks/hooks-comparison.html#deploy-hook with a link to the configuration side on https://docs.platform.sh/create-apps/app-reference/single-runtime-image.html#web-commands .

Additional context

See thread for screenshots with client questions/showing the confusion.

No response

@AnouckColson AnouckColson changed the title Rework Build and Deploy page to include pre_startcommand Rework Build and Deploy page to include pre_start command Apr 24, 2024
@chadwcarlson
Copy link
Collaborator

A typical example would be to regenerate / warm up cache

web:
    commands:
        pre_start: 'bash warmup-cache'

@chadwcarlson chadwcarlson reopened this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants