HTTP MarketPlace


MarketPlaces of HTTP make use of a conventional HTTP server to expose the images (MarketPlaceApps) uploaded to a MarketPlace of this kind. The image will be placed in a specific directory that must be configured to be exposed by HTTP.

This is a fully supported MarketPlace with all the implemented features.


A web-server should be deployed either in the Frontend or in a node reachable by the Frontend. A directory that will be used to store the uploaded images (MarketPlaceApps) should be configured to have the desired available space, and the web-server must be configured in order to grant HTTP access to that directory.

It is recommended to use either Apache or NGINX as they are known to work properly with the potentially large size of the MarketPlaceApp files. However, other web servers may work as long as they’re capable to handle the load.

The web-server should be deployed by the administrator before registering the MarketPlace.


These are the configuration attributes of a MarketPlace template of the HTTP kind.

Attribute Description
NAME Required
MARKET_MAD Must be http
PUBLIC_DIR (Required) Absolute directory path to place images, the document root for http server, in the Frontend or in the hosts pointed at by the BRIDGE_LIST directive.
BASE_URL (Required) URL base to generate MarketPlaceApp endpoints.
BRIDGE_LIST (Optional) Comma separated list of servers to access the public directory. If not defined, public directory will be local to the Frontend.

For example, the following examples illustrates the creation of an MarketPlace:

cat market.conf
NAME = PrivateMarket
PUBLIC_DIR = "/var/loca/market-http"
onemarket create market.conf
ID: 100

Tuning & Extending

System administrators and integrators are encouraged to modify these drivers in order to integrate them with their datacenter. Please refer to the Market Driver Development guide to learn about the driver details.