blocks|key|3746732|text|对于一些项目，我使用Capistrano进行推送。它构建在ruby之上，并且使用ssh使得部署脚本编写变得非常容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3746733|在其他项目中，我有一个小型部署应用程序，它使用bash将svn导出到一个临时目录，然后将其rsync到实时服务器。您可以使用ssh使rsync。|3746734|我非常喜欢Capistrano方法，即使你的项目不是ruby/rails。|3746735|entityMap|0|LINK|mutability|MUTABLE|url|http://www.capify.org/^0|A|A|0|0|0|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|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

For some projects I use <a href="http://www.capify.org/" rel="nofollow noreferrer">Capistrano</a> to push out to live. It is built on top of ruby and makes deploy script writing super easy and uses ssh. 

On other projects I have a tiny deploy app that uses bash to do an svn export to a temporary directory and then rsync it over to the live server. You can make rsync use ssh.

I greatly prefer the Capistrano method, even if your project isn't in ruby/rails.

blocks|key|708628|text|您总是可以编写一个小型的客户端/服务器应用程序，它在源端加密，推送文件，然后在目标端解密。这是一点工作，但可能是微不足道的。只要你的自动化工具支持在文件系统中执行某些东西(我想所有的都支持)，它就是可以脚本化的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|708629|唯一的缺点是，如果您没有做更多的工作，您可能无法在集成环境中获得关于失败的有意义的错误消息(尽管这可能与向stdout发送错误消息一样简单，具体取决于您的设置)。|708630|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You could always write a small client/server app that encrypts at the source, pushes the files, and then decrypts at the destination. That's a little bit of work, but probably a trivial amount. And it's scriptable as long as your automation tool supports executing something in the file system (which I think all do).

The only downside is that you may not be able to get meaningful error messages on failure in your integration environment without a bit more work on your part (though depending on your setup, this could be as simple as sending error messages to stdout).

blocks|key|5157726|text|嗯，这里我们使用登台“服务器”在实时环境(实际上，它是生产服务器上的一个apache虚拟主机)上进行测试，并使用araxis+merge+(一个非常智能的逐行文件比较工具)来同步开发和登台。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5157727|测试完成后，只需替换生产webroot上的文件:)|5157728|/mp|5157729|entityMap|0|LINK|mutability|MUTABLE|url|http://www.araxis.com/merge/index.html^0|1K|C|0|0|0|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|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

hm, around here we use a staging "server" for testing purposes on the live environment (actually, its an apache virtual host on the production server) and <a href="http://www.araxis.com/merge/index.html" rel="nofollow noreferrer">araxis merge</a> (a really smart line-by-line file comparison tool) to sync development and staging.

once its tested, just; replace the files on the production webroot :)

/mp

blocks|key|3747048|text|这似乎是使用SFTP可以轻松完成的事情。看看PuTTY+(psftp和pscp)或者Windows的WinSCP，或者Unixes的rsync和OpenSSH。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3747049|entityMap|0|LINK|mutability|MUTABLE|url|http://www.chiark.greenend.org.uk/~sgtatham/putty/|1|http://winscp.net/eng/docs/introduction|2|http://rsync.samba.org/|3|http://www.openssh.org/^0|M|5|0|1E|6|1|1U|5|2|20|7|3|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]|$A|Y|B|Z|1|10]|$A|11|B|12|1|13]]|C|$]]|$1|D|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]|P|$5|G|H|I|C|$J|Q]]]]

This seems like the sort of thing that could be done easily with SFTP. Take a look at <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/" rel="nofollow noreferrer">PuTTY</a> (psftp and pscp) or <a href="http://winscp.net/eng/docs/introduction" rel="nofollow noreferrer">WinSCP</a> for Windows, or <a href="http://rsync.samba.org/" rel="nofollow noreferrer">rsync</a> and <a href="http://www.openssh.org/" rel="nofollow noreferrer">OpenSSH</a> for Unixes.

blocks|key|5158039|text|创建一个实时站点目录的副本，使用rsync将该副本更新为最新版本，然后重命名实时目录和更新后的目录，以便更新后的版本现在是实时的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5158040|在bash中：|5158041|#!/bin/bash

set+-e
cp+-R+/var/livesite+/var/newversion
rsync+user@devserver:/var/readytogolive+/var/newversion
mv+/var/livesite+/var/oldlivesite
mv+/var/newversion+/var/livesite|code-block|syntax|javascript|5158042|维奥拉！|5158043|编辑：@Ted+Percival+-这是个好主意。我甚至不知道"set+-e“这个词。更新的脚本。Edit:在Ted的建议下再次更新(尽管我认为如果cp命令以某种方式失败了，它仍然可以工作，如果cp失败，您可能会遇到更严重的问题。)|5158044|entityMap|0|LINK|mutability|MUTABLE|url|http://samba.anu.edu.au/rsync/^0|G|5|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Make a copy of your live site directory, use <a href="http://samba.anu.edu.au/rsync/" rel="nofollow noreferrer">rsync</a> to update that copy with your latest version, then rename the live and updated directories so that the updated version is now live.

In bash:

<pre><code>#!/bin/bash

set -e
cp -R /var/livesite /var/newversion
rsync user@devserver:/var/readytogolive /var/newversion
mv /var/livesite /var/oldlivesite
mv /var/newversion /var/livesite
</code></pre>

Viola!

Edit: @Ted Percival - That's a good idea. I didn't even know about "set -e". Updated script. Edit: updated again at Ted's suggestion (although I think it would still work if somehow the cp command failed, and if cp fails you probably have more serious problems.)

blocks|key|3747237|text|@Neall，我会在第二行添加一个set+-e，因为如果rsync由于任何原因失败，你都不希望实时站点被替换。如果脚本中的任何命令失败，set+-e会导致脚本退出。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3747238|编辑:脚本中的第一个内容应该是#!/bin/bash之后的set+-e。|3747239|entityMap^0|H|6|S|5|1W|6|0|F|B|T|6|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

@Neall, I'd add a <code>set -e</code> on the second line, because you don't want the live site being replaced if the <code>rsync</code> fails for any reason. <code>set -e</code> causes the script to exit if any of its commands fail.

Edit: The <code>set -e</code> should be the first thing in the script, right after <code>#!/bin/bash</code>.

blocks|key|5158262|text|我将附和Capistrano的建议，但是如果您正在寻找基于图形用户界面的解决方案，可以尝试Webistrano前端。干净的、基于ssh的、合理的部署和回滚语义，以及通过ruby实现的简单脚本和可扩展性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5158263|entityMap|0|LINK|mutability|MUTABLE|url|http://www.capify.org/|1|http://blog.innerewut.de/webistrano/^0|4|A|0|19|A|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I'll second the recommendation for <a href="http://www.capify.org" rel="nofollow noreferrer">Capistrano</a>, though if you're looking for a GUI-based solution you could try the <a href="http://blog.innerewut.de/webistrano/" rel="nofollow noreferrer">Webistrano</a> front end. Clean, ssh-based, sane deployment and rollback semantics and easy scripting and extensibility via ruby.

blocks|key|704118|text|在我做的一份自由职业工作中，我们设置了三个独立的环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|704119|704120|一个开发服务器，ran使用CruiseControl继续构建。任何签入都会触发构建。QA测试是在这里进行的。|unordered-list-item|704121|A测试服务器，即用户验收测试是在这里进行的|704122|704123|工作流程如下：|704124|704125|Developer签入对SourceControl.|ordered-list-item|704126|CruiseControl生成的更改并将生成部署到开发人员。|704127|开发人员通过QA后，运行用于部署开发人员生成以进行测试的robocopy脚本。更新|704128|704129|测试|704130|在测试通过后，运行robocopy脚本将测试部署到PRD。H220|704131|704132|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|13|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|N|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|N|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|N|7|1A|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1B|8|@]|9|@]|A|$]]|$1|V|3|W|5|N|7|1C|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|Z|$]]

On a freelance job I did, we set up three seperate enviroments.

<ul>
<li>A Dev server, that ran continues builds using CruiseControl. Any check-in would trigger a build. QA Testing was done here.</li>
<li>A Test Server, that user acceptance testing was done on.</li>
<li>Production.</li>
</ul>

The workflow was as followed:

<ol>
<li>Developer checks in changes to SourceControl.</li>
<li>CruiseControl builds and deploys the build to Dev.</li>
<li>Dev is QA'ed</li>
<li>After passing QA, a robocopy script is ran that deploys the Dev build to Test.</li>
<li>Test is UAT'ed</li>
<li>After Test passes, a robocopy script is ran that deploys Test to PRD.</li>
</ol>

So, in your experience, whats the best way? Is there a secure way that's also scriptable/triggerable in a build automation tool?

Edit: I should mention this is windows/.net and I'll be deploying to iis6

Whats the best way to securely publish a site post build?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

那么，根据你的经验，最好的方法是什么？在构建自动化工具中，有没有一种安全的方式也是可脚本化/可触发的？编辑:我应该提一下这是windows/.net，我将部署到iis6

问安全发布网站的最好方法是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安全发布网站的最好方法是什么？EN