Nous avons installé Discourse avec succès sur Digital Ocean, tout fonctionne bien, mais nous ne trouvons absolument pas où se trouvent les fichiers Discourse eux-mêmes. Nous voulions tester certaines modifications et créer quelques plugins, mais nous ne trouvons aucun fichier. Nous avons utilisé FileZilla pour nous connecter au site. Cependant, nous ne trouvons aucun des fichiers de l’application Discourse, par exemple discourse/app. Nous sommes allés dans le dossier var/discourse et rien. Puis dans var/discourse/containers et toujours rien. Nous avons fait SSH .launcher entrer app, et nous pouvons voir que nos fichiers dans le terminal sont situés dans var/www, mais ce répertoire n’existe pas lorsque nous nous connectons au serveur. Nous avons essayé var/lib/docker/containers et rien. Où exactement se trouvent les fichiers Discourse ? Merci.
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).