자신의 가정용 서버에 discourse를 설정하는 방법

지원 자체 호스팅
1

안녕하세요,
정적 IP를 사용하여 제 가정용 서버에 discourse를 설치하고 싶습니다.

저는 리눅스에 초보이며 시스템 관리자가 아니므로, 단계별로 순서대로 자세히 알려주시면 감사하겠습니다. 제가 여러분이 가지고 있을 수 있는 리눅스 지식을 갖추고 있다고 가정하지 마세요.

  1. 제 서버는 가정에서 호스팅되며 정적 IP 주소를 사용하고 있습니다(호주 ISP에서는 기본적으로 제공됩니다). 동적 IP를 사용할 때 일반적으로 필요한 dyndns나 기타 도메인 이름 서비스를 사용하길 원하지 않습니다. 세계 다른 지역의 ISP들은 정적 IP를 서비스의 무료 제공 항목으로 제공하지 않는 것 같아, 이 방법에 대해 정보를 찾기가 어렵습니다.
  2. Ubuntu Server 20.04를 설치했으며, 설치 과정에서 docker가 포함되어 설치되었습니다.
  3. Jeff Atwood가 제 필요에 맞는 튜토리얼이라고 말해줬지만, 제 눈에는 아주 직관적으로 보이지 않습니다: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub

이것은 클라우드에 정보를 호스팅하지 않기를 원하는 지역 커뮤니티 조직을 위해 설정하려는 것이기 때문에, Digital Ocean과 같은 호스팅 서비스는 절대 고려 대상이 아닙니다. 그들은 가정용 서버 설치를 매우 강력하게 원하고 있습니다. 따라서 이 작업에 대한 도움을 받을 수 있기를 바랍니다.

2

You can host your solution in the cloud whilst preserving complete privacy. Hence the “Private” in VPS.

Https protocol takes care of obfuscation of communication and this setting:

image
image828×173 28.6 KB

Prevents anyone other than someone authorised reading any content.

As a site you own your own data.

So I highly recommend you reconsider your proposed architecture.

3

This is not a solution my community organisation wants as it does not stop frivolous warrants to snoop on my organizations content.

I think it is important to note that Australia has the worst internet privacy and civil liberties laws in the first world.

Just disallowing anonymous access is still not an option even assuming the hosting provider does not have access to the encryption keys as they can still be ordered to take the site down by the Australian government.

This is why the community organization that I am volunteering for is quite adamant that we self host on our own hardware.

If we can do this using a static IP they do not have to worry about domain name providers also revoking their domain either. Another issue that we have seen a lot of in the last few years.

4

If you have a static IP I’m fairly certain a home setup will be vastly more vulnerable.

5

Even with selfhosted ssl?

Or VPN?

6

OK, let’s put the sense of it aside.

To the matter of getting it to work, you probably just need to install it as root user and follow the guide exactly the same.

If your server has static IP and full internet access, it should not be much different from a VPS.

You need to make sure your firewall is not active and if it is, you have it configured appropriately.

If you have a reverse-proxy in front of docker, same, but if there is no reverse-proxy set up you will in any case end up using the one within the docker container which is set up for you.

Do you have any errors?

7

I know this topic is rather old, but I believe I can add some value as I did this years ago with a self-funded SAAS startup.

Please consider cloudflare for a CDN and DNS proxy. Since this is being hosted on a consumer ISP, both a content deployment network and the anonymity of cloudflare will help tremendously. When you host your own site from your home, you lose a lot of protections that the large cloud hosting providers offer out of the box. Cloudflare will help with some of these.

I hope your throughput was able to handle your visitors as well. Mine was 10mbps upstream and struggled.