颠覆 Dreamhost 尾声

发布于 2024-08-13 00:09:12 字数 414 浏览 10 评论 0原文

我是一名中级 Web 开发人员,我正在尝试将 Subversion 集成到我的工作流程中。我已经认识到,这是值得学习的重要事情,可以使我免于将来重写问题的噩梦。

我当前的主机是 dreamhost,我已经与他们一起设置了 subversion,并且我已经使用版本(对于 mac)检查了该项目(我的语法可能与这里有很大出入),并且一直在使用 coda(对于 mac)来提交更改。

当我访问服务器上存储我的提交的目录时,它们会呈现为纯文本。目前,当我提交某些内容时,我还会将 ftp 上传到不同的目录,这样我就可以查看实际的站点。我可以在 coda 中回滚到不同版本,然后通过 ftp 上传。

我不确定我这样做是否正确,我是否仍然应该并排提交和 ftp 上传,或者我可以只进行提交并将最新的提交显示为渲染的网页而根本不接触 ftp 吗?

我说得有道理吗?

I am a intermediate web developer, I am attempting to integrate subversion into my workflow. I have come to the understanding, that it is something important to learn, and can save me from rewrite issue nightmares in the future.

My current host is dreamhost I have setup subversion with them, and I have checked out the project(my syntax may be way off here) with versions(for the mac) and have been using coda(for the mac) to commit changes.

When I visit the directory my commits are stored in, on the server, they are rendered as plain text. Currently when I commit something I also ftp upload to a different directory, so I can view the actually site. I can rollback in coda to different versions and then upload via ftp.

I am not sure if I am doing this properly, am I still supposed to commit and ftp upload side by side, or can I just do the commits and have the most recent commit show up as a rendered webpage without touching ftp at all?

Do I make sense?

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

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

发布评论

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

评论(3

临风闻羌笛 2024-08-20 00:09:12

你是对的。您想要将代码提交到存储库,然后通过 ftp 传输到您想要进行更改的服务器。如果您回滚存储库中的代码,则可以通过 ftp 传输更改的文件。

简单的问题:您能够在本地测试您的代码吗?如果没有,您可能需要采用此工作流程:

  1. 更改代码。
  2. 通过 ftp 上传到 Dreamhost 上的开发目录,您可以在其中查看和测试。
  3. 如果存在错误,请修复它们并重复。
  4. 当您的更改生效后,将更改提交到 subversion
  5. 然后将文件上传到生产目录(其中的内容是实时的)。

这样,您就不会意外地将损坏的代码传输到您的生产环境。

You are correct. You want to commit your code to the repository, then ftp to the server where you want the changes to be. If you rollback your code in the repository, you can then ftp your changed files.

Quick question: Are you able to test your code locally? If not, you may want to go with this workflow:

  1. Make changes to code.
  2. Upload via ftp to a development directory on Dreamhost where you can view and test.
  3. If there are bugs, fix them and repeat.
  4. When your changes are working, commit your changes to subversion
  5. Then upload your files to the production directory (where things are live).

This way, you never accidentally ftp up broken code to your production environment.

空袭的梦i 2024-08-20 00:09:12

www.beanstalkapp.com 是一个托管的颠覆服务,可以为您完成这一切。您可以将其与 coda 很好地集成,然后从他们的站点进行部署。

看看它。

www.beanstalkapp.com is a hosted subversion service that can do all this for you. You can integrate it nicely with coda, then deploy from their site.

Take a look at it.

情丝乱 2024-08-20 00:09:12

由于 Dreamhost 提供对大多数(所有?)托管帐户的控制台访问,您可能只想在服务器上签出您的存储库,以便在从本地开发环境提交后进行更新。所以,像这样:

  • 对本地项目进行编辑
  • 提交本地项目以存储
  • SSH 到 Dreamhost,cd 到站点所在的目录
  • svn up

这就是我所做的(使用几乎完全相同的工具集,减去 Coda)并且它有效完美,您不必搞乱 FTP。

Since Dreamhost offers console access to most (all?) hosting accounts, you'd probably want to just have a checkout of your repo on the server that you can update after you commit from your local dev environment. So, something like this:

  • Make edits to local project
  • Commit local project to repo
  • SSH to Dreamhost, cd into the directory where your site lives
  • svn up

That's what I do (using almost exactly the same set of tools, minus Coda) and it works perfectly and you wouldn't have to mess with FTP.

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