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

Storing settings #11

Open
PeterJWhite opened this issue Jul 18, 2016 · 3 comments
Open

Storing settings #11

PeterJWhite opened this issue Jul 18, 2016 · 3 comments

Comments

@PeterJWhite
Copy link

I was discussing with @thibautjombart that it would be useful to be able to store the settings, to avoid having to set them manually each time.

I suggest the best way to do this is to allow settings to be stored in a file that can be downloaded, stored, shared, and uploaded when required. This would allow for settings to be shared by different users: typically in an outbreak there will be multiple people doing data processing in each location and often people in different locations following the same operating procedure.

@daattali
Copy link
Collaborator

Sounds like my job. I can implement that in the future, once the backend seems solid enough that the tool is starting to be very useful I'll work on working that in

@thibautjombart
Copy link

Awesome!
=D
On 18 July 2016 at 17:38, Dean Attali [email protected] wrote:

Sounds like my job. I can implement that in the future, once the backend
seems solid enough that the tool is starting to be very useful I'll work on
working that in


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKQkIl0brte5RZgVn6cQtP7WgjfrRTrjks5qW6vsgaJpZM4JO2If
.

@PeterJWhite
Copy link
Author

Thanks a lot, Dean
Best wishes
Peter

From: Dean Attali [mailto:[email protected]]
Sent: 18 July 2016 17:38
To: Hackout3/epimatch
Cc: White, Peter J; Author
Subject: Re: [Hackout3/epimatch] Storing settings (#11)

Sounds like my job. I can implement that in the future, once the backend seems solid enough that the tool is starting to be very useful I'll work on working that in


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/11#issuecomment-233384348, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATkc_sjjbI7V59sK-CgBExFAdfsn5enfks5qW6vtgaJpZM4JO2If.

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

No branches or pull requests

3 participants