Hi, I wanted to set up Multisite , but this bug seems to have other plans: Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake otherside:migrate failed with return #<Process::Status: pid 776 exit 1>

not sure but maybe this will help [imagem] Rake multisite:migrate is broken Bug Earlier today, I created a support topic in this context, but I wasn’t sure so I did some more tries and investigation into this, Seems like something is very wrong here. mult…

Do you have any plugins installed? Some are incompatible with multisite.

[imagem] Justman10000: otherside:migrate Wait what? It’s multisite not otherside ?

I have renamed it to hide the name I am actually using there. This has been taken care of! Apparently I also had to change the name of the $home/config/otherside.yml

Please elaborate on what you have been doing, I am missing your point completely. You’ve been hiding a name? Renaming config files? And you didn’t think it was worth mentioning when you filed the support question?

I have the following configuration: hooks: after_postgres: - exec: sudo -u postgres createdb discourse_rubyhub || exit 0 - exec: stdin: | grant all privileges on database discourse_rubyhub to discourse; cmd: sudo -u postgres psql discourse_rubyhub …

[imagem] Justman10000: what is the http port, or how do I change it in the multisite Your can change it only for all sites, not just one.

How is that supposed to work? How is the web server supposed to know that another site is now being added? Reverse proxies cannot use the same port multiple times

You send all requests to the same place. I discourse can teeth from the headers which site it is

Pups::ExecError

Suporte Instalação

Justman10000 Maio 11, 2023, 9:32am 13

Como isso deveria funcionar? Como o servidor web deveria saber que outro site está sendo adicionado agora? Proxies reversos não podem usar a mesma porta várias vezes

Tópico		Respostas	Visualizações
Rake multisite:migrate is broken Bug	4	1536	23 de Junho de 2020
Discourse bundle exec rake multisite:migrate failed Bug	4	1592	12 de Março de 2021
Background worker "logical replication launcher" (PID 51) exited with exit code 1 Self-hosting	16	6838	17 de Setembro de 2022
Upgrade to 2.8.0beta11 fails on multisite due to code review plugin Support	0	424	13 de Janeiro de 2022
Multisite build error: #<MiniRacer::RuntimeError: Error: Parser rule not found: fragments_join> Bug	9	1131	17 de Setembro de 2022

Pups::ExecError

Tópicos relacionados