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=developme…

Sorry for replying to such an old topic. Did you ever manage to get this to work? My use case is wanting to do some tests with setting up a network of Discourse sites, where some of the sites are functioning as DiscourseConnect providers and other sites are functioning as DiscourseConnect clients. …

It’ll be really hard to get DiscourseConnect to work (at least as the source, which needs a URL) to work in development. If you’re good at those DNS games (like routing those in through your firewall?), then nothing is stopping you from running multiple production sites on your local machine.

[Bild] Jay Pfaffman: If you’re good at those DNS games I’m not :slight_smile: I’ll stick with testing on production sites.

Multiple development instances

Development

simon 13. Dezember 2022 um 20:00 4

Ich bin es nicht Ich bleibe beim Testen auf Produktionsseiten.

Thema		Antworten	Aufrufe
Set up a multisite development environment Developer Guides dev-install , how-to	0	2158	7. Juni 2022
Best approach for test and production instance of discourse Self-hosting	6	2084	9. August 2019
Is creating a second app.yml-like file enough for multisite? Self-hosting hosting	3	1621	3. Juni 2020
How to setup both development and production environment Support	3	2256	10. Juli 2016
What is the latest recommended workflow for local development? (Ubuntu 16.04) Development	7	2483	6. Oktober 2017

Multiple development instances

Verwandte Themen