Magnolia Cloud Simulator

Use these instructions to smoke test your bundle before trying it properly in Magnolia Cloud.

The project could be further developed into an integration test framework for custom bundle deployment.
The current state is only compatible with Magnolia versions > 6.2.1. For older version use the tag compat/pre-6.2.1.



Prerequisites

  • You must have created your custom cloud bundle.

  • You must have verified/validated your custom cloud bundle.

  • You must have locally deployed your custom cloud WAR file.

  • You must have set up the PostgreSQL databases for your cloud bundle.

    See Set up PostgreSQL for Cloud here if you have not already done this.


Instructions

  1. Clone the magnolia cloud simulator repository.

    git clone https://git.magnolia-cms.com/scm/od/magnolia-cloud-simulator.git
  2. From your custom cloud bundle project, copy your .war file into the dist/ folder.

  3. Copy the following into your project pom.xml file:

    <build>
      <pluginManagement>
        <!-- Copy artifact to dist folder for docker build. See docker/README.md -->
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-dependency-plugin</artifactId>
          <configuration>
            <artifactItems>
              <artifactItem>
                <groupId>${project.groupId}</groupId>
                <artifactId>example-cloud-webapp</artifactId>
                <type>war</type>
              </artifactItem>
            </artifactItems>
            <outputDirectory>dist</outputDirectory>
            <stripVersion>true</stripVersion>
          </configuration>
        </plugin>
      </pluginManagement>
    </build>
  4. Run the following to copy the artifact into the docker/dist folder:

    mvn clean verify -U dependency:copy
    Ensure the war file is now in the docker/dist folder. Alternatively, you can copy the war file manually.

Build and run docker compose

Ensure that you have your LICENSE_ID and LICENSE_SECRET to hand in the .env file to use when running docker-compose up.

Alternatively, you can run the command below along with docker-compose up.
export LICENSE_ID=<INSERT_HERE>
export LICENSE_SECRET=<INSERT_HERE>
docker-compose up
Hooray

Now you have one Magnolia author instance and one Magnolia public instance. Publishing should work without any additional configuration.

You can access Author and Public via:

Login credentials

You can login to Magnolia with users listed here.

Username and password are the same.
Username Password

adminuser1

adminuser1

adminuser2

adminuser2

developer1

developer1

developer2

developer2

developer3

developer3

developer4

developer4

dev days event sign up
dev days event sign up
Feedback