Electrode Native
v0.41
v0.41
  • Introduction
  • INTRODUCTION
    • Overview
      • What is Electrode Native
      • Why use Electrode Native
      • What is a MiniApp
      • Electrode Native workflow
      • Native dependencies management
      • JS/Native communication
      • Requirements
      • Upgrading Electrode Native
      • Contributing
  • REFERENCE
    • Bundle Store
    • Composite
    • Container
      • What's inside
      • Publication
      • Integration
      • Initialization
      • Launching MiniApps
    • Cauldron
      • Structure
      • Setup
      • Compatibility checks
      • Guidelines
    • Manifest
      • Override
      • Native Modules
      • Configurable Modules
    • Runner
    • APIs
      • Project Generation
      • Implementation
      • Versioning
      • Guidelines
    • Bridge
      • Message Types
      • Communication
      • Leveraging APIs
    • CLI
      • Global CLI
      • Local CLI
    • GLOSSARY
  • GUIDES
    • Debugging multiple MiniApps
  • CLI COMMANDS
    • add
    • bundlestore
      • create
      • delete
      • upload
      • use
    • binarystore
      • add
      • get
      • remove
    • code-push
      • patch
      • release
      • promote
    • compat-check
    • create-api-impl
    • create-api
    • create-composite
    • create-container
    • create-plugin-config
    • publish-container
    • transform-container
    • create-miniapp
    • link
    • regen-api
    • regen-api-impl
    • run-android
    • run-ios
    • start
    • unlink
    • upgrade-miniapp
    • cauldron add
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron config
      • get
    • cauldron del
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron get
      • config
      • dependency
      • nativeapp
    • cauldron repo
      • add
      • clear
      • current
      • list
      • remove
      • use
    • cauldron update
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron batch
    • cauldron regen-container
    • cauldron upgrade
    • cauldron why
    • github
      • github create-ref
      • github delete-ref
      • github align-dependencies
    • platform
      • plugins
        • list
        • search
      • config
        • set
        • get
        • del
        • list
      • install
      • versions
      • uninstall
      • use
Powered by GitBook
On this page
  • Description
  • Currently Available Official Publishers
  • Syntax
  • Related commands
  1. CLI COMMANDS

publish-container

Previouscreate-plugin-configNexttransform-container

Last updated 4 years ago

Description

  • This command can be used to publish a local Container to a repository, using a given publisher.

Currently Available Official Publishers

  • To publish Android and iOS Electrode Native Containers to a remote git repository. The git repository provider does not matter (GitHub, BitBucket, TFS ...).

  • To publish Android Electrode Native Containers to a local or remote Maven repository.

  • To publish Android Electrode Native Containers to a remote JCenter repository.

  • This publisher is mostly used for testing and as starter simple publisher reference to create your own. It does not actually publish the Containers anywhere.

Syntax

ern publish-container

Options

--containerPath

  • The local file system path to the directory containing the Container to publish.

  • Default If this option is not provided, the command will look for a Container in the default platform directory ~/.ern/containergen/out/[platform].

--platform

  • Specify the native platform of the target Container to publish (android or ios)

  • This option is required, there is no default.

--version/-v

  • Specify the Container version to use for publication.

  • The version must be in the format: x.y.z where x, y and z are integers. For example version=1.2.30.

  • Defaults to 1.0.0.

--publisher/-p

  • Specify the Container publisher to use.

  • This option is required, there is no default.

  • You can also use a local file system path to a Container publisher package (only used for developing custom publishers)

--url/-u

  • The url to publish the Container to

  • Some publishers might not need an url. Check the specific Container publisher documentation for reference

--extra/-e

  • Extra configuration specific to the publisher used.

  • Some publishers might not need an extra configuration. Check the Container publisher documentation for reference.

  • There is three different ways to provide the json extra configuration :

    • As a json string

      For example --extra '{"configKey": "configValue"}'

    • As a file path

      For example --extra /Users/username/my-publisher-config.json

      In that case, the configuration will be read from the file.

    • As a Cauldron file path

      For example --extra cauldron://config/publishers/my-publisher-config.json

      In that case, the configuration will be read from the file stored in Cauldron.

--inPlace

  • Run the publisher directly from the container directory instead of a temporary directory

  • Defaults to false

Related commands

For this way to work, the file must exist in Cauldron (you can add a file to the cauldron by using the command).

| Create a new container (native or JavaScript only) locally to the workstation.

git
maven
jcenter
dummy
ern cauldron add file
ern create-container