1.6.0 • Published 5 years ago

nocms-cli v1.6.0

Weekly downloads
1
License
ISC
Repository
-
Last release
5 years ago

nocms-cli

TODO

  • Create package nocms-api-server to reduce boilerplate within Fragments, WebApi and other API containers.
  • Create nocms-build to handle bundling of js and css in web containers
  • Put important config values in CLI promots
  • Create config validation for common containers
  • I nocms-config-client: setDefaults
  • Auth

Prompts: RabbitMQ-login RabbitMQ-passord TokenSecret

Command line interface for NoCMS projects.

Installation

Install from npm: npm i -g nocms-cli Run nocms help to get an overview of the available operations.

Containers

A typical collection of containers for a NoCMS project would be:

ContainerImage NameDescriptionTypeStartup order *
Elasticsearchdocker.elastic.co/elasticsearch/elasticsearch-oss:6.1.0Elasticsearch database used by page and i18n.External1
Config API_config_apiCentral store for configuration values. Implemented using nocms-config-api-server package.Project1
Rabbit MQrabbitmq:3.6.2-managementMessage queue used for write operationsExternal1
Authentication API *_authentication or nocms_authenticationAuthentication service using Auth0 or custom implementationsNoCMS or Project3
Authorization API *_authorization or nocms_authorizationAuthorization service using values from Config API or custom implementationNoCMS or Project3
Fragment API **_fragmentsHTTP server providing HTML fragments for use with ESI includes though VarnishProject2
Web API *_web_apiHTTP server providing API for reading operation on data that are user specific, real-time, etc.Project2
Message API *nocms_messsage_apiEndpoint to handle POST requests for publishing messages on the message queue.NoCMS2
Pagenocms_pageAPI for providing page dataNoCMS3
I18n API **nocms_i18nApplication for handling translations and data APINoCMS2
Varnish_varnichCache and reverse proxy with ESI support.External4
Cloudinarynocms_cloudinaryProxy for accessing the Cloudinary service used for imagesNoCMS3
  • Optional, but required for publishing. ** Optional

* Startup order

| # | Description | |===|======================================================================================================| | 1 | These containers have other containers depending on them, and thus should start as early as possible | | 2 | These containers are exposed through Varnish and needs to be available before Varnish starts up | | 3 | Other containers with no particular dependencies, and are not listed in Varnish backends | | 4 | Varnish |

1.6.0

5 years ago

1.5.0

5 years ago

1.3.0

5 years ago

1.2.0

5 years ago

1.1.0

5 years ago

1.0.1

6 years ago

1.0.0

6 years ago