edgexfoundry/docker-export-client-go repository overview

This image is ARCHIVED and no longer actively developed or maintained in EdgeX Foundry. Use only when working with an older version of EdgeX.

⁠Quick reference

• Maintained by: EdgeX Foundry⁠ (a Linux Foundation⁠ project)

• Where to get help: EdgeX Web Site⁠, EdgeX Documentation⁠, EdgeX Slack⁠, EdgeX Project Wiki⁠

⁠Supported tags and respective Dockerfile links

• Fuji
  • 1.1.0 - Dockerfile⁠

⁠Quick reference (cont.)

• Where to file issues: https://github.com/edgexfoundry/export-client/issues⁠ (NOTE - this image is archived and issues are no longer being worked)

• Supported architectures: intel/amd64

• Published image artifact details: https://nexus3.edgexfoundry.org⁠

• Source of this description: https://github.com/edgexfoundry/cd-management/tree/edgex-docker-hub-documentation⁠

⁠What is EdgeX Foundry?

EdgeX Foundry is a vendor-neutral, open source project hosted by The Linux Foundation building a common open framework for IoT edge computing. At the heart of the project is an interoperability framework hosted within a full hardware and OS agnostic reference software platform to enable an ecosystem of plug-and-play components that unifies the marketplace and accelerates the deployment of IoT solutions.

In simple terms, EdgeX is edge middleware - serving between physical sensing and actuating "things" and our information technology (IT) systems.

EdgeX's official documentation can be found at docs.edgexfoundry.org⁠.

Edgey - the official EdgeX Foundry project mascot

⁠What's in this image?

ARCHIVED The EdgeX Foundry Export Client Registration micro service enables clients, whether they are on-gateway or off-gateway, to register as recipients of data coming through Core Data. This service is used for export of data in older EdgeX Foundry releases. It is no longer used or supported.

The service source code: https://github.com/edgexfoundry/export-client⁠

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Some additional license information which was able to be auto-detected might be found in the Attribution.txt file located in the image and copied from the associated

source repository⁠.