라즈베리파이에서 Discourse 설치 | 블로그

Maybe hardcode that IP in your local hosts file?

3개의 좋아요

Thanks Falco! I will check that out.

2개의 좋아요

I tried hardcode the IP in my client’s hosts file, and the browser always redirect me to the external connection.
Is it possible to provide more than one domain name to the DISCOURSE_HOSTNAME?
Do i need to set DISCOURSE_FORCE_HTTPS: to false to allow local connection? I got this from one of your article.

I am trying to install Discourse on my Raspberry Pi 4 using Dietpi OS and some apps working with Nginx like Nextcloud. I am trying to use Cloudflared service as a tunnel but after the Discourse installation is complete I can’t access Discourse site and i got 502 bad gateway error.

What kind of customization is required on Nginx? Which port should we use?

I applied this guide but without success

1개의 좋아요

My guide assumes that Discourse is the only app on the Pi, and then runs the tunnel exposing the port 80 that is assigned to the Discourse container.

Running multiple apps that share a reverse proxy, while possible, is a more advanced setup and out of the scope of this guide.

1개의 좋아요

I got this working by setting DISCOURSE_BACKUP_HOSTNAME to machinename.local and DISCOURSE_FORCE_HTTPS to false. Now i can access with my domain name and local network domain name.

2개의 좋아요

Well done. Maybe should be a How To in #howto:admins ?

Thanks @merefield. Sure!
There is one problem when using a backup hostname, the images doesn’t display properly.
If the post’s images created with main hostname and when access with the backup hostname, the images will be missing. This also happens in vice-versa.

1개의 좋아요

What happens when you rebake a Post? (Rebuild HTML)

Perhaps you will need to stick to one access address.

Yeah, Rebuild HTML works. But the vpn access is broken because it depends on the local address (backup hostname).

i guess there is no solution to this…

Will this work on an armv7l?

1개의 좋아요

No it won’t. I did try, but there are some missing packages on the 32 bit ARM debian repositories that made it a no go.

2개의 좋아요

The demo site link seems dead

Same as before, I moved houses again. Will plug it back on as soon as I can find it.

3개의 좋아요

now that is the kind of infrastructure bug i like to deal with :joy:

looking forward to giving this a whirl :dizzy:

hope you’re settling in well to your new place @Falco :relieved:

3개의 좋아요

@th21 it’s now back up.

@eh223 thanks :smile:

2개의 좋아요

So I recently got one of these: :+1: :+1:

:eyes: 20231216_12h54m40s_grim :eyes:

And decided to get the development install running, which tbh required a significantly manual effort as the scripted solutions don’t work at present, but :tada:

Thanks to everyone who’s made this possible, very cool indeed! :pray:

12개의 좋아요

What “scripted solutions” work on ANY Pi? I have a few Pi4’s that would like to try this one, but not being a Linux guru, I don’t have the knowledge to deal with manual “dependencies”.

I do have a recursive PiHole running on my network though which I think will allow me to at least deal with the doman name issue…maybe.

2개의 좋아요

Been very happy with mine. I would recommend

  • 8gb Raspberry Pi since mine is regularly hitting 4gb
  • SSD disk. Microsd is too slow.
2개의 좋아요