遗留代码的版本控制帮助

发布于 2024-07-18 01:13:34 字数 566 浏览 7 评论 0原文

我正在为遗留系统寻找某种备份/版本控制方法:

  • 系统是用 BASIC 版本开发的。 这是一个解释版本。 程序以一些伪代码的形式保存; 不是纯文本。
  • 所有制作程序都存储在同一文件夹树中,并根据类别分为多个文件夹。
  • 除了将要修改的程序的先前版本存储到名为 old_versions 的子文件夹中之外,没有颠覆策略。 每个类别文件夹内都有一个 old_versions 子文件夹。 示例:/programs/accounts_payable/old_versions/
  • 程序在生产环境中动态修改。
  • 系统在Solaris服务器上运行

我想要一些实时备份的方法,每个修改的程序都存储在单独的位置。没什么花哨的。 它不需要进行回滚或更改比较。 它只需要保存程序的最新版本

谢谢。

PS:是的,我真的很愤怒,也很绝望。

I'm looking for some kind of backup/version-control method for a legacy system:

  • Systems are developed in a version of BASIC. It's an interpreted version. Programs are saved in some pseudo-code; not pure text.
  • All production programs are stored in the same folder tree, divided into folders depending on the category.
  • No subversion strategy, apart from storing the previous version of the program being modified into a subfolder named old_versions. There is one old_versions subfolder within every category folder. Example: /programs/accounts_payable/old_versions/
  • Programs are modified on the fly, in the production environment.
  • System run on a Solaris server

I would like some method of real-time backup of, every program modified, stored in a separate location. Nothing fancy. It doesn't need to do rollbacks or change-comparisons. It just needs to SAVE THE MOST RECENT VERSION OF THE PROGRAM.

Thanks.

PS: Yes, I'm really angry and desperate.

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

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

发布评论

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

评论(4

╰つ倒转 2024-07-25 01:13:34

在不改变开发流程的情况下,也许一种方法是在 shell 脚本中使用 rsync 或类似的方法,每 xx 分钟拍摄一次快照,并将它们发送到另一个位置。

我认为最好的解决方案是迁移到 VCS,我个人推荐 git 或 svn,并停止在生产中编辑代码。 如果需要,您始终可以使用 svn export 来获取干净的树。

Without changing your development process, perhaps one way would be to use rsync or similar in a shell script to take snapshots every xx minutes, and send them to another location.

I think the best solution would be to migrate to a VCS, personally I'd recommend git or svn, and stop editing code in production. You can always svn export to get a clean tree if needed.

|煩躁 2024-07-25 01:13:34

IBM Tivoli 可能适合您。

我以前以大约 50 美元的价格购买过它。 它监视您设置的文件/文件夹的更改,并将副本(或增量,我不知道)写入您指定的位置。

我希望能给您一个该程序的链接,但在与 IBM 网站进行了 5 分钟的斗争(再次)之后,我沮丧地放弃了。 他们的产品很可靠,但他们的网站或购买方法却不然。

IBM Tivoli might be something for you.

I have purchased it in the past for about 50$. It monitors changes to files/folders you have setup and writes a copy (or delta, I don't know) to a location you specify.

I wish I could give you a link to the program but after fighting 5 minutes with the IBM website (again) I gave up in frustration. Their products are solid, their website or methods to purchase them are, well, not.

谜泪 2024-07-25 01:13:34

如果在生产环境中动态修改软件,我会谦虚地建议实时备份并不能解决您的问题。 它可能会解决错误的结果,但完全忽略根本原因。

If software is being modified on the fly in the production environment I'd humbly suggest that real-time backups are not the solution to your woes. It potentially solves a faulty outcome while completely ignoring the root cause.

暗地喜欢 2024-07-25 01:13:34

你可以看一下 rsnapshot; 请参阅http://www.rsnapshot.org/。 它可以创建目录树的多个快照,使用硬链接文件来节省文件未更改的空间。

You could take a look at rsnapshot; see http://www.rsnapshot.org/. It can make multiple snapshots of a directory tree, using hard-linked files to save space where a file hasn't changed.

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