Tommy B

@ronald.fuquay: Custom Stacks are images you can make from an active DevBox. That way you only have to setup your desired environment once, and quickly deploy it unlimited times. One DevBox means can have only one at a time, when you delete it you can make a new one without upgrading your account.

The DevBoxes have a public DNS, but it’s a random string (so you can’t tell which DevBox belongs to who) and all access to it is controlled by you just like on a full fledged server (the default is only your account can access the SSH terminal).

One share means you can receive access to one other users share. You can access the share unlimited times until the share is revoked by the other user. The number of shares you can create and users to share them with is not limited.

You can pretty much install anything on the DevBox, we compiled the templates to make it easier for users to get started. That said, we don’t currently have scripts for setting up other services, your best bet would be to follow the developers instructions or man pages.

You can put your Git URL when creating a new DevBox otherwise you’ll have to do it from the SSH terminal. BitBucket has implemented a “edit in Codeanywhere” button.

We have hinting for html/css/php/and javascript, but no scss at the moment ??

@ nmgwp: For all mission critical stuff, I personally prefer hosting my own environment. But when that’s not the case or simply not viable, hosted services are there and easily accessible.
Codeanywhere does have folder structure and editor for SSH (even on the free plan).

@ronald.fuquay: the free plan comes with 1 DevBox (paid plans have more ofc). They currently do not come with support for sass/scss out of the box, but you can install whatever you need just like on a standard Ubuntu/CentOS machine. The editor does have syntax highlighting for sass/scss but you’ll have to compile via the ssh terminal.

@catacaustic: thumbs up for looking out for the community. I looked over our terms and noticed that it’s not stated clearly enough that all code/data is the sole property of the user and that we have no claims to it. I’ve contacted the guys that handle the legal stuff to fix that.

Hi catacaustic,
I completely understand your concern regarding code ownership and want to say that all code is the sole property of the user.
Users can easily code on their own servers/hosting directly (all code is saved on their own hardware regardless of the status of their account on codeanywhere), save to their own Google Drive/Dropbox/Amazon S3 (again, all code is saved on their own Google Drive/Dropbox/Amazon S3 accounts separate from codeanywhere), or they can chose to run one or more of our DevBoxes. Our DevBoxes are linux containers that are on our hardware (and so is the code/data). All DevBoxes are archived (migrated from the active server to a backup) after 7 days of non-use, and permanently deleted (along with all code/data) after 6 months.

We have several paid and one free plan, so if a user decides (or forgets) to pay for a subscription they will be downgraded to the free plan where they will retain access to all of their code/data/servers.
Coding best practices (and logic) suggest you always keep multiple copies of your code, on multiple locations/providers (whenever possible). Since most of us are coders, we understand that sometimes “stuff” happens and whenever possible will do our best to help even former subscribers. Not because it’s good business but because we’ve all been in similar situations.

As far as the actual code is concerned, as long as it’s not damaging to us or others (viruses, malware, DDoS scripts or similar) we don’t really have any interest in what is coded. We don’t read, analyse, copy (ok, we copy DevBoxes as a whole for backup, but that gets deleted after 6 months) or heaven forbid sell/provide to others.

Disclamer I work for Codeanywhere.com

That being said this is one of the premier use cases of our App. Codeanywhere has over 400.000 Users on the service. So I definitely recommend you try us out.

Also, I would love to hear your feedback as to what you think of it.

Cheers!