Closed pun-ky closed 5 years ago
maybe it is only needed to use https://github.com/bmuschko/gradle-vagrant-plugin and create valid box.
consider following this approach and setup 2 sites for example project: https://helpx.adobe.com/experience-manager/dispatcher/using/dispatcher-domains.html
It is possible to run Vagrant on Docker, so we could possibly have one plugin that uses Vagrant and runs both Docker containers and Vagrant images.
Added the first proposal of the solution:
Problem is routing from dispatcher to local instance. It is not possible to access hosts localhost from Docker network. Also, it would be good to configure only logical names in dispatchers, solrs, etc. configurations instead of hardcoding IPs or specific hosts.
I am working on it.
I find out that this is not a problem, at least for Docker on Mac and Windows. I used host.docker.internal
name as the host address. Dispatcher connects to publish without any problems. I won't introduce and proxies then to keep the setup simple.
PR with a proposal of local environment setup for project multi (basic dispatcher and unconfigured solr instances): https://github.com/Cognifide/gradle-aem-multi/pull/45
Implementing improvements after review:
environment
plugin - DONEenvironment
plugin - DONEenvironment
plugin - DONEThis is the final PR for this task: https://github.com/Cognifide/gradle-aem-plugin/pull/361
done, to be released within 7.0.0
AEM on Vagrant / VirtualBox works, but its performance is not enough good as native.
Taks
aemSetup
is now able to rollout easily native AEM instances. The missing parts of typical production ready AEM stack are:Imagine:
sh gradlew aemSetup
We will achieve full AEM stack configured in one place (one project VCS repository) with native AEM performance.