Aptana 同步远程更改
我使用部署向导设置了 Aptana Studio 3,以便从本地/远程两个方向同步我的项目的更改。这对于将本地更改同步到远程站点来说效果很好;我的更改会自动通过 FTP 上传。
当文件远程更改时,它似乎不起作用 - 有几种情况,我打开了一个自上次下载以来已被其他人修改的文件,并且远程更改尚未下载到我的本地副本。
在开始处理目录之前,我一直在手动同步目录,但这是一个有点烦人的解决方法。 Aptana 是否可以自动检查远程更改并同步我的本地副本?
I have Aptana Studio 3 set up using the Deployment Wizard to sync changes in both directions from local/remote for my projects. This works fine for syncing local changes to the remote site; my changes get FTP'd up automatically.
It doesn't seem to be working out when a file has changed remotely - there have been several situations where I've opened a file that has been modified by someone else since I last downloaded it, and the remote changes have not been downloaded to my local copy.
I've been manually synchronising directories before starting to work on them but this is a bit of an annoying workaround. Is it possible for Aptana to automatically check for remote changes, and sync my local copy?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我发现了一个错误报告,它几乎回答了我自己的问题: https://jira.appcelerator.org/ browser/APSTUD-2811
不幸的是,这个问题似乎不会很快得到解决。在我看来,这是一个非常重要的功能,特别是对于那些在团队中工作的人来说。
I found a bug report which pretty much answers my own question: https://jira.appcelerator.org/browse/APSTUD-2811
Unfortunately it doesn't look like this is going to be fixed any time soon. It's a pretty essential feature IMO, especially for those working in teams.
您应该考虑使用 Git 来移动文件(加上整个版本保存功能)。
如果您对本地开发系统进行更改,只需
将其拉到部署服务器上即可。
全部完成。
如果您在部署服务器上进行更改,只需在部署服务器上提交该更改,然后将该更改拉至您的开发计算机即可。虽然 FTP 在移动未跟踪的二进制文件时确实派上用场,但实际上不再需要那么多了。
http://try.github.com/levels/1/challenges/1
You should consider using Git for moving files around (plus the whole version saving feature).
If you make a change on your local development system, simply
And then pull it down on your deployment server.
All done.
If you make a change on your deployment server, simply commit that change on the deployment server, and subsequently pull that change down to your development machine. There isn't really that much of a need for FTP anymore, although it does come in handy for moving untracked binary files.
http://try.github.com/levels/1/challenges/1