Which is the better option to self-host?

installation
1

Hi everyone, I was thinking about self-hosting a Discourse forum, and I wanted to know 2 things:

  1. Where should I host the forum on? Docker, or my Raspberry Pi?
  2. How would I deploy it if it’s on my Pi/Docker?

I’m still unsure about the options; personally, I’m fine with either for 1, but for 2, that’s the main question.

2

This is not a choice :slight_smile:

Deployment on Raspberry Pi would be on Docker :slight_smile:

In any case you want to use the standard install.

(for general interest see this Topic: Discourse on a Raspberry Pi | Blog)

2 Likes
3

So I would have to install Docker on my Pi?

1 Like
4

@merefield May I ask why not install it (Docker) on my computer instead? What difference would it really make?

5

The easiest way to install Discourse is and has always been deploying to a VPS in the cloud.

Deploying locally on any computer is less optimal, but can be done.

Often people have a raspberry pi lying around not always fully engaged and it’s a fun and educational hobby project to do.

Running on your main PC? Well I don’t think you want sessions of Rocket League impacting performance of your Discourse instance? :slight_smile:

3 Likes
6

Right. I’ll try out the Pi setup and see what I can do.
Will post back here if I have any updates.

7

Is that a tacit admission of Rocket League participation? :wink:

Good luck!

2 Likes
8

Quick question, will it be free if I follow the guide on the Github repo? Or will DigitalOcean be paid?

9

Digital Ocean is but one supplier you can use for a VPS install.

If you are using a Raspberry Pi you will not be using Digital Ocean.

I suspect you will have to pay for an Email Service provider to handle outgoing emails though, but follow the guide.

3 Likes
10

Should be the last question:
Could I do this instead?

11

What is it you want?

A working production install or a development install?

This is for the latter

1 Like
12

Any is fine, I suppose. I could try the second one then put it in production with the first one, I guess.
I’ll go try them out; thanks for the help!

13

For use nothing, for installing something.

I have a rasp lying down and holding my personal photo gallery, for example. It doesn’t waste electricity too much and I don’t expose my laptop to every other users. Because I’m using already Discourse as a private notebook I could use raspberry for that because I don’t have need to access it from outside world and at same time I could save close to 10 buck a month VPS bills.

That is one reason. Matter of choise, nothing else.

1 Like
14

Alright. So here are the issues I encountered. Note that this was on my Pi.
First, I tried setting it up with the Docker installation guide for development. I encountered a problem eventually when running d/rails s, as it said that the container was restarting, and I had to wait until it has started. I simply stopped and deleted the container (this may not have been the best course of actions).
Then, I attempted to try the Ubuntu/Linux development guide (this one), but also couldn’t continue when I tried bundle install, saying that bundle was not found. I attempted to clone the repo to another folder and try, but to no avail.
Eventually, I rm -rfd both folders and uninstalled Docker, preparing for another battle with the terminal tomorrow.
Do you guys @merefield and @Jagster have any suggestions?

15

I suggest you use the supported production install.

The docker dev install is intended for Ubuntu and you will have to resolve the issues yourself if you choose to try that on the pi.

16

Just to make sure I understand you, I will have to run this? Is it possible to do it on a Pi instead?

1 Like