-
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
Discovery for Docker environment with containers [SPIKE] #126
Comments
Mentioned this in Slack, didn't know there was an issue for it. Forked a Magento 2 docker image and made it pull from the 2.3-develop branch. Also added a script to install Venia. The docker image also comes with a self signed cert so magento can be served through HTTPS (default for the venia-concept). Installing venia is documented in the readme here Link to the repo: https://github.com/pcvonz/docker-magento2 There is one stumbling block that I can think of: The There is a little bit of cruft from the version of the image I forked, notably the developer / integrator folders. Those aren't relevant anymore. They can probably be removed and we could use just one dockerfile. It doesn't clutter up the actual image and I just wanted to start contributing to Venia 😃 To build the
Left to do:
|
Kamino cloned this issue to magento-research/pwa-studio |
work being picked up under #734 |
This issue is for the following packages:
[ ]
venia-concept
[X]
pwa-buildpack
[ ]
peregrine
[ ]
pwa-module
[X]
pwa-devdocs
This issue is a:
[ ] Bug
[X] Feature suggestion
[ ] Documentation issue
[ ] Other (Please Specify)
Environment
node -v
)npm -v
)Description
As a developer, I want to utilize Docker to quickly get started with development for PWA Studio regardless of my environment and potentially contribute to the project.
Expected result:
Discovery for continuously updated Docker container for PWA Studio environment
Review and summary of Docker findings and process
Additional user stories/epics for implementation
Example and demo (as appropriate)
Possible solutions:
The text was updated successfully, but these errors were encountered: