docs
docs copied to clipboard
docker
ENGDOCS-999
Changes the references to 'Share' to reflect the changes to the functionality in the Dev Envs tab
Still to do - update screenshot
Deploy Preview for docsdocker ready!
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | b3ee5bd49dee6ce87108d508074341354074f78b |
| Latest deploy log | https://app.netlify.com/sites/docsdocker/deploys/632c2f0cb1b3b700085f9f88 |
| Deploy Preview | https://deploy-preview-15629--docsdocker.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Deploy Preview for docsdocker ready!
| Name | Link |
|---|---|
| Latest commit | 4b9b6d542259761ccca86c3ab6e391511d076146 |
| Latest deploy log | https://app.netlify.com/sites/docsdocker/deploys/634d1a6394df9800087b50f6 |
| Deploy Preview | https://deploy-preview-15629--docsdocker.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
For the small % of users who are currently using Dev Envs, they might want to know what's happening under the hood when they use Dev Envs with 4.13. Should this following be included somewhere?
If your project was configured to make use of the .docker folder, we migrate it to a compose-dev.yaml on launch
- If you were using
.docker/docker-compose.yaml, we move it to../compose-dev.yaml(but don’t make any changes) - If you were using
.docker/config.json, we create a../compose-dev.yamlfile with a single service named “app” that is configured to use the image/Dockerfile referenced in the JSON as a starting point
(This is a description that @milas wrote a few weeks back, which I think is still accurate)
Thank you for your comments @nicksieger. I've incorporated most of them. The only one I haven't is about saying more about compose-dev.yaml as the single place where you configure your dev environment.
As discussed and agreed with @hyu , I'm going to tackle this in a separate PR next week, alongside doing a fairly major overhaul of all of the Dev Envs docs as this has pulled at a thread and the content is quickly unraveling...