Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our community
SupportiveGullveig's Experience
Top Con
•••
Top Con
•••
Top Pro
•••
Edward Wissler's Experience
Top Pro
•••
Top Pro
•••
Top Pro
•••Top Con
•••Top Pro
•••
Top Pro
•••Top Pro
•••
Top Pro
•••Top Pro
•••
Terrible customer service. Has a failing grade with the BBB and questionable billing. See More
The custom domain feature fails at the SSL cert, even if you are bringing your own via Cloudflare, etc. Running on port 80 appears to break the site. This is especially frustrating when you paid an extra $24 for 15 custom domains that you cannot use. Support is non-existent so they will not help resolve the issue. See More
Codeanywhere relies on right click for major actions but doesn't support this interaction on iPad. Selecting listed Dev box URLs to access site is also unworkable in practice. iPad app allows the actions but has very limited set of Dev box controls. Using an external keyboard with the app can also be problematic as the arrow keys don't work. See More
CodeAnywhere recently partnered up with DigitalOcean. Now users can manage, spin up and provision DigitalOcean droplets all from the CodeAnywhere IDE. This is a great addition for both products, combining the power of an affordable host with the portability and power of CodeAnywhere IDE. See More
It's new!!! Supports sharing my containers via SNS to be helped or co-work. See More
Koding uses the Ace editor that's developed by Cloud9. Besides the basics, it covers most important advanced code editor features such as code folding, converting cases, auto-completion, code analysis and refactoring, regex search and offers easy access to relevant documentation. It also gives access to the CLI, has support for Vim and Emacs keybindings, includes multiple cursors and zen coding mode that removes all distractions and allows focusing on code. See More
Every software project on sourceLair is backed up by the Source Control Manager of your choice; Git or Mercurial. Clone repos, commit, pull and push changes and work with branches on the cloud without having to install and configure anything or worry about compatibility between your Source Control Manager and the system of your choice. See More
Allows anyone to build and test your application from anywhere. Starts a Docker image and mounts your project into it, allowing your to control the runtime environment. Out of the box Che uses Docker as runtime provider but can use a remote SSH or many other. A custom Stack is basically you writing a Dockerfile. See More
Eclipse Che is single user without even any authentication (it's recommended to run it behind Nginx to add authentication). One can run an instance for each user, or switch to Codenvy (which is a multi-tenant, multi-user, elastic implementation of Che). Currently it is unsafe to deploy it on a publicly accessible network, and Che behind Nginx isn't enough, because other ports don't use HTTP protocol and also require no authentication. See More
Che injects an SSH daemon into workspace machines. Connect your existing IDE–Eclipse if you like–with an SSH sync point. Upload your key pair or have Che generate a new pair for each workspace. You can also access your workspace with Che's browser terminal, giving you root access to workspace machines. See More
The workspace in Che includes project sources, IDE and the runtime. So if you hand your Che workspace definition to another user and they execute it they will get everything they need to build, run and debug the project. Also the runtime is in a container so it will work even if the second user is on a different OS than the original user who shared their workspace with them. See More
Eclipse Che uses workspace "factories" to create replica environments for anyone who clicks on a factory link. The workspaces generated are based on recipes that can be run in any Kubernetes orchestration platform. This includes recipes that generate multiple connected containers (via compose file or Kubernetes YAML). This makes it trivial to replicate a developer's workspace with others on the team. See More
Because the VM image is managed by Google and either provided entirely by Google or configured by a Dockerfile (which is regularly rebuilt), packages are far more likely to be kept up-to-date with the last patches and security fixes compared with Cloud IDEs that give you your own VM and make you, yourself, in charge of applying updates. See More
If your GitHub repositories does not have a manifest to make a stack, Gitpod will attempt to make a stack based on what it understood about your codebase. However, for popular projects, a central repository on GitHub exists to configure a workspace automatically for them without the manifest file to be present. See More