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

Restrict client to one running instance #31

Closed
lyarenei opened this issue Sep 1, 2017 · 4 comments
Closed

Restrict client to one running instance #31

lyarenei opened this issue Sep 1, 2017 · 4 comments

Comments

@lyarenei
Copy link
Collaborator

lyarenei commented Sep 1, 2017

Idea from #6
Should be quite easy on Unix, I am not sure about Windows.

@starek4
Copy link
Owner

starek4 commented Sep 1, 2017

We should label that with low priority if you are ok with it. We need to discuss how will the user use our app (if it will be as GUI, as service, etc.) and so on. Now, we certainly have to focus on getting the code to better condition and write unit tests. Then we can do these things, but it is very good that we have them in this backlog.

@lyarenei
Copy link
Collaborator Author

lyarenei commented Sep 1, 2017

No problem, we can definitely introduce priorities. Can you please make low/medium/high labels and assign them to other issues? Thank you.

@starek4
Copy link
Owner

starek4 commented Sep 1, 2017

Yes, I did that.

@starek4
Copy link
Owner

starek4 commented Nov 22, 2017

05ec95f

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