In http://www.koding.com/docs/getting-started-c-cpp, the example code, (as seen on chrome on my chromebook, at least), does not have any file target after "#include", and my attempt failed until I included "<"stdio.h">" afterwards. Those "<" may be the culprit, perhaps, especially since they dont show on the preview here, either (without the extraquotes)?
copied from page
"

include

void main(){
printf("Hello world\n");
}
"

https://learn.koding.com/guides/upgrading-your-vm/

First you should always run apt-get update to update the repository indexes.

Then, In the description of apt-get you say that you use apt-get dist-upgrade to upgrade ubuntu files like the kernel and apt-get upgrade to upgrade packages. This is a common misunderstanding due to a badly named option for apt-get. However the man page explains it correctly:

dist-upgrade
dist-upgrade in addition to performing the function of upgrade, also intelligently handles
changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution
system, and it will attempt to upgrade the most important packages at the expense of less important
ones if necessary. The dist-upgrade command may therefore remove some packages. The
/etc/apt/sources.list file contains a list of locations from which to retrieve desired package files. See
also apt_preferences(5) for a mechanism for overriding the general settings for individual packages.

IMO, you should ALWAYS use apt-get dist-upgrade or you risk not upgrading a dependency and wondering why the new version of an app is crashing.

Next, you should always reboot after updating your system.

And finally, after the reboot run apt-get autoclean to get rid of old packages that may now be orphaned (ie if the new version of some package you want is no longer dependent on a particular package that only it was using, get rid of that package)

So, in summary, my recommended sequence of updating your VM is:

sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot

wait for the reboot

sudo apt-get autoclean

I tried setting http://mojolicio.us with the sample app they provide, it works fine on my workstation but on Koding it doesn't. I don't get where's the issue, can someone put a guide for that? If I am able to solve this, I'll post the guide and close this issue, till then, keep this open.

https://learn.koding.com/guides/connect-with-ssh-windows/

I believe the entire section about setting up a local proxy is unnecessary unless you have some weird firewall setup.

When I attempted to replace the sftp subsystem for the few lines mentioned on the docs, it resulted in openssh not starting. I could not login with ssh or filezilla. I did exactly what the article told me.

https://koding.com/docs/ssh-into-your-vm is pointing to https://github.com/koding/kdlearn/blob/master/faq/vm-address which doesn't exist any more.

Hi, I'm not a command line expert or even linux user. But after installing wordpress and following this guide it wasn't allowing me to upload anything to wordpress (no themes, no images, nothing), even though I did run the command:

sudo chown -R :www-data wp-content/uploads

so after an extensive day of googling I ended up running these two other commands in the terminal @ Koding, which are quite similar :

sudo chown -R www-data:www-data /var/www/wordpress/wp-content/uploads
sudo chmod -R 755 /var/www/wordpress/wp-content/uploads

and that solved it. I'm not 100% sure what these commands do (as I said Im no terminal or experienced user) but Im writing this in case there needs to be and update for this guide, by an experienced user. Adding maybe one of these commands and prevent future users with issues have this solved.

Deep into Step three, we are told to use the limited console that comes up with the combo CTRL-ALT-T, with command ssh.

But my Chromebook is telling me that "that feature has been removed"

I'm looking to work through the process using the Secure Shell official app. It looks like: