Currently discourse is hosted in Docker by nginx! but you could add an option in the discourse-setup where instead of nginx just discourse itself runs (so that discourse reaches via :3000>)… Furthermore, another option in the installer could make discourse run on a port other than 3000! The EXPOSE will be automatically adjusted accordingly! Discourse could then be reached via a reverse proxy over a domain
إعجاب واحد (1)
Again: that can be done already. It is really trivial task.
إعجاب واحد (1)
Yes, but it should be possible to do it without major configurations
إعجاب واحد (1)
It is not a major configuration. It is just another typical virtual host configuration what you have to do everytime no matter what is listening at backend; WordPress, Moodle or Discourse under Docker. Plus one really minor change on app.yml: what port discourse will listen.
إعجابَين (2)
Which variable in de app.yml would this be?
إعجاب واحد (1)
As you said here Content Security Policy: The settings of the page have blocked the loading of a resource ("script-src") - #19 by Justman10000 you should expose only 90:80.
إعجاب واحد (1)
discourse-setup is intended to support only the most basic installations. If you’re doing something like using a reverse proxy then it’s assumed that you know enough about how things work that it’s easier to use a text editor than run a script that asks a whole bunch of questions.
4 إعجابات