Instalamos Discourse con éxito en Digital Ocean, todo funciona bien, pero no logramos encontrar en absoluto dónde están los archivos reales de Discourse. Queríamos probar algunas modificaciones y desarrollar algunos complementos, pero no encontramos ningún archivo. Utilizamos Filezilla para iniciar sesión en el sitio. Sin embargo, no podemos encontrar ninguno de los archivos de la aplicación Discourse en ningún lugar, por ejemplo, discourse/app. Entramos en la carpeta var/discourse y no había nada. Luego en var/discourse/containers y tampoco había nada. Ejecutamos SSH .launcher enter app y podemos ver que nuestros archivos en la terminal están ubicados en var/www, pero este directorio no existe cuando nos conectamos al servidor. Probamos var/lib/docker/containers y tampoco había nada. ¿Dónde se encuentran exactamente los archivos de Discourse? Gracias.
That is how Docker works, the actual files are inside a Docker container, and therefore “invisible” using Filezilla.
If you want to test modifications to Discourse, like plugins and themes, you won’t be able to do it in a production install.
For themes check Beginner's guide to using Discourse themes
For plugins Beginner's Guide to Creating Discourse Plugins - Part 1
Is there another way to install this other than using docker then? I have read all the guides, but it’s kind of difficult to develop with invisible files.
The paradigm is very different from the 90’s PHP applications, where it was normal to edit files in production servers using FTP.
Changes to Discourse behavior are supposed to be separate projects, living in a git repository of their own, and to make use of the existing plugin and theme APIs.
So let’s say you want to add an extra field to the topic composer where a user will add their preferred color. You will create a new Discourse plugin following Beginner's Guide to Creating Discourse Plugins - Part 1, then put that on GitHub in a repository named discourse-favorite-color and install that to your instance using Install Plugins in Discourse
OK, got it. Will have to get used to this new way to develop. Just curious, every time we add a plugin we need to ./launcher rebuild app? And then do that again when modify the plugin?
Yes.
However, that is something that should happen infrequently, as that is your production install.
For development and test purposes, the very first part of Beginner's Guide to Creating Discourse Plugins - Part 1 tells you to setup a “Development Environment” where you can do changes and test just refreshing your browser.
That’s what I do, though you can also do an upgrade via the web interface at /admin/upgrade.
Also, a 2-container install lets you upgrade like
./launcher bootstrap web_only
./launcher destroy web_only; ./launcher start web_only
so your site is down just as long as it takes the new server to boot up (about a minute).