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

Update deployments.md to clarify the statement about zero-downtime deploys. #524

Merged
merged 3 commits into from
Feb 21, 2025

Conversation

dougjq
Copy link
Contributor

@dougjq dougjq commented Oct 21, 2024

Here's a simple improvement that should support developers working with managers who may read the docs without realizing that database migrations are separate and may require downtime.

If I'm wrong in anything I've written, please edit or reject. This did not take long.

…ployment. Support developers working with managers who may read the docs without realizing that database migrations are separate and may require downtime.
Co-authored-by: Scott Walkinshaw <[email protected]>
@retlehs
Copy link
Member

retlehs commented Jan 23, 2025

Thank you for the PR! I'd like to also at least mention which file they would want to be modifying to handle migrations, which would likely be build-after.yml (for folks using Acorn, this is where they would want to run Laravel migrations)

Are you on Roots Discourse? If so, I'd love to get you added to an author on this docs page

@dougjq
Copy link
Contributor Author

dougjq commented Feb 13, 2025

I've signed up for roots discourse just now, username dougjq.

@retlehs retlehs merged commit 5923b48 into roots:docs Feb 21, 2025
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants