Rietveld 与 App Engine 有着千丝万缕的联系吗?

发布于 2024-09-12 01:14:21 字数 156 浏览 2 评论 0原文

我一直在寻找 Rietveld 作为我公司缺乏代码审查的解决方案。是否可以在不使用 App Engine 的情况下在内部服务器上进行设置?它似乎有一些 App Engine 特定代码,我不确定它是否可以在普通的旧 Django/Apache 安装上进行设置。我环顾四周,但没有找到任何有关此的信息。

I've been looking at Rietveld as a solution for the lack of code reviews at my company. Can it be set up on a server in-house without using App Engine? It seems to have a bit of App Engine specific code, and I'm not sure it could be set up on a plain old Django/Apache install. I've looked around, but haven't found any information about this.

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

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

发布评论

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

评论(4

忘年祭陌 2024-09-19 01:14:21

请查看 http://django-gae2django.googlecode.com/svn/trunk/examples/rietveld/自述文件

gae2django 项目允许 GAE 应用程序在 django 而不是 GAE 开发环境上运行。

这意味着您可以使用(默认情况下)SQLite 后端直接在 django 下运行 rietveld。您还可以使用 mysql 或 django 支持的任何其他数据库后端。

再加上带有 WSGI 集成的 Web 服务器(例如 Apache),使得本地 rietveld 安装运行良好。

Check out http://django-gae2django.googlecode.com/svn/trunk/examples/rietveld/README

The gae2django project lets GAE apps run against django instead of the GAE development environment.

That means you can run rietveld under django directly, using (by default) an SQLite backend. You can also use mysql or any other DB backend django supports.

That, plus a web server (e.g. Apache) with WSGI integration, makes a local rietveld install run nicely.

流绪微梦 2024-09-19 01:14:21

使用这些提供与 GAE 相同后端服务的项目之一怎么样?

可能还有更多,这些只是我脑海中所知道的。

What about using one of these projects that provide the same backend services as GAE?

There may be more, these are just the ones I know about off the top of my head.

风苍溪 2024-09-19 01:14:21

一些 App Engine 特定代码?它应该是一个示例 App Engine 应用程序,所以是的,它与它有很好的联系。但是,你是对的,它确实使用了 Django,这可以使其移植起来更加可行。我会赞同 @cope360 的建议,但从您的问题的声音来看,您似乎没有对 App Engine 做太多工作。如果只有少数人使用,请尝试在 GAE SDK 本身上运行它。

除此之外,我认为您可以获取“codereview”目录中的大部分代码,并从中构建您自己的 Django/apache 应用程序。

A bit of App Engine specific code? It's supposed to be an example App Engine app, so yeah it's pretty well tied to it. But, you're right, it does use Django which could make it somewhat more feasible to port. I'll second @cope360 recommendation, but from the sounds of your question, it doesn't sound like you've done much with App Engine. If it's only used by a few people, try running it on the GAE SDK itself.

Beyond that, I'd think you could take most of the code in the "codereview" directory and build you're own Django/apache app from that.

一页 2024-09-19 01:14:21

我不会考虑使用端口或其他 GAE 仿真,而是考虑使用 ReviewBoard

审查板是一个功能强大的基于网络的
提供的代码审查工具
开发人员处理代码的简单方法
评论。它从小规模就可以很好地扩展
向大公司提供项目和报价
各种工具来承担大部分
代码审查的压力和时间
流程。

代码审查已经持续太久了
太麻烦了。这很大程度上是
由于缺乏优质工具
可用,让开发人员
诉诸电子邮件和基于错误跟踪器的
解决方案。

我们花费了大量的时间和精力
浪费时间在公开场合进行代码审查
来源项目和公司。在
这两种情况下,代码审查都是
通常通过电子邮件完成。一个
花费了大量的时间
在形成审查请求时,切换
差异和电子邮件之间,以及
试图了解其中的哪些部分
审阅者所指的代码。

因此,为了保持我们的理智和
公开改进流程
源项目和公司,我们
审查委员会写道。我们希望它会是
对您的团队也有用,因此您可以
专注于重要的事情:写作
很棒的产品。

Rather than fussing around with a port or other GAE emulation, I would consider using ReviewBoard.

Review Board is a powerful web-based
code review tool that offers
developers an easy way to handle code
reviews. It scales well from small
projects to large companies and offers
a variety of tools to take much of the
stress and time out of the code review
process.

For too long, code reviews have been
too much of a chore. This is largely
due to the lack of quality tools
available, leaving developers to
resort to e-mail and bug tracker-based
solutions.

We've seen a lot of time and energy
wasted doing code reviews both in open
source projects and at companies. In
both cases, code reviews were
typically done over e-mail. A
significant amount of time was spent
in forming review requests, switching
between the diff and the e-mail, and
trying to understand what parts of the
code the reviewer was referring to.

So in an effort to keep our sanity and
improve the process both in our open
source projects and at companies, we
wrote Review Board. We hope it will be
useful to your team too so you can
focus on what's important: writing
great products.

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