Skip to content
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

Config Files #6

Open
ryanbressler opened this issue Nov 19, 2013 · 3 comments
Open

Config Files #6

ryanbressler opened this issue Nov 19, 2013 · 3 comments

Comments

@ryanbressler
Copy link

The server should be driven by a config file...but what format?

@hrovira
Copy link

hrovira commented Nov 19, 2013

Depends on what configuration options you specify: port, host, secret, what
else?

On Mon, Nov 18, 2013 at 4:34 PM, Ryan Bressler notifications@github.comwrote:

The server should be driven by a config file...but what format?


Reply to this email directly or view it on GitHubhttps://github.com//issues/6
.

@ryanbressler
Copy link
Author

eventually we'll need something like:

tls vs not,
cookie timeout (hardcoded to the tornado web default of 31 days atm)
where to store persistent data if we want non ephemeral messaging?
maybe allowed users and services?

I can start out with a json file and sub out if it gets complex.

@hrovira
Copy link

hrovira commented Nov 20, 2013

cookie timeout > handled by tornado
persistent data > would be the responsibility of service calling API, but
you should consider maintaining a log (perhaps a database) for synch
allowed users and services > handled by tornado

On Wed, Nov 20, 2013 at 10:31 AM, Ryan Bressler notifications@github.comwrote:

eventually we'll need something like:

tls vs not,
cookie timeout (hardcoded to the tornado web default of 31 days atm)
where to store persistent data if we want non ephemeral messaging?
maybe allowed users and services?

I can start out with a json file and sub out if it gets complex.


Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-28915296
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants