So I did all the setup and I was able to successfully run the server command - bundle exec rails server --binding=0.0.0.0 . But instead of seeing the message Server listening on PORT 3000, I only see DB queries as logs in the command line.
Can someone point to the direction, why I don’t see the server listening log ?
So I am running this inside a Ubuntu VM and once the server is up, I can access it using the ip address of the vm and port 3000. But ya for general usage.
That’s a development install, are you a coder / computer programmer intending to write Discourse plugins or contribute to the Discourse open source source code? You said
For general usage follow the install guide I linked, you don’t want the development install.
I am a coder but I am not willing to write any plugins etc, just want to setup discourse forum add on for my website. Where people can go and share their topic of concerns and me and my team can answer them.
Hi @Falco so let’s say I see the standard output on development mode, but if I go to that vm ip address and on port 3000, I don’t see anything, could there be anything that I am missing.
To setup discourse on gcp, I follow this url - https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md , instead of digital ocean, I created an ubuntu VM on gcp and tried the setup, when I came to the step of setting the hostname for my discourse , I have a registered domain but I wasn’t able to attach it and it gave me error.
By default development only binds locally, so other devices in the same network can’t browse it. You can use standard rails flags to change the behavior.
What do you mean by “attach” a domain?
Domain must point to the instance public IP, and instance must have the standard web ports open. One of the reasons we recommend Digital Ocean is that non-technical users have difficult opening ports in cloud providers, which doesn’t happen on simple VPS providers.