blocks|key|445168|text|在这里可能太晚了。但我在github上找到了这个项目，似乎做了你想做的事情，但以一种更干净的方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|445169|https://github.com/logsol/Github-Auto-Deploy|offset|length|445170|看看这个。我也有兴趣知道其他人对此的评论和好评。|445171|干杯,|445172|S|445173|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|18|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|C]]]]

Probably very late to repond here. But I found this project on github and seems to do what you want to do but in a much cleaner way.

<a href="https://github.com/logsol/Github-Auto-Deploy">https://github.com/logsol/Github-Auto-Deploy</a>

Check it out. Would be also interested to know what others think of this in terms of comments and upvotes. 

Cheers, 
S

blocks|key|659381|text|在我目前正在开发的一个项目中，我遵循了Jez+Humble的优秀书籍"Continuous+Delivery“(很值得一读)中介绍的指导方针。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|659382|这意味着使用某种形式的持续集成服务器(我使用的是Go的Thoughtworks免费社区版)创建一个部署管道，负责首先检查代码的质量、复杂性和运行单元测试。然后，它可以遵循部署管道，从而推送到您的生产服务器。|offset|length|659383|这听起来非常复杂，但并不是必须的，它确实使编写代码的整个过程和它进入生产的方式安全和无忧(没有可怕的发布日！)。|659384|我对实时系统使用完整的部署管道，对我编写的npm模块使用精简版本，两者共享相同的1-click部署技术。|659385|entityMap|0|LINK|mutability|MUTABLE|url|http://www.thoughtworks-studios.com/go-agile-release-management^0|0|O|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

In a project I am currently developing I follow the guidelines covered in Jez Humble's brilliant book "Continuous Delivery" (well worth a read). 

This means creating a deployment pipeline using some form of continuous integration server (I use Thoughtworks free community edition of <a href="http://www.thoughtworks-studios.com/go-agile-release-management" rel="noreferrer">Go</a>), that is responsible for first checking your code for quality, complexity and running unit tests. It can then follow a deployment pipeline resulting in a push to your production servers.

This sounds very complicated, but doesn't have to be, and does make the whole process of writing code and it making it's way into production safe and worry free (no scary release days!).

I use a full deployment pipeline for live systems, and a cut down version for npm modules that I write, and both share the same 1-click deployment technique.

blocks|key|659481|text|我刚刚发布了一个基于节点的问题解决方案：node-cd|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|659482|它包含一个运行在VPS上的简单节点应用程序，它将接收Github+post-receive+Hooks并执行您喜欢的脚本(例如，将终止您的应用程序的shell脚本、git拉入并重新启动它)。|659483|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/A21z/node-cd|1|https://help.github.com/articles/post-receive-hooks/^0|K|7|0|0|Q|P|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

I just published a node-based solution to your problem: <a href="https://github.com/A21z/node-cd">node-cd</a>

It consists in a simple node app running on your VPS that will receive <a href="https://help.github.com/articles/post-receive-hooks/">Github post-receive Hooks</a> and execute a the script you like (for example a shell script that will kill your app, git pull, and restart it).

blocks|key|659533|text|下面是另一个简单的nodeJS实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|659534|它是一个非常简单的节点服务器，运行在您配置的主机名和端口上，可以设置为处理GitHub+post接收web挂钩。并且可以定制实际的pul/test/deploy操作来做任何你想做的事情。在当前实现中，它是在nodeJS服务器脚本中以内联方式指定的外壳命令。而且还有一个非常简单的基于secret_key的安全方案。|659535|https://github.com/shyam-habarakada/rscds|offset|length|659536|我的临时服务器已经安装并运行了节点，因此编写起来非常简单快捷。|659537|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|15|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]]]

Here's another simple nodeJS implementation. 

It's a very simple node server that runs on a hostname and port you configure and can be setup to handle GitHub post receive web hooks. And the actual pul/test/deploy actions can be customised to do anything you want. In the current implementation, it is a shell command that is specified inline in the nodeJS server script. And there is a very simple secret_key based security scheme in place as well.

<a href="https://github.com/shyam-habarakada/rscds" rel="nofollow">https://github.com/shyam-habarakada/rscds</a>

My staging server already had node installed and running, so writing this up was quick and easy.

blocks|key|659650|text|为了便于部署，我发现这个项目使用了git。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|659651|git-play|offset|length|659652|我认为这对你来说是合适的方式。|659653|看看这个。|659654|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/interruptz/git-play^0|0|0|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I found the project for easy deployment uses git.

<a href="https://github.com/interruptz/git-play" rel="nofollow">git-play</a>

I think it's proper way for you.

Check it out.

blocks|key|445282|text|如果你想要一个基于python/tornado的解决方案，我写了一个脚本来处理来自Github的Webhook+Services的POST请求。你可以在https://github.com/Akobi/ops/tree/master/autodeploy上找到它|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|445283|它基本上使用了一个JSON配置文件来列出您希望从哪些repos获取推送，您希望在部署时运行哪些命令，以及这些命令必须在哪个目录中运行。您所要做的就是根据自己的喜好修改配置文件并运行脚本！|445284|此外，我使用Nginx作为反向代理将这些帖子转发到我的脚本中。你可以在'+Nginx‘文件夹下的同一个Github库中找到nginx配置。|445285|祝你推得开心！|445286|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.github.com/webhooks/|1|https://github.com/Akobi/ops/tree/master/autodeploy^0|1C|G|0|24|1F|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

If you want a python/tornado-based solution, I wrote a script to handle POST requests from Github's <a href="https://developer.github.com/webhooks/" rel="nofollow">Webhook Services</a>. You can find it at <a href="https://github.com/Akobi/ops/tree/master/autodeploy" rel="nofollow">https://github.com/Akobi/ops/tree/master/autodeploy</a>

It basically uses a JSON config file to list which repos you expect pushes from, which commands you want to run on deploy, and what directory the commands must run in. All you would have to do is modify the config file to your liking and run the script!

In addition, I use Nginx as a reverse proxy to forward these POSTs to my script. You can find the Nginx config in the same Github repo under the 'nginx' folder.

Happy pushing!

blocks|key|445036|text|在我看来，PHP的答案是完全正确的，但是如果你更喜欢Ruby，我在博客上发布了一个解决方案。这和PHP的答案是一样的，只是用了不同的语言。您使用了一个web钩子，并且有一个简单的脚本监听相关的HTTP请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|445037|http://gilesbowkett.blogspot.com/2012/06/heroku-style-deployment-on-ec2.html|offset|length|445038|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|24|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

the PHP answer is totally legit in my opinion, but if you prefer Ruby, I blogged a solution. it's the same thing as the PHP answer, just in a different language. you use a web hook and you have a simple script listen for the relevant HTTP requests.

<a href="http://gilesbowkett.blogspot.com/2012/06/heroku-style-deployment-on-ec2.html" rel="nofollow">http://gilesbowkett.blogspot.com/2012/06/heroku-style-deployment-on-ec2.html</a>

blocks|key|659614|text|我已经创建了我自己的基本部署工具，它会自动从repo+-+https://github.com/jesalg/SlimJim中下载新的更新-基本上它会侦听github+post-receive-hook，并使用代理来触发更新脚本。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|659615|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jesalg/SlimJim^0|T|X|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I've created my own rudimentary deployment tool which would automatically pull down new updates from the repo - <a href="https://github.com/jesalg/SlimJim" rel="nofollow">https://github.com/jesalg/SlimJim</a> - Basically it listens to the github post-receive-hook and uses a proxy to trigger an update script.

blocks|key|445346|text|我是https://commando.io的创始人，最近我们宣布通过一个服务与GitHub集成。该集成允许您在推送到GitHub存储库时在服务器上运行执行。这是在推送代码时自动运行部署脚本的绝佳机会。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|445347|执行是在Commando.io内部编写的脚本，可以用bash、perl、python、ruby、go或node.js编写。要阅读更多内容并查看运行git+pull的示例执行脚本，请参阅我们的博客公告：http://blog.commando.io/run-executions-via-github-push/|style|CODE|445348|entityMap|0|LINK|mutability|MUTABLE|url|https://commando.io/|1|http://blog.commando.io/run-executions-via-github-push/^0|2|J|0|0|21|8|2S|1J|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|H|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I'm the founder of <a href="https://commando.io" rel="nofollow">https://commando.io</a> and recently we announced an integration with GitHub via a service. The integration allows you to run executions on servers when you push to a GitHub repo. This is a perfect opportunity to automatically run deployment scripts when you push code.

An execution is a script you write inside of Commando.io that can be written in bash, perl, python, ruby, go, or node.js. To read more, and see an example execution script of running <code>git pull</code>, see our blog post announcement: <a href="http://blog.commando.io/run-executions-via-github-push/" rel="nofollow">http://blog.commando.io/run-executions-via-github-push/</a>

blocks|key|659781|text|还要注意的是，有一些免费/廉价的服务，比如REPOMAN.IO，它们几乎可以为你自动完成所有这些工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|659782|entityMap|0|LINK|mutability|MUTABLE|url|https://repoman.io/^0|L|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Also note there are free/inexpensive services out there like <a href="https://repoman.io/" rel="nofollow">REPOMAN.IO</a> that automate almost all of this for you.

I have my application (node.js) deployed on a VPS (linux). I'm using git hub as a repository. How can I deploy the application automatically, on git push ?

How can I automatically deploy my app after a git push ( GitHub and node.js)?

单元测试

服务器

GitHub

JSON

我将我的应用程序(node.js)部署在VPS (linux)上。我使用git集线器作为存储库。如何在git推送上自动部署应用程序？

问如何在git推送( GitHub和node.js)后自动部署我的应用？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在git推送( GitHub和node.js)后自动部署我的应用？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在git推送( GitHub和node.js)后自动部署我的应用？
EN