Is it ever possible to use Sailhouse in development/not production?

[whitep4nth3r]

When creating apps, topics and subscriptions, developers will want to create and connect to Sailhouse "dev" apps, with separate topics and subscriptions for development purposes — as not to pollute production data.

How could we connect Sailhouse to localhost, for example?

Additionally, larger teams may want even more control over sending events to more environments, including staging and testing environments.

[estephinson]

So yeah, the intention is that people can easily create a new app which will serve as their environments as they need

• acme-prod
• acme-dev
• acme-staging

Etc.

What could be cool, is the ability for this to be on demand from a schema or even clone from another app.

sailhouse dev --schema schema.yaml

This could create an on-demand app (under the hood just a randomly generated app name). Push subscriptions would be interesting, as they're full URLs, but maybe could add a --push-base-url type argument which would allow you to forward them all to a localhost endpoint

[estephinson]

This has also given me an idea similar to the Stripe CLI, where you can locally consume real-events and handle them locally.

sailhouse subscribe user-created --endpoint http://localhost:8888/api/test-endpoint

Mechanics of this would be fun to work out to ensure it's a short-lived thing but a nice idea regardless

[whitep4nth3r]

Let's add a docs page for this? Titled something about working in different environments?

[estephinson]

Yeah sounds good, like the idea of having a full on guides-like section for best practices