如何管理我的项目? (源代码控制、生产服务器/开发服务器)

发布于 2024-10-16 05:30:16 字数 1436 浏览 5 评论 0原文

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

街角卖回忆 2024-10-23 05:30:16

你的标签中有 github(也许是私人帐户,因为 github 太棒了!),所以我建议你学习 git(命令行)。我认为这是最好的。 git 的一大优点是它是分布式。我还敢打赌,如果您努力搜索,您可以找到两个编辑器的插件(就像我很快做的那样):

但我只会使用 cli,因为它的功能实在是太强大了。

you have github(maybe by private account, because github is just amazing!) in your tag so I should suggest to just learn git(Command-line). It is the best in my opinion. One of the nice features of git is that it is distributed. I also bet if you search hard you could find plugins for both editors(like I did quickly):

But I would just use cli instead because it's power is just amazing.

星光不落少年眉 2024-10-23 05:30:16

就版本控制而言,Subversion 是一个流行的选择,并且在我看来很容易设置。看起来它可以与 Dreamweaver 集成 从 CS4 开始,以及 VIM (尽管我不对这些插件没有任何直接经验)。即使没有直接集成,也可以轻松地从命令行使用。在深入研究任何新事物之前,我是 RTFMing 的忠实粉丝,因此 O'Reilly Subversion 书在他们的网站上以免费 PDF 形式提供,这对我来说是一个很大的优势。

为了协调从开发到生产的转变,我个人的建议是尽可能实现自动化 - 我见过这样的情况,其中迁移是由具有检查表的人员处理的,而人为错误似乎最终总是会悄悄出现。如果您最熟悉 PHP,并且主要通过 FTP 访问服务器,则可以使用 PHP 的 FTP 功能可自动将测试的代码从开发服务器移动到生产环境。

As far as version control goes, Subversion is a popular choice, and easy to set up in my opinion. Looks like it can be integrated with Dreamweaver beginning with CS4, as well as VIM (although I don't have any direct experience with either of those plugins). Even without direct integration it's easy to use from the command line. I'm a big fan of RTFMing before digging into anything new, so the fact that the O'Reilly Subversion book is available as a free PDF on their website was a big plus for me.

For coordinating the move from development to production, my personal advice would be to automate as much as you possibly can - I've seen cases in which the migration is handled by a human with a checklist, and human error always seems to creep in eventually. If you're most comfortable with PHP, and you primarily access your servers via FTP, you could use PHP's FTP functions to automate moving the tested code from the development server to production.

别低头,皇冠会掉 2024-10-23 05:30:16

场景:您可以在生产和开发服务器上安装 subversion

  1. 使用 svn,我建议您添加消息,例如 +) 用于添加内容,-) 用于删除(如果发生这种情况),o) 用于修复错误。这会对你以后有所帮助。
  2. 尽可能频繁地提交
  3. 如果您不熟悉 SVN 中的标签和分支,只需列出要在实时服务器上更新的文件列表即可。
  4. 转到实时更新。

场景:你不能在生产服务器上安装 subversion

  1. 在开发服务器上创建一个单独的“实时环境”
  2. 更新它,当你看到所有作品使用任何类型的 FTP、SFTP 将其复制到实时服务器

祝你好运

Scenario : you can install subversion on production and developer server

  1. Use svn and i suggest you add messages like +) for added stuff, -) for removed if that happen, o) for fixed bugs. This will help you latter.
  2. Do commits as offen as you can
  3. If you are not familiar with Tags and branches in SVN, just do the list of files that you are going to update on live server.
  4. go to Live update.

Scenaria : you can't install subversion on production server

  1. create a separate "live enviroment" on developer server
  2. update it, when you see all works use any kind of FTP, SFTP to copy it to live server

Good luck

寂寞美少年 2024-10-23 05:30:16

对于版本控制,几乎所有现代开源版本控制软件都可以,
对于初学者来说,有 Subversion、mercurial、bazar、git。如果您以前从未使用过其中一个,我建议您至少快速浏览一下,看看您喜欢什么。我最喜欢的是 git,但其余的都很容易使用(ish)。大多数公司都提供版本控制即服务(因此您不必自己管理软件),例如 github、launchpad 等。

所有这些都有其优点和缺点,具体取决于您的工作风格和项目。

For version control almost any modern open source version control software will do,
For starters there is Subversion, mercurial, bazar, git. If you've never used one before I would recommend giving them all at least a quick look over to see what you like. My preference is git but the rest are all easy to use (ish). Most have companies that provide version control as a service (so you don't have to gaff with managing software yourself)such as github, launchpad, etc.

All have their benefits and downsides depending on your working style and project.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文