Documentation
Primary version
Primary version
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • Key features
  • The Artifactsearch
  1. Terms and concepts

Base

PreviousUser roles

Last updated 6 years ago

The Base is the backend of the Cubbles platform. It provides a repository to manage Cubbles components and services for component upload, replication between multiple Base instances and component delivery to web clients. Base operators can set up any numbers of independent “stores”. Each store can be referred to by a web client (using the ).

The Cubbles Platform

Key features

  1. Webpackage Repository: The Base is able to store an unlimited number of webpackages.

  2. Webpackage Delivery: Any stored webpackage can be requested directly by any web client.

  3. Multiple Stores: Admin can create any number of independent webpackage stores.

  4. Authorized Uploads: Uploading of new webpackages is restricted to users with corresponding permissions.

  6. Replication: Webpackages for a store can easily be replicated from other stores.

The Artifactsearch

Easy Setup: The Base is Docker-based. All images are publicly available on .

The artifact search is an application that allows accessing the artifacts of a store; e.g., the .

Artifactsearch
Docker Hub
"shared" store
Cubbles-RTE