[Coronium LS] Updating Beta Releases

Third Party Coronium
#1

Hi folks,

In regards to updating, since this is a beta, releases will be coming out quickly. Though many will have minor changes, some will be larger, so what’s the best way to handle it?

Localhost

If you want to go the “pro” route, then you should “clone” the Coronium LS repositories you’re interested in (I personally recommend a popular – and free – desktop tool called SourceTree).

When source is updated, you can “pull” the latest code into your local clone, and from your deploy folder, simply run:

sudo vagrant reload --provision

Builds are provisioned using Chef-Solo, and should generally should not mess with your existing configuration. Though some releases may not render that the case (and will be noted).

In general, during beta, it’s best to just start a fresh compile. The rapid releases will slow as the first round of issues are dealt with. There will eventually be a way to update from the internal “cloud-tools” on the system.

Let me know if you have any questions. Issues? https://github.com/coroniumcloud/Coronium-LS/issues

Releases

You can always find the latest (and previous) releases here, with important changes noted:

Using a release is not the same as “cloning” the source code.

Core and Deploy

Corona SDK Module

Latest docs can always be found at http://docs.coronium.cloud

Thanks for taking part in the beta. It’s gonna be a little rocky at first. :slight_smile:

Cheers.

#2

When source is updated, you can “pull” the latest code into your local clone, and from your deploy folder, simply run:

sudo vagrant reload --provision

Builds are provisioned using Chef-Solo, and should generally should not mess with your existing configuration. Though some releases may not render that the case (and will be noted).

I’m no good with the syntax so I’d have to dig around to figure it out. But is there an easy way to deploy a live coronium instance to a droplet using vagrant’s digitalocean plugin? (or an easy way to essentially re-run chef-solo on an existing instance?)

Deploying a snapshot is easy enough. But I’m looking to deploy and provision it directly, so that I can easily re-provision from source when an update occurs while keeping my keys and system configuration.

Haven’t touched linux since my MUD times, so a bit rusty and out of date lol.

#3

Hi,

I have to admit the updating process is next up to get refined. So my apologies for the unclarity.

There will be fresh releases, and update “cookbooks” so in theory the idea is you can just leave your server as-is and run the Chef  update. Which should keep everything in-line without losing any config data. That’s the goal at least. Additionally, add that functionality directly into the cloud-tools.

Basically, a proper updating model is on its way.

Cheers.

#4

It is always a good idea to have a backup

#5

Even when updating your phone os or desktops. There was an iOS update that cleared data of iPad pros

#6

When source is updated, you can “pull” the latest code into your local clone, and from your deploy folder, simply run:

sudo vagrant reload --provision

Builds are provisioned using Chef-Solo, and should generally should not mess with your existing configuration. Though some releases may not render that the case (and will be noted).

I’m no good with the syntax so I’d have to dig around to figure it out. But is there an easy way to deploy a live coronium instance to a droplet using vagrant’s digitalocean plugin? (or an easy way to essentially re-run chef-solo on an existing instance?)

Deploying a snapshot is easy enough. But I’m looking to deploy and provision it directly, so that I can easily re-provision from source when an update occurs while keeping my keys and system configuration.

Haven’t touched linux since my MUD times, so a bit rusty and out of date lol.

#7

Hi,

I have to admit the updating process is next up to get refined. So my apologies for the unclarity.

There will be fresh releases, and update “cookbooks” so in theory the idea is you can just leave your server as-is and run the Chef  update. Which should keep everything in-line without losing any config data. That’s the goal at least. Additionally, add that functionality directly into the cloud-tools.

Basically, a proper updating model is on its way.

Cheers.

#8

It is always a good idea to have a backup

#9

Even when updating your phone os or desktops. There was an iOS update that cleared data of iPad pros