Greetings, I can’t post in the Sysadmin category. I can configure an external DB using: DISCOURSE_DB_USERNAME DISCOURSE_DB_PASSWORD DISCOURSE_DB_HOST DISCOURSE_DB_NAME But I couldn’t find: DISCOURSE_DB_PORT (External PostgreSQL Port) DISCOURSE_REDIS_HOST DISCOURSE_REDIS_USERNAME DISCOURSE_REDIS…

You can see all of the possible global vars documented at: config/discourse_defaults.conf main # # DO NOT EDIT THIS FILE # If you need to make changes create a file called discourse.conf in this directory with your changes # On import this file will be imported using ERB # # D…

I’m doing this for a docker-compose application, and despite exporting the environment variable for DISCOURSE_REDIS_HOST (as redis) it is not honoring this variable: name, 'name', name),\n updated_at,\n created_at,\n updated_at\nFROM facebook_user_infos\n") discourse_1_9cc0cea436ca | rake aborte…

[immagine] vsoch: I’m doing this for a docker-compose application, I’m not quite sure why you’re having that problem, but you’ll experience considerably less pain if you do it this recommended way: Install Discourse for development using Docker See also, Can Discourse ship frequent Docker i…

Maybe I’m reading the code incorrectly, but the bin/docker/boot_dev --init script is still interacting with a database and dependencies on the host. For the second thread, what in particular are you pointing me to look at? It has 151 posts. Thanks!

[immagine] vsoch: I’m doing this for a docker-compose application, and despite exporting the environment variable for DISCOURSE_REDIS_HOST (as redis) it is not honoring this variable: That variable is honored in production just fine. For development we search for a local instance by default,…

I’m running it with production as the environment variable, and it wasn’t being honored. As a workaround I changed the config with sed, and that fixed it. There are still numerous other issues I’m working on.

For example, I’m starting by explicitly saying to not daemonize (to keep the container running): bundle exec rails s --port 3000 --no-daemon --environment=production --binding 0.0.0.0 but it seems to decide to do it anyway! And then logically the container exits. discourse_1_f60e0e3f1186 | [358] …

[immagine] vsoch: I’m running it with production as the environment variable Do you want a production environment or a development environment?

Why can’t I run a production environment and use it for development? And what does sidekiq do? Should that be run alone to start the application? E.g., I have another container (same base) with a start command: bundle exec sidekiq And it depends on the main discourse container (migrating the db, p…

I’m happy to spend lots of (more) time on this, granted that I haven’t started anything yet, but I need a solution that doesn’t require me installing a database on my host. With containers, we shouldn’t need to do that. And again, the compose application here GitHub - vsoch/discourse-compose: docker…

Variabili d'ambiente DB esterne non documentate (porta PG esterna, variabili d'ambiente Redis esterne)

Supporto Installazione

Falco (Falco) 8 Luglio 2019, 3:39pm 6

Questa variabile viene rispettata correttamente in produzione.

Per lo sviluppo, per impostazione predefinita, cerchiamo un’istanza locale, il che funziona perfettamente se segui uno degli ambienti di sviluppo supportati.

Argomento		Risposte	Visualizzazioni
Configure Discourse to use a separate PostgreSQL server Self-Hosting how-to	50	29293	Gennaio 8, 2026
Discourse with DO managed Redis Development	2	1274	Giugno 5, 2020
Using Discourse with external PostgreSQL and Redis Self-hosting docker , advanced-setup	1	1134	Ottobre 26, 2023
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	3466	Settembre 20, 2022
How to resolve Pups exec errors during Discourse bootstrap Support	21	443	Aprile 24, 2025

Variabili d'ambiente DB esterne non documentate (porta PG esterna, variabili d'ambiente Redis esterne)

Argomenti correlati