[RELEASE] Coronium LS v1.0.0-beta

Third Party Coronium
#1

Bake Your Own Cloud For Corona SDK

Coronium LS Beta  is now available for your testing adventures.

http://docs.coronium.cloud

It’s still a work in progress, so please feel free to post any feedback in this thread.

Releases

Coronium LS Core (beta)

Corona SDK Module

All suggestions and use discussions are very welcome. Good or bad. See the following for reporting errors.

Issue and Enhancement Reporting

All issues will need to be logged with the appropriate “issue tracker” on GitHub.

If you want some type of response to your request, it must reside in the issue tracker. Don’t feel ignored if you don’t get a response otherwise. It’s the only way to keep things orderly if we (and I mean the community) want to do this right.

LS Core and Deploy : https://github.com/coroniumcloud/Coronium-LS/issues

Corona SDK Module : https://github.com/coroniumcloud/Coronium-LS-Module/issues 

Documentation : https://github.com/coroniumcloud/Coronium-LS-Docs/issues

Thanks for reporting. It can’t be fixed if we don’t know about it!

Be sure to catch the replay of  Corona Geek  to learn more about the project as a whole (and a demo).

Video tutorials are coming soon.

Development Branch

If you have interest in the “bleeding edge” version of Coronium LS (test features, new features, breaking features, etc) there are “dev” branches as well in all the repos. If that doesn’t mean anything to you, then disregard. :slight_smile:

Core and Deploy : https://github.com/coroniumcloud/Coronium-LS/tree/dev

Corona SDK Module : https://github.com/coroniumcloud/Coronium-LS-Module/tree/dev

Documentation :  http://docs.coronium.cloud/en/dev/

Enjoy!

#2

Hey Chris, looks like that link should be https? 

{EDIT} Works now.

#3

Link got copied in wrong, should be working now. The docs are not secure, so be careful.  :ph34r:

Cheers.

#4

I’m getting an error running packer, not sure what I’m doing wrong, I followed the Readme file

Chris$ packer validate -var-file=do.json -var-file=variables.json coronium.json

Failed to parse template: open coronium.json: no such file or directory

#5

Looks like it’s supposed to be “cloud.json” now, I still need to catch up on cleaning docs. Thanks for taking the time to post it, I’ll fix it up.

packer validate -var-file=do.json -var-file=variables.json cloud.json

I think you need to be in the Packer folder as well just in case.

Cheers.

#6

Ok all installed at DigitalOcean :slight_smile:

You might want to mention in the docs that once installed you have to run ‘sudo cloud up’ to get it all up and running.

Also I just let the default SSL certificate be trusted, as I’m not sure how to use lets encrypt in this situation to get my certificate (I have used it on another droplet before) for the corundum droplet. (I see the certificates in the .ssh folder but letsencrypt wants to know the document root etc. Any pointers in this direction would be useful also.

Other than that it’s looking good :slight_smile:

Thanks Chris

#7

The echo example works fine.

The Upload example doesn’t work, there seems to be a couple of problems, it doesn’t put the correct prefix on (https) and it can’t find the path.

#8

Hi Chris,

Do you have a timeframe, when the tutorial to deploy on Amazon EC2 will be available ?

thanks
Nick

#9

Chris,

What would be the advantage of using Coronium LS over Coronium Cloud beyond the latter no longer being actively developed?

Tom

#10

Besides being actively maintained, my experience with Coronium LS is that it is much more customizeable than Coronium Cloud. In about 3 hours yesterday, I whipped up a basic register/login system storing users in a mySQL database. Additionally, for a beta, it has many incredible features, and Develephant is actively making things even better. I’m amazed by what I can do with the server in so little time.

Although I was hesitant at first to migrate from Coronium to a testing local server, I’m much happier with Coronium LS. It did take a little research through the docs to set things up initially, but after working through it, I’m glad that I made the switch.

Lastly, the fact that it is open source is icing on the cake. A full pull requests or reported issues on Github improve the platform for everyone.

#11

Someone should create a fourm thread to dump code for Coronium LS. Or maybe open marketplace etc

#12

I was thinking about working on my users system a little bit more (with an email confirmation, etc.) and releasing it somewhere here. But yes, I’m not entirely sure where to do so.

#13

I just made a fourm thread if you want to share your code
https://forums.coronalabs.com/topic/64778-coronium-ls-code-share/

You share how ever you want Dropbox, corona file upload, Google Drive, github, etc

#14

So I’m not sure if I’m doing something wrong or there’s an error, I’m trying to just list the mongo databases

-- Coronium Cloud local api = cloud.api() function api.post.test( in\_data ) local mongo = cloud.mongo.new() local dbs, e = mongo:databases() if not dbs then return cloud.error( e ) end return dbs end api.get.test = api.post.test return api

and I get internal error (I changed the IP address and domain name) …

[error] 2605#0: *191 lua entry thread aborted: runtime error: unknown reason

stack traceback:

coroutine 0:

[C]: in function ‘error’

/usr/local/cloud/lualib/resty/mongol/colmt.lua:57: in function ‘docmd’

/usr/local/cloud/lualib/resty/mongol/colmt.lua:287: in function ‘query’

/usr/local/cloud/lualib/resty/mongol/dbmt.lua:16: in function ‘cmd’

/usr/local/cloud/lualib/resty/mongol/init.lua:68: in function ‘databases’

/usr/local/cloud/lualib/cloud/mongo.lua:67: in function ‘databases’

/usr/local/cloud/apps/echo/api.lua:8: in function ‘api_func’

/usr/local/cloud/lualib/cloud/input.lua:149: in function ‘request’

content_by_lua(cloud_server.conf:116):5: in function <content_by_lua(cloud_server.conf:116):1>, client: 00.00.00.00, server: localhost, request: “POST /echo/test HTTP/1.1”, host: “xxxxxx.xxx”

#15

HUGE Admin request. Please start new threads for new topics. This thread has a chance to become a huge monolithic mess of hijacked thoughts. Feel free to discuss the announcement here, but if you’re building a module and want to talk about it, or you’re having an error, those all need to be their own threads.

#16

Chris was on Corona Geek Monday talking about this. I don’t know what Charles’ plan is with when the show will be up on https://www.youtube.com/user/CoronaGeek but one of the things that stood out to me from Chris’ presentation was that the older Coronium was a hodge-podge collection of API calls that were not consistent.  In other words some would return data, others would use a listener function. There HTTP POST calls, GET calls, PUT calls.  In the new system everything works the same. If you know network.request() then you won’t have any issues with the Coronium LS calls.  It’s also much more modular and you can add your own mods. As an Open Source project, this framework will lend itself better community enhancements.  (I hope I’m characterizing this properly). 

I’ve not had time to dive through all of the docs yet and I’m running on just his presentation, but it sounds like it’s going to be awesome. I’ve got to move a couple of personal websites off of my DO server to my other web hosting company, so I can blow away that instance and get a Coronium LS instance up to start messing with.

Oh and a huge feature: All LS endpoints can generate JSON, plain text (for Internet of Things devices) and HTML. If Chris can add a small feature to this, module developers could detect who’s hitting the endpoint and choose what to output. Imagine someone hitting your leaderboard endpoint from a web browser and getting back a well formatted HTML page but if it came from a Corona app, it would smartly deliver JSON data for the app to format.

Rob

#17

Hi folks,

I’m closely watching (and coding), so don’t think your errors are going unnoticed, especially in terms of “getting started” docs.

Gotta give credit where credit is due; the “auto-content” negotiation idea was given by Rob. It’s great idea and will be an option in the near future.

Bugs, Installation, and Enhancement Issue Reporting

I didn’t really think this part through well, but to keep a handle on fix requests, enhancements, and bugs, all issues will need to be logged with the appropriate “issue tracker” on GitHub.

If you want some type of response to your request, it must reside in the issue tracker. Don’t feel ignored if you don’t get a response otherwise. It’s the only way to keep things orderly if we (and I mean the community) want to do this right.

Core and Deploy : https://github.com/coroniumcloud/Coronium-LS/issues

Corona SDK Module : https://github.com/coroniumcloud/Coronium-LS-Module/issues 

Documentation : https://github.com/coroniumcloud/Coronium-LS-Docs/issues

Thank you for taking time to report, it’s very appreciated!

Cheers.

#18

I’ve made some updates to the original post for more details and options.

Cheers.

#19

I’ll get some clearer docs together for this process. Localhost was the main priority for beta so a little lacking in other deployments.

Thanks!

#20

I should be deploying AMIs shortly, just cleaning a few things up. Currently Amazon AMIs are auto generated, so there isn’t really a process for “building” one.