- Notifications
You must be signed in to change notification settings - Fork18
db:download task : Read-only file system#31
-
I use deployer-extended-wp-composer with a roots-bedrock setup for all my wp projects and usually everything works nicely. Dev-env is powered by Recently, after an upgrade from As I understand the error, the process failed during the dumps trying to create a dir on the remote server ("mkdir" see error output above) ? But if I look at the dumps folder on the remote server, dumps are created. Everything work fine for Cmd and error output are: dep db:pull production➤ Executing task db:pull Any idea or advice ? |
BetaWas this translation helpful?Give feedback.
All reactions
if i add aWP_INSTANCE in .env, in addition ofINSTANCE..
IT WORKS !! (same for production and staging)
INSTANCE='development'WP_INSTANCE='development'It's strange, because WP_ENV is already defined in .env (and works in Bedrock), and as I can see in EnvDriver.php, it should also works, no ?
Replies: 6 comments
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
hi The config is now read from Also try to run the command with Could be that this folder is tried to be created locally because for some reason the instance name is wrongly read for local instance. |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
Hi, Thanks for your answer! Yes, Exception trace: The only thing I see is that I needed to customize the instances names, because of your default changes, and re- namespaceDeployer;require__DIR__ .'/vendor/autoload.php';new \SourceBroker\DeployerExtendedWordpressComposer\Loader();set('instance_local_name','development');set('instance_live_name','production');set('default_stage','staging');#(...) If I run +-------------+-------------------------+-------------+-------+------------------------------------------+| Host| Hostname| Stage| Roles| Deploy path|+-------------+-------------------------+-------------+-------+------------------------------------------+| production| prod.mywebsite.ch| production|| /mywebsite/app/wp|| staging| stage.mywebsite.ch| staging|| /mywebsite/app/wp|| development|| development|| /Users/xxx/LocalWebsites/mywebsite/app|+-------------+-------------------------+-------------+-------+------------------------------------------+Ok. Thanks again for your time. |
BetaWas this translation helpful?Give feedback.
All reactions
-
You should not touch |
BetaWas this translation helpful?Give feedback.
All reactions
-
What is the behaviour when you remove |
BetaWas this translation helpful?Give feedback.
All reactions
-
Ok I didn't know that. So I removed the "set default_instance". a |
BetaWas this translation helpful?Give feedback.
All reactions
-
if i add a It's strange, because WP_ENV is already defined in .env (and works in Bedrock), and as I can see in EnvDriver.php, it should also works, no ? |
BetaWas this translation helpful?Give feedback.
All reactions
This discussion was converted from issue #13 on September 20, 2024 11:58.