We’ve moved development of koding.com from our local machines to team on koding.com. It’s a big undertaking, but it’s necessary to do it to understand the day to day experience of using teams on koding.com.
You should have been invited to team.koding.com already. Please do the following:
- Build your stack on https://team.koding.com and follow instructions there to get a working version of koding on your VM.
- Add your team
5... foo.dev.koding.comif you want to develop teams product. The first part,5...is the ip address of your VM. The second partfoois the name of the team.
- Pull latest code from upstream:
git pull --rebase <upstream> <branch> - Update any changed config:
./configure - Start/rebuild required services, i.e. databases:
./run buildservices - Start the workers:
./run backend
To connect your Koding VMs to your local IDE, we’ll use a command line program called: kd To get started, login to team.koding.com and click on http://take.ms/rB1Jm to get link to download kd.
Currently only OSX and Linux are supported. Once it's done installing, kd should be available in your path and you can do kd -h to see list of help topics.
kd help <command>to see help for that command.kd listto see list of your vms.kd mount <alias>:/home/<username>/koding <local folder>to mount your remote koding to your local folder. Remote path needs to be a full path to the folder on your VM.kd ssh <machine name>to ssh into the machine.kd run <command>to run command on remote machine when inside mounted folder.- Alias common commands like
gittokd run, iealias git="kd run git".
- Recursive file read commands like
find -r, oragwill take a long time to complete due to network roundtrip. Usekd runinstead. - In case of fire unmount and mount your machine. In worst case scenarios, do
sudo kd restartto restart kd anddiskutil unmount <local path>to unmount manually. - This is a BETA software, so here be bugs. Open a bug report and they'll all be fixed.