[RELEASE] Coronium LS v1.0.0-beta

@cublah Logged your issue. https://github.com/coroniumcloud/Coronium-LS/issues/3

Thanks again.

Great that you added the issues to github, as you say better to get it all in one place. Just a quick question, when changes are done to the code what is the best way to upgrade the current server code?

[quote name=“develephant” post=“334473” timestamp=“1469649877”]@cublah Logged your issue. https://github.com/coroniumcloud/Coronium-LS/issues/3   Thanks again.[/quote] Thanks Chris, you are doing an awesome job :slight_smile:

So how do we update to the latest version? do we just copy over the changed files or do we have to create a whole new snapshot at DigitalOcean?

You should be able to reinstall it

But creating a new snapshot and then using that snapshot would delete anything that you’ve done right?

I honestly have not used Coronium LS but I imagine Chris does not write over important files. I would make a backup just in case.

When I updated my localhost, I started fresh. Make sure to backup/export any databases you have, as well as any lua files you’ve created/edited (like the api.lua file). When the new installation is set up, make sure to update your api key in your cloud initialization client-side.

I’m sure there will be a better way to do it, but since it is a beta after all, I figured that starting fresh is the best way to do things.

This discussion about snapshots and how updates are handled is a prime example of hijacking the thread. Please start a new thread for this. We have a whole forum for Coronium. Please use it.

Hey Chris, looks like that link should be https? 

{EDIT} Works now.

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

Cheers.

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

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.

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

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.

Hi Chris,

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

thanks
Nick

Chris,

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

Tom

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.

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

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.