Hello,
If users with Apache, MySQL, and PHP can install Discourse, I think the market capture of Discourse would increase greatly. Thank you.
Tom
Do users and community managers really care what something is written in?
I recommend reading Why Ruby?
1 个赞
* and the references of that post
1 个赞
Many website administrators need LAMP to build their business websites in addition to Discourse. However, if they deploy Discourse on their LAMP server, the Apache had to use a different port. Some kind of trade off between Apache and Discourse.
But, I do really think that Discourse is a great work!
Well if apache is anything like nginx, i would expect it to be possible to forward different connections/subdomains/hosts to different local ports. discourse listens on one of those ports (or on a unix socket) and the php website listens on another.
i have the feeling we’re going off the original post’s subject.
I don’t know whether that is true, but I do know that will never happen.
What most people do is to run discourse on another server.
2 个赞
If two servers mean two public IP addresses. But many small home users only has one public IP address.
This means they must use iptables rules to set up a DNAT gateway.
Tom
Most admins surely sensibly host in the cloud? Just guessing but suspect that’s a cheaper approach than having business class broadband at home. For the price premium of that you surely could instead afford several VPS servers in the cloud with superior internet bandwidth?
It’s a trade off, man.
I have many data like movies files to stream for my home (via Plex). I have my home server with big size hard drives so that I could backup many of my documents and data there.
For example, you could upload public data to the home server and everyone in the private network could download them if permitted. I have my home private network of 1000 Mbps bandwidth, really fast. But with a cloud VPS, this is not a good plan. The bandwidth between your client and the cloud VPS server might be 100 Mbps or so, but it is unlike that it could be 1000 Mbps.
The cloud computer service has serious disk size limit for above intentions.
Actually, I have my cloud VPS server but I only use it to establish the IPsec connections.
Tom
But you don’t need 100’s of Gigs of storage for small to medium sized communities?
2 个赞
恰好看到这篇帖子，也想在这里发表一下我的看法。
尽管 Web 开发领域总是对某些较新的语言抱有“才是未来”的情绪，但 LAMP 始终是托管网站的基本组成部分，尤其是对于小型企业或组织而言——这与 Discourse 旨在帮助其发展社区的目标受众相同，他们不希望必须设置与其基础设施完全分离的东西，而且我们不应该评判他们如何规划自己的基础设施。人们需要在 LAMP 上使用 Discourse 肯定有其充分的理由，无论具体情况如何。
从软件开发的角度来看，增加一个变体仅仅意味着工作量和市场份额，它不一定总是要取代另一种语言。
话虽如此，考虑到 Discourse 有一些功能可能需要一个常驻内存的守护进程/运行时来进行实时处理，而 Apache 的基本构建方式与此不同，更倾向于即时处理，因此在 LAMP 的使用方面确实存在合理的技术考量。可能需要对某些调整或机制进行完全不同的基础处理，以实现相同的用户体验。
也许有点直白，但那么运行 Discourse 就不适合他们。如果他们不能自己投入精力来运行它，那么他们应该使用托管选项。
在 Apache 服务器（也托管带有 MySQL 的 PHP 应用程序）后运行 Discourse 并非不可能，也不是极其困难。你“只需要”能够运行 Docker 容器。你可以使用 http 或 unix socket 将 Apache 流量代理到 Discourse 的 nginx。所有这些在每月 10 美元的 VPS 上都可以轻松实现，具体取决于流量。
2 个赞