-
Notifications
You must be signed in to change notification settings - Fork 683
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
Docker compose #859
Docker compose #859
Conversation
This pull request is automatically deployed with Now. |
docker/README.md
Outdated
* add a custom domain, configured in `.env.docker`, to the host system's `/etc/hosts` file | ||
* generate a self-signed ssl/tls certificate and trust the certificate in the system keychain | ||
* run `docker-compose build` to build the container network | ||
* run `docker-compose up` to start the container running PWA at the customer domain with https |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
docker/README.md
Outdated
* run `docker-compose build` to build the container network | ||
* run `docker-compose up` to start the container running PWA at the customer domain with https | ||
|
||
After `docker/run-docker` is executed from the root of the repository, the default confgiuration will have the PWA application running at `https://pwa-docker.local`. |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
@@ -1,11 +1,7 @@ | |||
{ |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
@@ -5,5 +5,6 @@ | |||
"node": "10.x.x" | |||
}, | |||
"public": true, | |||
"version": 1 | |||
"version": 1, | |||
"type": "npm" |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
to PWADevServer configuration options. | ||
More options for this feature are described in documentation. | ||
`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes above are from running prettier
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's odd...what version of Prettier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't have prettier globally on my computer so this is coming from the repo, I can change it back and try it again. Not sure why this triggered in the first place.
f485bde
to
7966261
Compare
host: '0.0.0.0', | ||
port: await portscanner.findAPortNotInUse(10000), | ||
host: config.host || '0.0.0.0', | ||
port: config.port || (await portscanner.findAPortNotInUse(10000)), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe these values should just be checked against process.env
values rather than messing with them in webpack.config.js
7966261
to
17d4a6a
Compare
Since |
When Google steamrolled |
@bbatsche great point. I'm for either |
610b587
to
d76f721
Compare
well that's disconcerting, the now deploy does not fail the check if there are 500 errors from the now server... |
3a9988e
to
3d1bdf0
Compare
docker/run-docker
Outdated
docker-compose build | ||
|
||
message "Starting Docker network and containers" | ||
message "You may see some warnings that @magento/venia-drivers could not be \n resolved. This is normal and not an error." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is going to be resolved with #881.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed since this has been merged now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments from group review
docker/run-docker
Outdated
|
||
main () { | ||
# copy environment variables to .env in root for docker-compose to consume for build | ||
cp ./docker/.env.docker $ENVFILE |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
docker/run-docker
Outdated
-config $OpenSSLConf | ||
|
||
# add the certificate to the system keychain and trust the certificate | ||
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ./docker/certs/$DOMAIN.crt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
look into adding this to the login keychain rather than the system keychain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looked into adding the cert to the login keychain and while I successfully added it to the login keychain file and it was present in the keychain access gui the cert was not being trusted by the browser. despite a lot of google searching I could not get this to work in the login keychain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The OSX security
CLI is so weird and poorly documented that I think it's not even supposed to be public API. OH well!
3d1bdf0
to
9e6d2f2
Compare
840b87d
to
3f77ee8
Compare
3f77ee8
to
47389e9
Compare
Description
This pull request adds the ability run PWA inside of a docker container with a secure https protocol.
Related Issue
Closes #734
Motivation and Context
Containerizing PWA will allow for more CI configuration in the future and help towards a more platform agnostic development environment. So far the setup script in this PR will only work on Mac, but in the future the hope is to get this working on Windows Docker as well.
How Has This Been Tested?
Manually.
To check this out, follow the instructions under the docs draft file
Proposed Labels for Change Type/Package
FEATURE
pwa-buildpack, venia-concept, pwa-devdocs
Checklist: