Vagrantfile and resources to make a development instance of AEM in Virtualbox
-
vagrant 1.8.1or higher Installig Vagrant -
Ansible 2.0.1.0or higher Installing Ansible
-
Place your
aem-author-4502.jarandlicense.propertiesinside/aem_install_files/ -
Content packs will be installed in alphabetical order inside
/aem_install_files/packages_to_install/ -
Packages that require restart should be placed inside
/aem_install_files/packages_to_install/servicepacks/
Folder structure should look like this(The readme.md is already in the repo):
├── LICENSE
├── README.md
├── Vagrantfile
├── aem_install_files
│ ├── aem-author-4502.jar
│ ├── license.properties
│ ├── packages_to_install
│ │ ├── content
│ │ │ ├── example-content-pack.zip
│ │ └── servicepacks
│ │ ├── README.md
│ │ ├── acs-aem-commons-content-xxx.zip
│ │ ├── aem-service-pkg-wrapper-xxx.zip
│ └── readme.md
├── playbook.yml
└── resources
-
vagrant upfrom project root (might take a while) -
Navigate to
localhost:4502to access AEM
You can now safely remove the jar and license.properties placed from step 2
-
❓❓❓
-
Profit 🚀
Changing of JVM/AEM parameters can be done in resources/aem.service using an Environment directive.
Getting started with Fedora Unit files
Learn more about systemctl
Starting and stopping of the AEM service from inside the VB can be done using systemctl start aem or systemctl stop aem (Don't forget to sudo)
The MIT License (MIT)
Copyright (c) 2016 Jose Miguel Mendez
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.