Question

我试图利用玩具解决我面临的一个小问题。

I have a development laptop, and develop the majority of my websites on it. If however I am on the move, and someone sends me an SMS reporting a bug for example, I often login to my ftp on any computer there an then, and fix the website live per se.

If i then make an additional change on my development laptop, I often forget about the live change that I have made, and as a result lose it.

因此,我期待着利用玩具来缓解这一问题。

我的托管账户是与东道国共用的托管账户,后者支持特别志愿人员网的存放处。

我正确地认为,特别志愿人员网的工作方式是,我的活本是存放地? 或者我是否失踪了?

难道有人会解释我如何实现我所希望的东西,哪怕需要改变东道方,或者也许更适合我的情况。

Many Thanks.

纽约总部

Answer 1

我不肯定你通过“生命”复印件的含义,但这里指的是你如何与SVN合作。

首先,你有自动备份机,可以上手提电脑,但最好与自动备份相分离。

然后,在你的地方机器上,你有工作副本。工作复印件大多是服务器内容的 clo,但经过当地修改。如果你对你的当地修改感到满意,你就会对服务器作出(提交)改动。如果你不满意你的当地变化,你可以很容易地回到服务器上的版本(或旧版本)。

给生产环境做事与拯救无关。这称为部署进程或释放进程。部署过程通常汇编、支持安装或收集将安装的文档,最后安装/复制结果,以达到生产环境。

The "master" copy of your application/web site should be on the svn server. To get something into production you run a script or follow a manual procedure to get the content from a working copy to the production.

如果你在生产环境中直接编辑文件,就没有解决缺少更新的问题。但是,如果你能远程使用(sh)面粉,你就可以在生产服务器上拥有一份当地工作复制件,在工作复印件中戴上it,并通过指挥线扫描工具加以检查。

Edit
To clarify: your "live" copy should absolutely not be the repository. The repository is not structured like a regular file tree with regular files in it. More like a sequence of changesets.
Your "live" copy should preferably not be a working copy either. The working copy contains special folders and files to keep track of "stuff" that you don t want on your public web site. Your live copy should be a copy of relevant files in a working copy. Either with copy *.html /www-folder/ or svn export or some more elaborate method.

Answer 2

One of the best answer is to use a distributed versioning system where your web-site is a mirror branch or directly the repository (or working copy, it s the same in DVCS).
So you benefit directly from your version control !

你们可以利用Bazaar、Gite或mercurial这样做(或任何其他DVCS,它只是大国)。

友情链接