Then modified the app.yml file to include my postgreSQL & Redis details along with host, notifications & so on.
When I run sudo ./launcher bootstrap app
I get following error message
Status: Downloaded newer image for discourse/base:2.0.20180802
cd /pups && git pull && /pups/bin/pups --stdin
/usr/bin/docker: Error response from daemon: could not get container for data: No such container: data.
See ‘/usr/bin/docker run --help’.
cat: cids/app_bootstrap.cid: No such file or directory
“docker rm” requires at least 1 argument.
See ‘docker rm --help’.
Usage: docker rm [OPTIONS] CONTAINER [CONTAINER…]
Remove one or more containers
rm: cannot remove ‘cids/app_bootstrap.cid’: No such file or directory
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
Is this a fresh install or an upgrade? Which installation instructions are you following?
You normally shouldn’t have to edit the .yml files for a basic install, ./discourse-setup should handle all that for you.
If there isn’t a specific need for separate containers and a more complex setup I would just follow https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md and keep it as simple as possible until you have the instance up and running.
I’m unfamiliar with the data.yml container but it’s probably meant to handle persistent storage in a fully cloud-native installation like on Kubernetes when overlayfs isn’t an option.
…oh wait data.yml is the postgres server container I think. It should probably be paired up with web_only.yml instead of app.yml but I would really just go with the easy single-container setup unless you have a good reason to split it up.
You probably also have to build build the redis and postgres containers before the rest, have you tried “./launcher bootstrap data” and “./launcher bootstrap redis” ?
When you say “my own” do you mean outside of docker, or just the separate containers? I don’t think providing your own postgresql and redis is officially supported, you would have to pick apart the scripts to see how the Discourse bootstrap process configures everything…
Only catch for me that was not documented (maybe stating the obvious) but you have to grant Can Login permission to your new Discourse user in the database.