- You may see a 503 or a 502 error at a newly generated site's URL for a period of time.
ddev-live execcommands queue and cannot currently be run simultaneously, leading to long waiting times and CLI timeouts.
- When you make a change in the GitHub repo for a previously deployed site you do not have the ability to check on the status of the deployment from the CLI.
- It can take up to 3 seconds after site creation for the
ddev-live describecommand to succeed.
- Databases from deleted sites are not being cleaned up properly.
ddev-live push filesdoes not yet work with an archive of the entire files directory.
ddev-live push fileswill fail with the message "The access key ID you provided does not exist in our records." Please try your file push a few times and it should complete successfully.
Running into something that's not listed here? Support is here for you¶
Last update: 2020-10-19