github.com/graniticio/granitic/v2 (go): Package granitic provides methods for configuring and starting a Granitic application.  To get started with Granitic, visit https://granitic.io/getting-started-installing-granitic  This package provides entry point functions for your application to hand control over to Granitic. Typically your application will have a single, minimal file in its main package similar to:  You can build a skeleton Granitic application by running the grnc-project tool, which will generate a main file, empty configuration file and empty component definition file. The uses and syntax of these files are described in the config and ioc packages respectively.  A Granitic application needs two things to start:  1. A list of components to host in its IoC container.  2. One or more JSON configuration files containing environment-specific settings for your application (passwords, hostnames etc.)  Folders and files containing configuration are by default expected to be stored in  This folder can contain any number of files or sub-directories. This location can be overridden by using the -c argument when starting your application from the command line. This argument is expected to be a comma separated list of file paths, directories or HTTP URLs to JSON files or any mixture of the above.  When starting your application from the command, Granitic takes control of processing command line arguments. By default your application will support the following arguments.  If your application needs to perform command line processing and you want to prevent Granitic from attempting to parse command line arguments, you should start Granitic using the alternative:  where you are expected to programmatically define the initial settings.
Keywords: application-framework|application-server|configuration-management|dependency-injection|devops|golang|inversion-of-control|ioc|iot|json|microservice|microservices|scheduler|validation|webservices|xml