This the official place to share code for Coronium LS
Please do not ask questions here.
This the official place to share code for Coronium LS
Please do not ask questions here.
This is a great idea Scott, makes me think that we should work towards a system that can be incorporated in the cloud-tools.
Folks could post an app/mod (or how about App Modules ) to a GitHub repo with a meta file of some sort. These can be added to a database (through the cloud-tools) on one of the service machines which could then be used to keep a collection cache.
Between a database and the repos, it would seem trivial to implement (famous last words).
App Module meta could be like:
[lua]return
{
name = ‘MailGun’,
version = ‘1.0.0’,
author = ‘Coronium Developer’,
hash = <generated>,
repo = ‘https://github.com/author/repo_name.git’,
docs = ‘http://readthedocs.org/mailgun-ls/’,
site = ‘https://www.mydevelopersite/mymodule_info’
}[/lua]
So as not to highjack this thread, please share your suggestions and feedback over here.
Cheers.
This is a great idea Scott, makes me think that we should work towards a system that can be incorporated in the cloud-tools.
Folks could post an app/mod (or how about App Modules ) to a GitHub repo with a meta file of some sort. These can be added to a database (through the cloud-tools) on one of the service machines which could then be used to keep a collection cache.
Between a database and the repos, it would seem trivial to implement (famous last words).
App Module meta could be like:
[lua]return
{
name = ‘MailGun’,
version = ‘1.0.0’,
author = ‘Coronium Developer’,
hash = <generated>,
repo = ‘https://github.com/author/repo_name.git’,
docs = ‘http://readthedocs.org/mailgun-ls/’,
site = ‘https://www.mydevelopersite/mymodule_info’
}[/lua]
So as not to highjack this thread, please share your suggestions and feedback over here.
Cheers.