Here are listed some recommendations when deploying Aspire using the container images.
Official container imageimages:
- docker.repository.sca.accenture.com/docker/aspire:5.0 (online distribution)
- docker.repository.sca.accenture.com/docker/aspire-basic:5.0 (offline distribution)
...
So your containers can see what you install locally when running "mvn clean install
" on your aspire components
Code Block | ||
---|---|---|
| ||
$ docker login docker.repository.sca.accenture.com |
You'll need to use your registered email/password credentials.
For production deployments it is recommended to create a custom Aspire image, containing all the jar files needed for the deployment to run. This way no new downloads will be required during restarts and uptime will be improved.
There is an official docker image of aspire containing all the basic components jar files, only missing the premium components ones. Those premium jar files must be downloaded and added to your custom aspire image manually.
You'll need to have Maven 3 installed, and configured to use https://repository.sca.accenture.com/artifactory/public as the repository. Follow Configuring Maven for Aspire.
Code Block | ||
---|---|---|
| ||
mkdir custom-aspire-image
mkdir custom-aspire-image/jars |
Change directory to your image folder
Code Block | ||
---|---|---|
| ||
cd custom |
-aspire-image |
For each premium component you'll need to execute: (where VERSION is 5.0, 5.0.1, 5.0.2, etc, and COMPONENT-ARTIFACT-ID is the maven artifact id of the component)
Code Block | ||
---|---|---|
| ||
mvn dependency:copy -Dartifact=com.accenture.aspire:[COMPONENT-ARTIFACT-ID]:[VERSION] -Dmdep.useBaseVersion=true -DoutputDirectory=custom-aspire-image/jars |
Should be called "Dockerfile"
Code Block | ||
---|---|---|
| ||
FROM docker.repository.sca.accenture.com/docker/aspire-basic:5.0
ADD jars/* /opt/aspire/bundles/aspire |
docker build -t [image-name]:[image-tag] .
For instance:
Code Block | ||
---|---|---|
| ||
docker build -t custom-aspire:5.0 . |