The new Cloud9 development environment
41–50 of 76 posts
Re: The new Cloud9 development environment
#42The only complaint i have after 3-4 hours of ruby dev was performance when it appears i’m doing anything IO related on my container. For example re-seeding the test database, or even startup times of the test rails container.
For example right now here is a screenshot of the terminal: https://www.dropbox.com/s/w8b29sn8fjabbr3/Screenshot%202014-...
(56 load average? Swap almost full? Yikes)
That said, the features are solid and i was able to get up and running very quickly. Assuming the are just having some growing pains from launching the new services today, I’m definitely going to consider switching over to c9.
I haven’t checked the forums to see if there is a way to re-launch my project onto a different server to try and get better performance.
Re: The new Cloud9 development environment
#43I thought this was going to be Cloud9 from bell labs..
Re: The new Cloud9 development environment
#44Re: The new Cloud9 development environment
#45I thought this was going to be Cloud9 from bell labs..
Re: The new Cloud9 development environment
#46I've been playing today with the new version, loaded in a project i have been using in Nitrous.io and have been really happy with c9 so far. The only complaint i have after 3-4 hours of ruby dev was performance when it appears i’m doing anything IO related on my container. For example re-seeding the test database, or even startup times of the test rails container. For example right now here is a screenshot of the ter…
Re: The new Cloud9 development environment
#47I've been playing today with the new version, loaded in a project i have been using in Nitrous.io and have been really happy with c9 so far. The only complaint i have after 3-4 hours of ruby dev was performance when it appears i’m doing anything IO related on my container. For example re-seeding the test database, or even startup times of the test rails container. For example right now here is a screenshot of the ter…
As you can imagine we're getting a big load of traffic on release day. Which is fine; we have many servers hosting these containers. Some new ones are being spawned as the traffic increases. What we're finding now, though, is that we need to tune our load balancing logic, especially for the scenario where many new users show up. This requires the use of some other metrics than the "normal" scenario with many users le…
That said, poking around I realized I can create and edit projects on my own server. I just spun up a 2G droplet on digital ocean and was playing around with the SSH connector and i am beyond impressed. Ideally I'd prefer to manage my own system resources, but being able to drop in and work on my project from any browser on hardware that I can control, upgrade and allocate is very nice and feels more sustainable at least for my case.
Re: The new Cloud9 development environment
#48Re: The new Cloud9 development environment
#49Still no word on the OSS part. Last commit on master was November last year. I like it as a service for my personal use and OSS work. But employers will mostly not allow me to use a hosted service to edit their code; I've tried.
Re: The new Cloud9 development environment
#50Earlier quoted context omitted.
The new version is based on a completely new code base. We have a new core and eventually ported and rewrote most of the old plugins one by one. We're working on the APIs and documentation right now and want to bring the new version to github again pretty soon.
Awesome to hear! Looking forward to checking it out. Are you guys still using Architect? I love that module but I always felt it had a lot more potential -- wasn't sure if there were plans to enhance it at all.