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

Skip warning prompts in migrations when not in a TTY #12587

Closed
sneak opened this issue Dec 9, 2019 · 3 comments · Fixed by #12969
Closed

Skip warning prompts in migrations when not in a TTY #12587

sneak opened this issue Dec 9, 2019 · 3 comments · Fixed by #12969

Comments

@sneak
Copy link

sneak commented Dec 9, 2019

Pitch

First installs incur 3 different 10s delays applying initial database migrations. It would be awesome if first installs could set an environment variable to skip these delays when deploying new instances.

@sneak
Copy link
Author

sneak commented Dec 9, 2019

Perhaps it could be even simpler: check to see if stdout is a tty, and skip the countdown if it is not (e.g. during migrations from a startup script).

@Gargron
Copy link
Member

Gargron commented Dec 9, 2019

Don’t use db:migrate for first installs! db:setup is faster! It uses db:schema:load which just creates the latest schema right away instead of running migrations one by one

@Gargron Gargron closed this as completed Dec 9, 2019
@sneak
Copy link
Author

sneak commented Dec 9, 2019

Well, it shouldn't do a 10s delay in any case even for a migration if stdout is not a tty.

@Gargron Gargron changed the title Environment variable for skipping 10s migration delays for first installs Skip warning prompts in migrations when not in a TTY Dec 9, 2019
@Gargron Gargron reopened this Dec 9, 2019
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 a pull request may close this issue.

2 participants