-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Untangle tildes from tildes.net #17
Labels
Comments
There's a couple of different things which we might split out into issues:
|
Also, we should keep an eye on upstreamability -- we should work with the tildes team to separate their production operational config from the application source. Or provide some automated way to patch it out for other orgs. Our solution needs to be compatible with their operation in order to get it accepted. |
A few of the changes I have already committed are small steps in this direction. I'll try to find time to split them out onto a stand alone branch that the upstream can use.
…On Mon, 6 Jul 2020, at 1:26 AM, Rick Hull wrote:
Also, we should keep an eye on upstreamability -- we should work with
the tildes team to separate their production operational config from
the application source. Or provide some automated way to patch it out
for other orgs.
Our solution needs to be compatible with their operation in order to
get it accepted.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQCE25B6RQ6KBFGUYCHKYJTR2CLTRANCNFSM4OLZZNTQ>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, tildes production mode really wants to run on tildes.net. Obviously we will not be doing so. We need to set it up so that it can accept a custom domain and work properly on that domain.
The text was updated successfully, but these errors were encountered: