Oh snap!!! Definitely keeping my eyes on this!!
YESSS!!
-Mario
Oh snap!!! Definitely keeping my eyes on this!!
YESSS!!
-Mario
Chris,
Awesome!! Loving the use of Vagrant and Chef for development and deployment. Can’t wait to see the end result. Reach out if you need any testing or support.
Steve
hi i have some problem when installing coronium LS on my DigitalOcean droplet, here the error
digitalocean: STDOUT:
digitalocean: STDERR: fatal: could not read Username for ‘https://gitlab.com’: No such device or address
digitalocean: ---- End output of git ls-remote “https://gitlab.com/coroniumcore/Coronium-LS-ProjectTpl.git” “master*” ----
digitalocean: Ran git ls-remote “https://gitlab.com/coroniumcore/Coronium-LS-ProjectTpl.git” “master*” returned 128
digitalocean: [2016-08-29T15:05:42+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
==> digitalocean: Destroying droplet…
==> digitalocean: Deleting temporary ssh key…
Build ‘digitalocean’ errored: Error executing Chef: Non-zero exit status: 1
==> Some builds didn’t complete successfully and had errors:
–> digitalocean: Error executing Chef: Non-zero exit status: 1
Apologies if this is covered elsewhere, but all the documentation etc on installing on Amazon seems to have disappeared
Is there guidance on getting this working on AWS ?
Really need to look at this as currently using the old Coronium Cloud ( which was brilliant) and need to migrate to LS
You can look here for the previous documentation on deploying LS to AWS https://gitlab.com/coroniumcloud/Coronium-LS-Docs/blob/master/docs/Deploy/Amazon_EC2.md. This has been removed from the latest documentation. We are focusing on Digital Ocean deploys at the moment as the project is rapidly changing.
Steven, hi but im trying to install it on a droplet an little above i posted the error on my terminal, what can i do?
the new error installing coronim LS on my droplet is this
digitalocean: [2016-08-30T15:06:57+00:00] INFO: Running report handlers
digitalocean: [2016-08-30T15:06:57+00:00] INFO: Report handlers complete
==> digitalocean: Gracefully shutting down droplet…
==> digitalocean: Creating snapshot: CoroniumLS-1.3.3-1472569472
==> digitalocean: Waiting for snapshot to complete…
==> digitalocean: Error waiting for snapshot to complete: Timeout while waiting to for droplet to become 'active’
==> digitalocean: Destroying droplet…
==> digitalocean: Deleting temporary ssh key…
Build ‘digitalocean’ errored: Error waiting for snapshot to complete: Timeout while waiting to for droplet to become 'active’
Did you follow the directions here using packer?
digitalocean: Error waiting for snapshot to complete: Timeout while waiting to for droplet to become ‘active’
why im having this error now?
Is EC2 not longer supported? Or will it come back?
I just wonder why there is a screencast for EC2 Installation but not for digital ocean.
Hey guys,
just set up a new Coronium LS Instance on digital ocean.
Also activated SSL.
So hows that working? xD
Is there some kind of dashboard, like there was on the old Coronium?
And how to access it?
Thank you
I have the same error:
==\> digitalocean: Gracefully shutting down droplet... ==\> digitalocean: Creating snapshot: CoroniumLS-1.3.3-1473581909 ==\> digitalocean: Waiting for snapshot to complete... ==\> digitalocean: Error waiting for snapshot to complete: Timeout while waiting to for droplet to become 'active' ==\> digitalocean: Destroying droplet... ==\> digitalocean: Deleting temporary ssh key... Build 'digitalocean' errored: Error waiting for snapshot to complete: Timeout while waiting to for droplet to become 'active'
I followed all steps. The snapshot is there but no droplet. I generated a droplet with the snapshot and it worked, but coronium is not responding.
Any ideas? Would be nice if someone could make a better tutorial on how to set up coronium LS on digitalocean, there are a lot of open questions.
Thanks!
Sunmils and Rene,
Can you check that your API key for Digitalocean is valid?
Same thing happened to me, generated a droplet with the snapshot and it works. Did you do “sudo cloud up” to start the processes?
Also to the other poster, no, there isn’t a dashboard that I’m aware of.
I will use my coronium 1.93.5 instance @ EC2, that causes me less friction, and for my needs it seems to be sufficient.