Nope. We have a front-end Node.js app that talks to our backend Discourse docker containers. Users only interact with our Node.js app, so they never see Discourse.
Nope. I’m saying that I want to write our Discourse .yaml files that are used to build a container to our own personal Git. But when I create a dev environment and run a git init on the “/var/discourse” folder which contains /bin, /shared, /containers etc, it breaks the styling of Discourse and I’m not sure why.
When I run a rebuild, I always see this when the launcher bash script runs
7bde3d3..d1cdc3f master -> origin/master
* [new tag] v1.0.2 -> v1.0.2
So it’s like the discourse .yaml files are already preconfigured to pull from that personal Git.
We have forked the main discourse codebase. We are managing our main Discourse application files through the main discourse codebase. If we want to add functionality, we’ll use plugins.
Not sure what that is. We just want to use CI/CD to deploy our Discourse docker .yaml files.
Hope this helps.