Originally published at: Free Hosting for Open Source v2
Nearly two years ago we started very carefully experimenting with free hosting of open source projects. Today we’re announcing the next iteration of our free hosting program, casting a much wider net this time. Free Discourse Hosting For Your Open Source Project Do you run a popular open source project? Then you might be eligible…
37 个赞
How will this affect communities in the V1 program?
5 个赞
Projects on the legacy plan will continue to be hosted under the terms that applied when they signed up, meaning they will not need to change their domain names.
13 个赞
This is incredible!!! Thanks so much @erlend_sh and Discourse team!!!
7 个赞
All credit to @erlend_sh he has been driving this forward!
12 个赞
@erlend_sh We’d like to move Gitcoin to use the free version possible. Does this allow for a custom domain? If not, how do we qualify for the 50% off?
1 个赞
The free plan no longer allows for custom domains. The 50% discount is generally for not-for-profit open source projects, which puts Gitcoin in a bit of a grey area. But since it literally exists for the purpose of supporting open source that tips the scale in your favour 
I’ll send you a PM to discuss specifics.
6 个赞
When you say you can’t help import existing mailing lists and the like, does that mean it’s still possible for us to do it manually or only if we self-host? We have 17 years of mailing lists to not lose and we’re really not trying to self host anything anymore 
2 个赞
You can absolutely do it yourself. All our import scripts are open source, so you can set up a local dev site and run the import. From there, you can take a backup of your dev site, upload it to your free hosted site, and shoot us an email. We’ll work with you to restore the backup.
9 个赞
Awesome, guess I know what I’ll be doing this weekend 
3 个赞
Are you sure? The opening post explicitly says:
1 个赞
Yes, I’m quite sure . We will not assist with imports, but we’re happy to restore a Discourse backup, whether that backup is from an import, another hosting site, self-hosting, etc.
Let me see if I can edit the copy there a bit to be clearer.
7 个赞
FAQ in the linked blog post updated.
6 个赞
你好 
我不明白为什么在这些开源 Discourse 实例中 allow_restore 参数被禁用了。
虽然不提供需要 SSH 登录服务器并进行技术操作的自定义导入支持看起来很自然，但从 old.discourse.example.org 迁移到 new.discourse.group 本质上只是一个文件保存/打开操作，不需要任何技术知识。我是不是漏掉了什么？
4 个赞
我们的整个托管服务已禁用恢复功能，包括免费版、标准版、商业版和企业版。这与我们的开源托管无关。出于安全和客户支持的考虑，即使对于免费用户，我们也会代为处理恢复操作。
10 个赞
啊，好的，谢谢 @jomaxro，我之前没明白原因。
4 个赞
正在设置其中一个。我们希望启用通过 GitHub、Twitter 和 Google 登录。这是否可行？我们能否按常规方式设置？还是说，由于它托管在你的 discourse.group 域名下，Discourse 可以为我们处理此事？
如果我记得没错的话，在这些平台中的一个或多个上设置应用需要验证顶级域名（TLD）。
1 个赞
具体是哪一个？
我们有很多用户在 discourse.group 下使用社交登录。我测试的第一个站点使用的是 GitHub 和 Google。
5 个赞
好的，太棒了！感谢确认。我之前没做过多少次这类操作，容易忘记那些很久没执行的步骤。我会查看一下，如果遇到任何问题再联系你。
4 个赞
谢谢团队！看来这个功能在管理面板中也能找到。抱歉问了个新手问题，非常感谢你们的帮助！
1 个赞