What happens next?

Product Support Self-hosting

AI-generated summary

In the topic What happens next?, Ethsim2 asks whether updating their self-hosted Discourse instance (via Docker Manager) requires rebuilding and if any plugins listed in their app.yml need removal. merefield confirms no plugins need to be removed and advises upgrading via command line or online. Ethsim2 clarifies they’re self-hosting on an Ionos VPS in the UK and also uses a mail-receiver.yml, which they note isn’t a plugin. Later, Ethsim2 updates that three plugins — Discourse Calendar, Discourse Math, and Discourse Graphviz — are now bundled with Discourse core, so they plan to remove them from app.yml. They also ask if running chmod 700 on app.yml after editing is a good practice 8. merefield explains that if the file already exists, permissions don’t need to be reset, and notes that chmod 700 on the parent directory is sufficient for security — also suggesting text copy over photo uploads for accessibility. Ethsim2 replies they’ve been running as root and applied chmod 701 to the containers directory during setup, viewing the extra file-level restriction as harmless. The discussion centers on safe, self-hosted Discourse upgrades, plugin management, and filesystem permissions.

1

Hey Discourse Team,

my Docker_Manager is ready to be “bumped” by 1 commit

deos this mean i’ll need to rebuild again?

If yes,

will any of the following plugins need removing from my app.yml

2

You do not need to remove any plugins. Just upgrade, either online or by command line.

3

Are you self hosting?

4

yes i am self-hosting on one of those Ionos Virtual Servers in the UK

I also have a mail-receiver.yml and understand this deosn’t count as a “Plugin”

5

See above then :).

6

IMG_0848
IMG_08481206×829 110 KB

I imagine there will be no plugins to remove, but if there is when i rebuild (after some time), i can update this topic with which of the plugin(s) that was

7

is now bundled with discourse core :tada:

is now bundled with discourse core :tada:

is now bundled with discourse core :tada:

As a self-host person, I will remove all three from my app.yml now

8

Every time i save a new app.yml

I always run a mode-change command

IMG_0850
IMG_08501206×253 79.5 KB

Is it a “good idea” to?

9

Not sure I understand this. Why do you need a “new” file?

If the file already exists, you are not creating a new file and the existing file permissions will remain?

The recommended chmod command is in the standard install instructions (though that’s on the directory).

If I understand this correctly:

  • chmod 700 on the directory means only you (the owner) can enter/read/list/write in that directory or see its contents.
  • Even if a file is world-readable (e.g. chmod 644), nobody else can access it because they can’t get into the directory in the first place.

btw, are you able to take screen snippets or even better just copy the text? Your camera photos will be less accessible to search etc.

10

Thanks! I was running as root the whole time, so I set chmod 701 containers during setup. I figured applying chmod o-rwx to app.yml after CTRL+X in nano …wouldn’t conflict — just adds a bit of extra restriction on the file itself. Alike when i applied to mail-receiver.yml