Skip to content

Conversation

@jaylett
Copy link

@jaylett jaylett commented Sep 12, 2010

Hey — I think this helps. (It should actually work now, which previously it wouldn't unless you were running all of the standard /dev/fort setup.)

…t you don't *have* to intercept twitter for your entire local network.


Remove the twitter bind configuration that assumes you'll have a second machine serving DNS. If you do have, then you want some slave configuration at the other end, and it doesn't seem worth documenting; if you need resilience in your DNS serving, you probably know what you're doing (or should learn ;-).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant