0

Koding

管理整个开发基础设施的最简单方法。（The Simplest Way to Manage Your Entire Dev Infrastructure!）

官方网站
Github 资源库
主要指标

Github星跟踪图

Koding

管理整个开发基础架构的最简单方法！

Koding 是一个协调开发环境的开发平台。开发人员可以在几秒钟内获得构建完整堆栈、特定于项目的环境所需的一切。通过一个简单的接口共享、更新和管理基础设施。

你现在可以在 koding.com 上试试 Koding

Docker-Compose 快速入门

运行 Koding 最简单的方法是安装docker-compose，可以在这里找到。其余的您可以遵循以下步骤。 

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

现在，您可以通过主机上的端口 8090（例如 localhost:8090）访问 Koding。

在 Koding.com 上运行 Koding

是的，您可以使用提供的 .koding.yml 在 koding.com 上运行 koding。

有关堆栈的更多信息，请访问：koding.com/docs

开发入门

您需要安装以下软件包才能运行Koding：

开始开发

你现在准备好运行 Koding 了。

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

如果你没有一台功能强大的电脑，这可能需要一段时间，速度慢的电脑在构建整个系统之前可能需要15分钟。请耐心等待。一旦它开始运行，一切都会很顺利，很快。

现在，您可以浏览 http://localhost:8090 以查看本地 Koding 实例。 请享用！ （如果你没有看到它，继续等待，它会出现）

在主机上编辑文件时，它们将在运行时环境中可见。 Watchers 将自动重启后端 workers，重新编译前端代码。 你不需要做任何事情。

提示

如果需要在运行时环境中执行一些命令，下面是如何在后端服务容器中启动 shell： 

docker-compose exec backend bash

您可以关注我们所依赖的 coffeescript-styleguide。

在本地计算机上运行 Koding

如果您不想使用 docker-compose 方式并在本地安装所有内容（不推荐）。

软件先决条件

开始开发

按照以下步骤运行实例 

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

您应准备好运行构建特定脚本的软件包。 

./configure #create必要的配置文件
./run install #start to install dependencies
./run buildservices＃构建服务
./run＃运行所有服务
./configure # create必要的配置文件
./run install # 开始安装依赖项
./run buildservices # 构建服务
./run # 运行所有服务

因此，您将有一个文件监视程序监视您的后端文件(node 和 golang)，并在必要时重新启动服务。现在打开另一个终端并运行以下命令： 

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

现在你应该有2个不同的观察者（1）你的后端文件，（2）你的前端客户端文件。 现在，您可以浏览查看本地 Koding 实例。 请享用！

许可

这个存储库是在 GNU AGPL V3 下授权的，Koding Community Edition 是在 Apache 2.0 下授权的。

First version: vz 2019/07/27

主要指标

概览
名称与所有者koding/koding
主编程语言Go
编程语言Python (语言数: 14)
平台Docker, Linux, Mac, Windows
许可证GNU Affero General Public License v3.0
所有者活动
创建于2014-06-29 05:46:24
推送于2022-08-15 05:11:42
最后一次提交2019-02-07 21:49:27
发布数5
最新版本名称sandbox-deployment (发布于 )
第一版名称oldkoding (发布于 )
用户参与
星数2.1k
关注者数104
派生数603
提交数97.5k
已启用问题?
问题数935
打开的问题数246
拉请求数9811
打开的拉请求数6
关闭的拉请求数778
项目设置
已启用Wiki?
已存档?
是复刻?
已锁定?
是镜像?
是私有?

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!