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

Customisable prefix #76

Closed
aymericbeaumet opened this issue Feb 20, 2014 · 5 comments
Closed

Customisable prefix #76

aymericbeaumet opened this issue Feb 20, 2014 · 5 comments
Assignees
Milestone

Comments

@aymericbeaumet
Copy link

I think it would be nice if the frontend: prefix could be configurable from the configuration file.

This way it would be more easier to avoid conflicts in the database.

@dmp42
Copy link
Member

dmp42 commented Mar 15, 2014

Hi,

Doesn't using a different database (which is possible right now using redisDatabase in your config file) cover your case? (eg: avoid conflict with other data)

Thanks!

@aymericbeaumet
Copy link
Author

Yes it could if I do not have any other choice, but I'd prefer to be able to change the prefix :)

@dmp42
Copy link
Member

dmp42 commented Mar 17, 2014

:-)
Is that a matter of personal preference, then?
Or are there strong arguments for not using redis databases to segregate data?

Thanks again for your input on this!

@aymericbeaumet
Copy link
Author

It is totally a personal preference. And as you said, I could just choose a different database.

@dmp42 dmp42 added this to the 0.3 milestone Mar 19, 2014
@dmp42 dmp42 self-assigned this Mar 19, 2014
@dmp42 dmp42 mentioned this issue Mar 20, 2014
@dmp42
Copy link
Member

dmp42 commented Apr 2, 2014

Fixed by #89

@dmp42 dmp42 closed this as completed Apr 2, 2014
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