版本控制系统建议

发布于 2024-10-11 06:25:08 字数 473 浏览 3 评论 0原文

我的独立开发工作已经到了一个阶段,我想开始使用 Subversion 技术。

到目前为止,我只是通过导出当前数据库并将它们与 PHP 项目文件压缩在一起来进行备份。

我在网上阅读了一些文章并观看了 Linus Torvalds 的视频 - 普遍的结论似乎是 Git 已经流行,旧的 CVS 技术已经过时。

我目前不在 Linux 下操作,我在 Windows 下完成所有 PHP 工作 ->蚀。由于Eclipse运行在JVM上,跳入Linux ->除了文件系统之外,Eclipse 或多或少会是透明的。

我想要实现的是能够保持不断的修订历史记录 - 但我希望这几乎是完全透明的。另外,我在 MVC 框架中工作,我希望能够向设计师发布我的视图,并让它们也可以在版本控制系统中工作。

Egit 能满足我的需要吗?或者对于一个人的劳动力来说,这是否意味着太多的开销? 您建议我使用什么来保留修订历史记录?

我还要求服务是免费的!

I've reached a point in my independent development work where I would like to start using Subversion techniques.

Up to now, I've been simply making backups by exporting my current database, and zipping them together with my PHP project files.

I've read some articles online and watched a video with Linus Torvalds - the general verdict seems to be that Git is in and old CVS techniques are out.

I'm not currently operating under Linux, I do all PHP work out of Windows -> Eclipse. Due to the fact that Eclipse runs on JVM, jumping into Linux -> Eclipse will be more or less transparent - file system aside.

What I would like to accomplish is being able to keep a constant revision history - But I want this to be almost entirely transparent. Also, I work in an MVC framework, and I would like to be able to release my views to Designers, and have them work from within the revision control system too.

Will Egit accomplish what I need? Or is it too much overhead for a one-man workforce?
What do you recommend I use so that I can keep a revision history?

I also require the service to be free!

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

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

发布评论

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

评论(3

心头的小情儿 2024-10-18 06:25:08

使用 Git 或 Mercurial


曾几何时,cvs 几乎完全取代了它的竞争对手并统治了版本控制的世界。

然后它本身被svn取代。

现在,svn 已被 git 取代。

Gitsvn 更复杂,因此 svn 项目很可能只想继续攻击而不进行转换。

但 svn 的日子已经屈指可数了。 GitMercurial 和一些专有系统显然是 VCS 世界的未来。甚至还有与其他类型的存储库交叉操作的机制。

最后,转换很容易,因为 git 可以与中央存储库一起使用,就像它是 cvs 或 svn 的(快得多)版本一样。

Use Git or Mercurial


Once upon a time, cvs almost completely replaced its competition and ruled the world of version control.

Then it was itself replaced by svn.

And now, svn has been replaced by git.

Git is more complex than svn, so an svn project might well want to just keep bashing along and not convert.

But svn's days are numbered. Git, Mercurial, and some proprietary systems are clearly the future of the VCS world. There are even mechanisms to cross-operate with other types of repositories.

Finally, the transition is easy, because git can be used with a central repo just like it was a (much) faster version of cvs or svn.

小苏打饼 2024-10-18 06:25:08

尝试这些搜索

https://stackoverflow.com/search?q=free+svn+hosting

https://stackoverflow.com/search?q=free+mercurial+hosting

至于选择哪一个 - 我倾向于同意Google 评论

  • 学习曲线。 Git 的学习曲线比 Mercurial 更陡峭
    由于多种因素。 git 有
    更多命令和选项,音量
    其中可能会吓到新人
    用户。 Mercurial 的文档倾向于
    更完整、更容易
    新手必读。水星的
    术语和命令也是
    更接近 Subversion 和 CVS,使得
    对于从这里迁来的人们来说很熟悉
    那些系统。

  • Windows 支持。 Git 有着深厚的 Linux 传统,并且
    在Windows下运行它的官方方法
    就是用cygwin,还差得很远
    从a的角度来看是理想的
    Windows 用户。基于 MinGw 的端口
    Git 越来越受欢迎,但 Windows
    仍是“二等公民”
    在 Git 的世界里。基于有限
    测试中,MinGW 端口似乎是
    功能齐全,但有点
    迟缓。正常情况下的操作
    在 Linux 或 Mac OS 上感觉即时
    X 花了零点几秒
    视窗。 Mercurial 是基于 Python 的,
    和官方发行版运行
    在 Windows 下干净利落地(以及
    Linux、Mac OS X 等)。

但他的无疑是最关键的:

维护。 Git需要定期
存储库的维护(即
git-gc),Mercurial 不需要
这样的维护。但请注意,
Mercurial也少了很多
管理方面成熟
客户端磁盘空间(请参阅客户端
上面的存储管理)。

我不想对 git 存储库进行“维护”。这是不可接受的。

摘要

在实施工作方面,
Mercurial 具有明显的优势,因为
其高效的 HTTP 传输协议。

就功能而言,Git更
强大,但这往往会被抵消
因为使用起来更加复杂。

我还没有将所有的东西都转移到 Mercurial - SVN 对于大多数项目来说都很好 - 特别是单人项目。

Try these searches

https://stackoverflow.com/search?q=free+svn+hosting

https://stackoverflow.com/search?q=free+mercurial+hosting

As for choosing which one - I tend to agree with the google review here:

  • Learning Curve. Git has a steeper learning curve than Mercurial
    due to a number of factors. Git has
    more commands and options, the volume
    of which can be intimidating to new
    users. Mercurial's documentation tends
    to be more complete and easier for
    novices to read. Mercurial's
    terminology and commands are also a
    closer to Subversion and CVS, making
    it familiar to people migrating from
    those systems.

  • Windows Support. Git has a strong Linux heritage, and the
    official way to run it under Windows
    is to use cygwin, which is far from
    ideal from the perspective of a
    Windows user. A MinGw based port of
    Git is gaining popularity, but Windows
    still remains a "second class citizen"
    in the world of Git. Based on limited
    testing, the MinGW port appeared to be
    completely functional, but a little
    sluggish. Operations that normally
    felt instantaneous on Linux or Mac OS
    X took several tenths of a second on
    Windows. Mercurial is Python based,
    and the official distribution runs
    cleanly under Windows (as well as
    Linux, Mac OS X, etc).

But his is the hands-down clincher:

Maintenance. Git requires periodic
maintenance of repositories (i.e.
git-gc), Mercurial does not require
such maintenance. Note, however, that
Mercurial is also a lot less
sophisticated with respect to managing
the clients disk space (see Client
Storage Management above).

I don't want to have to do "maintenance" on the git repos. That's just unacceptable.

Summary

In terms of implementation effort,
Mercurial has a clear advantage due to
its efficient HTTP transport protocol.

In terms of features, Git is more
powerful, but this tends to be offset
by it being more complicated to use.

I have not moved all my stuff to mercurial - SVN is just fine for most projects - especially single-person projects.

睫毛上残留的泪 2024-10-18 06:25:08

我正在使用 unfuddle,它对我有用。

解开

Unfuddle 是一个安全的托管项目
软件管理解决方案
开发团队。

我们知道您没有时间
让服务器启动并运行,然后
配置和保护代码
存储库、票务系统和
有价值的项目管理工具。

以下是一些功能:

  • 项目

    <块引用>

    从事许多不同的项目并且
    在一个范围内管理它们中的每一个
    单个 Unfuddle 帐户。每个项目
    有自己的一套门票,
    里程碑、消息和笔记本。

  • 仪表板

    <块引用>

    仪表板是
    项目的信息。在短短的一个
    一目了然,您和您的团队可以轻松
    查看源最近的任何更改,
    消息、票证以及任何即将到来或
    较晚的里程碑。

  • 门票

    <块引用>

    解开门票可帮助您的项目
    保持井井有条。优先级、评论
    然后将您的门票分配给
    您的团队成员。

  • 无痛 Subversion 和 Git 托管

    <块引用>

    正是您所期望的:
    无限的 Subversion 和 Git
    您的每个项目的存储库
    帐户,可快速访问
    直接从内部项目源代码
    您的浏览器。

  • 消息

    <块引用>

    消息都是关于简单和
    有效的沟通。如果你的团队
    无法很好地沟通你的项目
    会受苦的。

  • 人物与人物权限

    <块引用>

    Unfuddle 为您提供
    对您的内容进行细粒度的控制
    团队可以做到。

I am using unfuddle and it is working for me.

Unfuddle

Unfuddle is a secure, hosted project
management solution for software
development teams.

We know that you don't have time to
get a server up and running and then
configure and secure code
repositories, ticketing systems and
valuable project management tools.

Here are some features:

  • Projects

    Work on many different projects and
    manage each of them from within a
    single Unfuddle account. Each project
    has its own set of tickets,
    milestones, messages and notebooks.

  • The Dashboard

    The Dashboard is the hub of
    information for a project. In just a
    glance, you and your team can easily
    see any recent changes to the source,
    messages, tickets and any upcoming or
    late milestones.

  • Tickets

    Unfuddle tickets help your project to
    stay organized. Prioritize, comment
    upon and then assign your tickets to
    your team members.

  • Painless Subversion and Git Hosting

    Exactly what you would expect:
    Unlimited Subversion and Git
    repositories for each project in your
    account, with quick access to the
    project source code right from within
    your browser.

  • Messages

    Messages are all about simple and
    effective communication. If your team
    cannot communicate well your project
    will suffer.

  • People & Permissions

    Unfuddle provides you with
    fine-grained control over what your
    team can do.

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