Multiple development instances

Development

AI-generated summary

The discussion revolves around the need for multiple development instances of Discourse. pfaffman currently switches between branches and database environments to handle different development tasks, finding it inefficient. simon faces a similar issue, wanting to test a network of Discourse sites with DiscourseConnect providers and clients on his local computer. pfaffman suggests that running multiple production sites on a local machine is possible but may require advanced DNS configuration. simon decides to test on production sites instead, due to the complexity of DNS setup.

1

On my development box, I find myself needing multiple instances. One site I’m importing is on stable, others use importers that I am developing. Right now what I do is when switching jobs, I switch branches in git and run a script that does

RAILS_ENV=development
export RAILS_ENV
RAILS_ENV=development bundle exec rake db:drop db:create db:migrate
bundle exec rake admin:create

It’s really annoying when I’ve, say, run an importer that takes several hours and then want to run it again with updated input (and not have to re-import the whole thing).

Is there something different I should be doing? Perhaps I should run separate instances with Vagrant? Contrive to tell Discourse to use a different database for each different job?

Or am I doing the Right Thing?

2

Desculpe por responder a um tópico tão antigo. Você conseguiu fazer isso funcionar? Meu caso de uso é querer fazer alguns testes configurando uma rede de sites Discourse, onde alguns dos sites funcionam como provedores do DiscourseConnect e outros sites funcionam como clientes do DiscourseConnect. Posso configurar vários sites de produção para isso, mas seria ótimo poder ter os sites no meu computador local.

3

Será muito difícil fazer o DiscourseConnect funcionar (pelo menos como fonte, que precisa de uma URL) em desenvolvimento. Se você for bom nesses jogos de DNS (como rotear esses através do seu firewall?), então nada o impede de executar vários sites de produção em sua máquina local.

4

Eu não sou :slight_smile: Vou continuar testando em sites de produção.