What happens next?

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

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

Are you self hosting?

1 Like

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”

1 Like

See above then :).

1 Like

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

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

1 Like

Every time i save a new app.yml

I always run a mode-change command

Is it a “good idea” to?

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.

1 Like

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