Installing Artifactory Edge

JFrog Installation & Setup Documentation

Content Type
Installation & Setup

Subscription Information

This feature is supported with the Enterprise+ license.

JFrog Artifactory Edge (an "Edge node") is an edition of JFrog Artifactory whose features are customized to serve the primary purpose of distributing software to a runtime such as a data center, a point-of-sale or even a mobile device. All packages hosted in an Edge node are part of a Release Bundle which is uploaded using direct file upload through the UI or REST API.Distribute Release Bundles (v1)

The process of installing an Edge node is identical to installing a standard Artifactory instance. For Artifactory installation options, see Installing Artifactory. Specify an Artifactory Edge license during installation to create an Edge node.

The following table summarizes what an Edge node can and cannot do compared to a full Artifactory instance:

Artifactory

Edge Node

Uploading Files

Upload from a source Artifactory instance during a Distribution transaction

Direct upload of generic artifacts using the UI or REST API

To the artifactory-edge-uploads generic repository only

Downloading Files

Repositories

Local

Remote

Smart Remote Repository only

Virtual

Storage (all options supported by Artifactory)

Filestore Sharding

User Plugins

Replication

Builds

Xray Integration

High Availability

Projects

Deploying and Pulling Artifacts

The artifactory-edge-uploads repository is automatically created and cannot be removed. Deploy artifacts to this repository using the JPD UI or REST API.Deploying ArtifactsDeploy Artifact

All other repositories you define on an Artifactory Edge are read-only. The artifactory-edge-uploads repository is the only repository to which your Release Bundles are deployed.

From version 6.12, an Artifactory Edge node can be configured to pull artifacts using a Smart Remote Repository. Artifacts can be pulled from other Artifactory instances with Enterprise+ or Edge licenses.Smart Remote Repositories

Normal remote repositories that are not Smart Remote repositories are not supported. For example, you cannot create a remote repository pointing to a Docker hub.

Pull replication is not supported on Edge nodes.