שאלת אחסון עצמי פרטי

סיכום מבוסס בינה מלאכותית

In a discussion titled “Private Self Hosting Question” under the Hosting category, jakedn expresses interest in setting up a private family Discourse server using Docker but encounters challenges, including the need to run management scripts as root and desire to place it behind a reverse proxy container that doesn’t connect to the internet (accessible only via VPN). They also ask if email verification can be disabled for such a private use case. merefield suggests that while not a direct answer, Discourse can be deployed publicly yet made 100% private and invite-only. jakedn acknowledges this option but prefers network-level segregation via VPN, already having other services running this way. Thomas_Rother shares their own setup: running Discourse in a KVM VM with Docker under Proxmox VE, using HAProxy for SSL termination to expose only one IP address for multiple internal services — offering a practical example of isolating Discourse behind a reverse proxy in a private environment.

I really enjoy using discourse on different forums I joined!

Learning it is open source, I want to make a private family server with discourse, but I am running into a few issues.
It seems while using docker discourse has its own management script that needs to be run as root.
How would I go about adding it behind a reverse proxy container that doesn’t connect to the internet (only accessed through vpn)?
Is there a way to disable email verification for such a use case?

I am aware that this isn’t the target use case for discourse. Has anyone tried setting it up for a private company/family purpose ?

לא תשובה ישירה, אך שים לב שאתה יכול לפרוס לאינטרנט הפתוח וגם להפוך את Discourse שלך ל-100% פרטי ובהזמנה בלבד.

לא ידעתי שזו אפשרות.
עם זאת, יש לי את ה-vpn מוגדר ושירותים אחרים כבר פעילים.
אני אוהב להפריד את הרשת מהאינטרנט כאשר יש לי אפשרות.

I have the discourse installation in a KVM VM with docker, with proxmox VE for virtualization. Access from Internet uses haproxy for ssl termination, that allows to expose only one IP address, even for different services on the Internal network.