Developer Documentation
  • Documentation Overview
  • Development Introduction
  • Getting Started
  • Fundamentals
    • Deploy an App via Pre-defined Sidecar
      • Sidecar Tutorial: Server-side
      • Sidecar Tutorial: Client-side
      • Sidecar Tutorial: Docker & Deploy
    • Deploy an App with Eureka
    • Design Guidance
  • Authentication
    • Accessing data exposed by the platform
    • Single Sign-On
      • Angular
      • Vue
      • Java Spring: Accepting JWT
      • Python Django: Accepting JWT
    • User and Role Identification
  • APIs | Data Integration
    • Submodel Index
    • Masterdata
    • Transactional data
  • Docker Information
    • Ruby Stack
    • Golang Stack
    • Node JS Stack
    • Java Spring Stack
    • Python Stack
  • Connect to the Platform
    • Integrate using Eureka Rest APIs
    • Use our Pre-built sidecar
    • Production deployment
  • Add-on Features
    • IApps-Navigation
  • Testing
  • FAQs | Troubleshooting
  • Registration
    • Application pre-requisites
      • Basic Requirements
    • Register Developer Account
    • Submit basic application info
    • Onboard Application
      • Submit Appstore details
        • App basic information
      • Configure Application
        • App Permission
        • App Data
        • AAS Instance
        • Licensing
        • Access Rights
        • Account Info
        • Terms Of Use
        • Pricing
      • Publish and test
        • Deploy
        • Register into Service Discovery
    • Publish to Marketplace
  • User Experience
  • The business model - How do I get paid?
  • References
    • IndustryApps - Intro
    • What is an Asset Administration Shell?
    • What is ECLASS?
      • How is ECLASS and Concept dictionary are used
    • Industry 4.0 standards
    • Customer Terms of Use
      • Subscription Order
    • Solution provider Terms of Use
      • Contract regions
      • Submission Form ( Solution provider)
Powered by GitBook
On this page

Docker Information

Containerising, configuring and pushing your applications.

PreviousTransactional dataNextRuby Stack

Last updated 2 years ago

If you are looking to push your application to IndustryApps via Docker, you can integrate your application credentials into a docker-compose.yml file. The following compositions offer sample templates that may be used while pushing your application categorised by server-side languages.

The docker-compose.yml file will need to contain an image name appropriate to your application should you decide to push your container onto the IndustryApps platform directly.

Navigate to:

Applications > {App Name} > App Data, the required name will be available as shown below:

Things to note when containerising your application

The IndustryApps system expects the apps to be containerised and pushed to our container registry. When containerising the app please take care of below points.

  • The application start command should be added in the ENTRYPOINT.

  • Application should be running on port 80.

  • The Eureka Server URL and hostname should be set as environment variable - EUREKA_SERVER and HOSTNAME.

  • If the application is hosted externally, the hostname and status check which point to the platform require ssl certification for a successful registration.

To Deploy onto the IndustryApps docker registry, tag your applications' docker composition as seen below.

docker build --tag industryapps.azurecr.io/<my_company>/<APPID>

You may simply copy your applications unique URI from 'Applications > {App Name} > App Data' as seen above.

To Push your container onto the registry, execute the following command in terminal. Copy into the terminal the unique URI.

docker push industryapps.azurecr.io/<my_company>/<APPID>

Additionally, please be sure to configure the context URL for your client-side application in your index.html file as a relative path. An example shown below illustrates how this can be accomplished with Angular.

<head>
    <meta charset="utf-8">
    <title>Application</title>
    <base href=".">
    ...
</head>

If the application container image is pushed onto the platform, be sure to configure the application under a sub-directory inside your application directories designated as your applications'APPCODE.

https://your-domain.com/{APPCODE}/

Unique application container image name