github.com/graniticio/granitic/v2
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.
Readme
Granitic is a framework and lightweight application server for building and running web and micro services written in Go.
Additionally, Granitic is designed to be 'DevOps friendly' and offers:
Read and follow the installation instructions then work through the tutorials
The GoDoc for Granitic can be found here
Visit the granitic.io website to read the complete reference manual
Once you have followed the installation instructions, you can run Granitic's unit tests by running
cd $GOPATH/src/github.com/graniticio/granitic
go test ./...
We are always delighted to receive contributions from the community. Please read the Contributing and Code of Conduct guides and then have a look at the open issues
FAQs
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.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A hospital in Mobile, Alabama, agreed to a settlement in a landmark ransomware death lawsuit, but is now reportedly reconsidering the agreement and refusing to pay.
Security News
A new report explores how advancements in LLMs are enhancing cyber threats, including polymorphic malware, personalized spearphishing, and the risk of hijacking customer service bots.
Security News
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.