Deploy the service in a few minutes with Amazon AWS Cloud Formation
Fully manage the remote service with the Progressive Web Application or the API Rest
Server messages and the Progressive Web Application are localized in multiple languages
Authenticate with the AWS IAM Credentials (access key id and secret access key)
Available drivers:
Github
Gitlab
Tiggers:
create the Composer package definition when the branch or tag is created
remove the Composer package definition when the branch or tag is deleted
refresh the commit SHA1 on each commit
Storage:
store the Composer package definitions, API keys and config in the DynamoDB
put in cache the package versions and providers in S3
track the download count of each package version by Composer
API Rest to:
configure the server
list the repositories
enable or disable manually each repositories
generate or delete the token used by the Webhooks
list the API keys
generate or delete an API key
list the package versions
generate all package definitions for a specific repository
show the details of each package version
refresh all packages or a specific package version
delete all packages or a specific package version
clean and rebuild the cache
CLI commands to manage the remote service:
enable or disable manually each Github repositories
enable or disable manually each Gitlab repositories
generate or delete the token used by the Github Webhooks
generate or delete the token used by the Gitlab Webhooks
generate or delete an API key
generate all package definitions for a specific repository
refresh all packages or a specific package version
delete all packages or a specific package version
show the Github tokens
show the Gitlab tokens
CLI commands to create and deploy manually:
configure interactively the project
create or remove the S3 bucket to deploy the code
build, package, and deploy automatically the project in AWS API Gateway, Lambda, SQS, DynamoDB, S3, IAM,
and Cloud Watch with the Cloud Formation stack
remove the project on AWS (but keeping all the data in DynamoDB and S3)
serve the server in local for tests
All CLI commands use the API Rest of the Server
Auto configuration of the CLI tool:
authentication can be doing with the AWS Security Token Service (session token) or the AWS IAM Credentials
automatically configuration of the AWS credentials if the Shared Credentials File
is present on your machine
automatically configuration of the AWS regions if the Shared Config File is present on your machine