Skip to content
The Simplest Way to Manage Your Entire Dev Infrastructure!
Branch: master
Clone or download
Latest commit d36da0d Feb 7, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci circleci config: test command for config added Oct 25, 2017
.ebextensions
.github Create PULL_REQUEST_TEMPLATE.md Aug 3, 2016
.logs Empty .logs directory Jul 20, 2015
.supervisor Empty .supervisor directory Jul 20, 2015
client
config Merge pull request #11466 from mertaytore/inherit-options Oct 25, 2017
deployment deployment: add oud.cc domain Oct 30, 2017
docker/singular
docs removed outdated info Feb 7, 2019
docs_old docs: old docs moved to a new folder Oct 8, 2016
elektron
go go/vendor: update golang.org/x/... repo Nov 24, 2017
install install: remove docker sync script Oct 12, 2016
node_modules_koding Remove Pistachio custom node_module Aug 1, 2017
patches Pistachio: update node_modules with latest stable versions Jan 20, 2017
scripts Merge pull request #11419 from mertaytore/container-per-worker Oct 23, 2017
servers StackScript Search to use POST instead of GET May 10, 2017
tests/specs
versions Versions: remove extra char from versions Jun 23, 2015
website Swagger: update swagger definition for JStackTemplate.preview May 1, 2017
workers xss fix styling Jul 20, 2017
.braveqa change test file extensions Jun 6, 2017
.coffeelintignore
.dockerignore
.env-docker-compose
.env-kubernetes .env-kubernetes: variables for configuration added Oct 5, 2017
.gitattributes
.gitignore
.gitmodules client: jekyll: about: minor typo Oct 27, 2016
.koding.yml .koding.yml added for running koding on koding.com Jul 27, 2016
.npm-install.sh
.npm-postinstall.sh
.npm-preinstall.sh
.nvmrc
Brewfile
CNAME
CONTRIBUTING.md
Dockerfile
LICENSE
Makefile Define klient task May 23, 2017
README.development.markdown
README.gitlab.markdown
README.kdonkd.markdown
README.lp.markdown
README.markdown
README.nodejs-testing.markdown
README.outsourcingworkflow.markdown
README.react-components.markdown
README.softlayer.markdown
README.supervisor.markdown
Vagrantfile
cleanup
codecov.yml codeconv: decrease precision to 1 Mar 17, 2017
coffeelint.json
configure
docker-compose-init.yml
docker-compose.yml
icon.png
package.json Packages: update appmetrics to 3.0.2 to support node 8.x Aug 2, 2017
watch-node
wercker.yml

README.markdown

Koding

Docker Pulls

The Simplest Way to Manage Your Entire Dev Infrastructure!

Koding is a development platform that orchestrates your dev environment. Developers get everything they need to spin up full-stack, project-specific environments in seconds. Share them, update them, and manage infrastructure from a simple interface.

You can try Koding now on koding.com

Quick Start with Docker-Compose

Easiest way to run Koding is to install docker-compose which can be found here. For the rest you can follow these steps:

git clone https://github.com/koding/docker-compose.git koding-docker-compose
cd koding-docker-compose
# Requires docker-compose version >= 1.6
docker-compose up -d

Now you are able to access Koding via port 8090 (e.g. localhost:8090) on your host.

Run Koding on Koding.com

Yes, you can run koding on koding.com by using the provided .koding.yml

For more information about stacks: koding.com/docs

Getting started for Development

You need to install following software packages to run Koding:

Start developing

You are now ready to run Koding.

git clone https://github.com/koding/koding.git
cd koding
docker-compose -f docker-compose-init.yml run init
docker-compose up

If you don't have a powerful computer, this may take a while at first, slow computers may take up to 15 minutes before they build the entire system. Please be patient. Once it is up and running, everything will be smooth and very fast.

Now you can navigate to http://localhost:8090 to see your local Koding instance. Enjoy! (If you don't see it, keep waiting, it will show up)

When you edit files on your host computer, they will be visible in the runtime environment. Watchers will automatically restart backend workers, re-compile frontend code. You don't need to do anything for it.

Tips

If you need to execute some commands in runtime environment, here is how you can start a shell in backend service container:

docker-compose exec backend bash

You can follow coffeescript-styleguide that we are relying on.

Running Koding on Local Machine

This is if you don't want to do docker-compose way and install everything locally, (not recommended).

Software Prerequisites

Start developing

Follow these steps for running the instance:

git clone https://github.com/koding/koding.git /your/koding/path
cd /your/koding/path
node -v # make sure your node version is not greater than `0.10.x`
npm -v # make sure your npm version is 2.15.x
coffee -v # make sure your coffeeScript version must be 1.8
npm install

You should have packages ready for running build specific scripts.

./configure # create necessary config files
./run install # start to install dependencies
./run buildservices # build the services
./run # run all services

As a result, you will have a file watcher watching your backend files (both node, and golang) and restart services when it's necessary. Now open up another terminal and run following commands:

cd /your/koding/path
cd client # move into frontend client folder
npm install # install client dependencies
make # this will run a client watcher for you

Right now you should have 2 different watchers for (1) your backend files, (2)for your frontend client files. Now you can navigate to to see your local Koding instance. Enjoy!

License

This repository is licensed under GNU AGPL V3 Koding Community Edition is licensed under Apache 2.0

Contribute

The main purpose of this repository to continue evolve Koding in order to make it more stable and create the best development experience ever. If you're interested in helping with that, please check our open issues. You can also join the conversation in our slack team!

You can’t perform that action at this time.