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

Logging errors #11

Open
Ffisegydd opened this issue Nov 18, 2014 · 4 comments
Open

Logging errors #11

Ffisegydd opened this issue Nov 18, 2014 · 4 comments
Assignees

Comments

@Ffisegydd
Copy link
Member

When errors occur there should be some log of them, this will be especially important as the work becomes more involved and interconnected, i.e., when RABBIT and Nidaba start up.

Any serious ones cound be sent to [email protected] (which directs to [email protected] (which directs to my personal email)).

Alternatively, we could make use of the GH API and have them raise an Issue.

@OldTinfoil
Copy link

What about an opt-in mailing list that we could subscribe to?

@Ffisegydd
Copy link
Member Author

Yeah ideally it would be sent to more than just me, as I can forward emails to relevant people but seems a bit silly. Unfortunately Google charges quite a hefty fee per account so giving everyone an account is not really possible. If we decided to run our own mail server then we could have [email protected] which would be then forwarded to anyone who wanted to subscribe.

@OldTinfoil
Copy link

Can't you set up mail forwarding from the domain name provider?

@Ffisegydd
Copy link
Member Author

I don't know, I'm just a poor boy physicist from a poor family.

For some reason Jon decided against hosting our own mail server, and instead we use Google Accounts, this may be because of convenience, but if the cost/convenience is being outweighed by our inability to do some things then it's possibly a good idea to look at doing things ourselves.

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

3 participants