Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • By packaging contribution archives and the Fabric3 runtime as a deployable image using the the Fabric3 Gradle Assembly Plugin or Fabric3 Maven Assembly Plugin. This is the recommend way to deploy services in Fabric3.
  • By using the The Admin CLI which provides a command line interface and scripting API for automated deployment. This method is primarily available for legacy support. 
  • By placing contribution archives in the deploy directory of a running server instance.

...

  •  This method is primarily available for testing.

Directory-based Deployment for Testing

Contributions can be deployed by copying them to the server's /deploy directory. The server periodically scans the directory for new contributions and will deploy them when found. If an application is comprised of multiple contributions that depend on each other, the server will calculate the proper order the contributions must be deployed based on the import metadata contained in their manifests, including transitive dependencies. For example, if A depends on B which dependences on C, the server will deploy C, then B, followed by A.

...