Translations are usually merged on Tuesdays. I like to look at Commits · discourse/discourse · GitHub to check whether new translations were merged because then I want to update Discourse
Discourse is much more modern than many of the other platforms you mentioned, and so its foundation is different - written with Ruby, and running with Docker - it’s quite a learning curve but I do think it’s worth it (some of these things like Docker will pay off to understand in the future I think, and generally administration is quite smooth and it’s generally very stable with a pretty healthy development ecosystem from what I can tell).
And I’m not surprised there’s very little on the Chinese internet about it… perhaps that will change with time, but ultimately it’s not just a matter of language barrier, there are actual technical barriers as well.
Keep up the effort! You will succeed! Your translation suggestions and the issues here will also help others set up Discourse more smoothly.
I was previously using the SMF forum software (PHP-based and kind of retro) before discourse and I can understand where you’re coming from. Those forum softwares were a bit more logical and organized with it comes to admin stuff. However, I can happily report that after spending a little less than two days digging around in the Discourse admin section, I’m starting to get quite used to it. So I think it’s just very overwhelming in the very beginning, but the change in Discourse’s approach starts to pay off very quickly as it is incredibly customizable and truly future-proof. I wish you the best of luck!
Edit: spelling errors
I agree discourse is non trivial to set up, and it’s the first large project I’ve interacted with that’s written in ruby / rails.
The only actually difficult issues, however we’re with first getting outgoing emails setup, the suggested email providers won’t even talk to someone running a small volume. There was an additional day invested in setting up incoming emails, which many of our user base insist on .. everywhere you find people who don’t care to interact with a new service 
.
We also bricked our install, somewhere between me trying to do something I didn’t realize was impossible (nesting more than 2 levels of categories), then trying to delete what I’d done … simultaneously to a dev I’d shared root privileges with breaking some things trying to run another site alongside on the same host. .. had to reinstall and recreate all categories.
Completely worth it
Thanks! Really appreciated reading all your feedback for our product. We’re definitely trying to simplify the admin experience and will be making improvements in the areas you’ve mentioned.
We also usually have our new hires run through a self-hosted setup on a provider, so we’ll try and run through that again to see what we can streamline.
By the way from your screenshot, the translation key above says
js.notifications.titles.linked_consolidated
so it isn’t “likes” → “点赞”, but should be “link” → “链接”
There is a similar key
js.notifications.titles.likes_consolidated
which would be “点赞” though.
There is a command line to allow nesting subcategories beyond just 1 level. Have to do a search. But have mine set to allow 3 parent\subcat1\subcat2
Brevo com is pretty good in their free teir
I think you mean this?
Yes that is the one. Thanks
Hello! I recently tried a self-hosted installation under a Chinese cloud server and it didn’t encounter any complicated problems.
I guess the documentation seems a bit lacking here. In fact, the templates folder of the standard Docker installation already has built-in files to solve the Chinese network environment: web.china.template.yml
But I realized that this file doesn’t seem to be mentioned in the documentation. And this file also needs to be updated to solve the recent problem of China blocking docker.io
I have installed around 20 instances with the official guide (discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub) without any issues…
If you use the Alibaba Cloud region Hong Kong, there are no network environment blockers.
However, I think installing discourse does require some degree of experience in coding or how a website works (DNS, domain, network port, etc.) at least you should be comfortable reading the above guide.
If not, either you need someone to help you or dig the internet to find more documents ( mostly not in Chinese)
A small tip is that using English as the admin interface language will help you search faster and more accurately when you run into an issue, saving you time in finding the word mapping between Chinese vs English. Also in case you need to upload a screenshot asking for help. After you are familiar with it you can switch it back anytime ( I do this when I install my first instance)
그 이유는 Discourse가(노력하고 있지만) 다른 어떤 소프트웨어도, 심지어 유료 제품도, 하물며 무료 소프트웨어는 더더욱 제공하지 못하는 수많은 아름답고 명확한 기능들을 제공하기 때문입니다.
많은 옵션이 필요하면, 결국 sooner or later '옵션의 정글’이 될 수밖에 없습니다. 그리고 Discourse 팀은 이 '정글’을 가능한 한 질서 정연하게 유지하기 위해 열심히 노력하고 있습니다. 따라서 우리는 비판과 함께, 마음속에 칭찬을 함께 가지는 것이 좋다고 생각합니다.
(게시글이 작성자에 의해 삭제되었습니다)
이 말의 정확한 의미를 좀 더 구체적으로 설명해 주실 수 있을까요? 오해가 있는 것 같습니다. 여기에는 자체 서비스 약관이 있으며(Terms of Service - Discourse Meta), 이를 템플릿으로도 제공하고 있습니다(관리자들에게 약관을 읽어보고, 필요 시 자문 변호사와 상의하며, 임의로 수정하도록 권장합니다)… 하지만 대부분의 Discourse 사이트는 독립적으로 운영되므로, 우리는 소송 차단이나 직접적인 집행에 관여하지 않습니다.
discourse.org에서 호스팅을 직접 구매하는 사이트는 저희 호스팅 약관(Discourse Self-Serve Hosting Terms | Discourse - Civilized Discussion)을 준수해야 합니다… 단, 관리자들이 저희 규칙(주로 법률 준수와 관련)을 따르는 한, 그들이 자체 사용자에게 설정한 약관에 대해서는 개입하지 않습니다.
실수했어. 실수로 디스코드로 착각했었어. 정말 오해였지.
그때 내가 뭘 하고 있었는지는 모르겠지만, 디스코드와 관련된 것이라서 내 머릿속에서 자연스럽게 디스코스로 인식한 것 같아.
그렇지 않으면 디스코스는 그 자체로는 정말 좋은 도구야, 아무 문제 없어.
디스코드는 실제로 사용자 소송을 차단하는 데 꽤 나빠.
디스코드에 익숙하지 않은 사람인 것 같으니, 이 발언을 좀 더 자세히 설명해 주시겠어요?
그리고 디스코urs에서 그런 불편함을 느끼지 않으시나요?
어떤 회사에서 제품을 구매했는데, 그 제품이 너무 불량해서 누군가 심각한 피해를 입는다면, 그것은 회사의 책임입니다. 하지만 구매 과정에서 회사가 사용자에게 알리지 않은 채 소송 제기 가능성을 자동으로 차단하는 조항을 설정해 두었다면, 그 책임이 회사에 있더라도 사용자는 불리해질 수밖에 없습니다. 기본적으로 Discord에서 일어나고 있는 일은 바로 이런 것입니다. 만약 미래에 어떤 문제가 발생하게 될 경우를 대비해, 약관에 사용자 소송을 차단하는 항목에 자동으로 체크를 해 두어 소송 제기를 막고 있는 것입니다.
아니요, 그들은 사용자 소송을 차단하는 어떠한 조치도 시행하고 있지 않습니다. 그들의 제품이 어떤 방식으로든 저에게 해를 끼친다면, 여전히 소송을 제기할 권리가 있습니다. 온라인 토론 플랫폼에서 사용자 소송을 차단하는 것이 큰 영향을 미치지는 않을 수 있지만, 도덕적으로 우리의 권리를 침해하는 것은 분명합니다.