I have installed discourse development version on a CentOS 7.7 according to beginners-guide-to-install-discourse-for-development-using-docker/102009
the setup step is:
get source from discourse.git
change config about email sender in config/discourse_default.conf
./d/boot-env --init
./d/unicorn
the hostname is set an IP address like: 10.201.0.115
I can access the discourse use 10.201.0.115:9292
but all of the images can’t show.
Thank you very much.
you mean your website is not published to other user.
but I use the discourse to our company, people use the company local network can access the website.
how can I do at this situation?
@pfaffman
you mean: I just need to confige the DISCOURSE_HOSTNAME= localhost in app.yml?
any thing more?
can you give a example of the correct configration ?
You installed the development version, that is a local install to hack on the Discourse source code. It’s not to be used by multiple people to actually use the software.
ok, thank you very much!
but I have installed another version according to the same address as you give me using the discourse_docker.git instead discourse.git.
what we need to do is we can’t use 80 port which has used by another website.
we must use another port instead 80.
we have change the port to 28080, we main website of discourse can access.
but we get another new problem: the icon or png address is not take the new port 28080, it just use the ip to try get the png, you know, it can’t be reached.
the correct png url address is: http://10.120.0.115:28080/some.png
the wrong png url address is: http://10.120.0.115/some.png
how can i do when we use another port instead 80? @Falco@pfaffman
Look forward to hearing from you.
Discourse must be ran on the standard web ports 80/443. If you can’t let Discourse listen in those ports directly, you should configure a reverse proxy to redirect traffic from those ports to Discourse, preferably using a subdomain.
Again, you need a domain, even if that domain is pointing at 10.202.63.38. I’m sure Jay can help get that set up; you’ll probably have to talk to corporate IT