-
Notifications
You must be signed in to change notification settings - Fork 52
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
Vagrant setup is broken #10
Comments
tobemedia
added a commit
to tobemedia/proophessor-do-symfony
that referenced
this issue
Jul 21, 2017
fixes some of the issues listed in prooph#10
There is no more doctrine migration when symfony bundle is finished. The db
tables are created from the projectors instead.
…On Jul 21, 2017 16:37, "Tobias Berchtold" ***@***.***> wrote:
The vagrant setup is broken. I found multiple issues so consider updating
the vagrant and docker setup to fit the prooph/proophessor-do
configuration. Alternatively we could fix the issues in this repo by it
think it´s better to get in sync with the base repo.
- vagrant provision fails with "the input device is not a TTY" =>
remove "-i" argument from the docker run calls to get rid of
- can't open 'bin/setup_mysql.sh' => the file does not exist
- build prod assets during vagrant provisioning or change url in
"docs/installation/vagrant.md" to /app_dev.php
- run the doctrine migrations during vagrant provision
I´m gonna provide a pull request fixing some of the listed issues, but as
mentioned in #6
<#6> a better
concept is needed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAYEvAc-OKA5FjPXDtFZb5U_gKEpkv37ks5sQGNGgaJpZM4OfHd->
.
|
The Vagrant setup should be similar like in proophessor-do. I guess it's out of date due the new major prooph releases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The vagrant setup is broken. I found multiple issues so consider updating the vagrant and docker setup to fit the prooph/proophessor-do configuration. Alternatively we could fix the issues in this repo by it think it´s better to get in sync with the base repo.
I´m gonna provide a pull request fixing some of the listed issues, but as mentioned in #6 a better concept is needed.
The text was updated successfully, but these errors were encountered: