在 Rails 中构建电子商务网站的提示/建议
我即将开始在 Rails 中构建我的第一个电子商务网站。我在 Rails 中编写过其他项目，但从未做过电子商务。
我很想听听人们关于最好的插件、宝石、技巧、技巧或他们认为在 Rails 中构建此类网站有用的任何其他内容的信息。
谢谢大家！
I'm about to start building my first ecommerce site in Rails. I've coded other projects in Rails, but never done ecommerce.
I'd love to hear from people about the best plugins, gems, tricks, tips, or anything else that they found useful in building this sort of site in Rails.
Thanks all!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
使用或至少看看他们如何解决 spree 上的一些解决方案可能是一个好的开始。
Using or at least taking a look at how they've solved some solutions at spree might be a good start.
您还应该查看由 peepcode.com 制作的 活跃商家 pdf！
You also should take a look on the Active Merchant pdf made by peepcode.com!
您可能希望使用活跃商家，因此请选择受支持的网关之一。我个人推荐 BrainTree。您绝对想了解的主要内容是PCI 数据安全标准。除非您真的非常清楚自己在做什么并且愿意承担所涉及的法律责任，否则您希望让网关处理信用卡的存储。通常，您可以向他们发送卡号，他们会传回您可以安全存储的唯一 ID。这确实是要走的路。
或者，您也可以考虑使用 Google Checkout。有些电子商务问题通过外包给谷歌可以得到更好的解决。通常，与您自己的定制电子商务解决方案相比，您使用 Checkout 承担的责任要低，而且在许多情况下，这很重要。另外，如果出现信用卡退款的情况，Google 会代表您进行处理，这非常方便。
You probably want to be using Active Merchant, so pick one of the supported gateways. I personally recommend BrainTree. The main thing you absolutely want to know are the requirements of the PCI data security standards. And unless you really, really know what you're doing and are willing to take on the legal liabilities involved, you want to let the gateway handle storage of credit cards. Usually you can send a card number to them, and they'll pass back a unique ID that you can safely store instead. That's really the way to go.
Alternatively, you might consider Google Checkout. There are a certain class of e-commerce problems that are much better solved by outsourcing them to Google. You typically have lower liability with Checkout than with your own custom e-commerce solution, and in many cases, that's a big deal. Plus Google will go to bat on your behalf in the case of credit card chargebacks, which is quite handy.
首先，在 activemerchant 上观看免费的 Railscast：144 和
如果可以的话，您应该坚持一个非常简单的模型结构：
user has_many :orders、order has_many :items、order has_many :transactions>。 Activemerchant 实际上让您很容易不用担心细节。First, watch the free railscasts on activemerchant: 144 and 145.
There is a very straightforward model structure that you should stick to if you can:
user has_many :orders,order has_many :items,order has_many :transactions. Activemerchant actually makes it very easy to not worry about the details.