4 ms·
Oh, I've made one too! http://github.com/erming/shout http://github.com/erming/shout It's really stable (been using it for weeks without restarting) and I've e
by erming 12y ago
Oh, I've made one too!
http://github.com/erming/shout http://github.com/erming/shout
It's really stable (been using it for weeks without restarting) and I've even implemented a mobile interface: https://db.tt/fYTswBwO https://db.tt/fYTswBwO
You'll find the install instructions in the README (or just `npm install shout`). No configuration required. Should take under a minute to get it running if you already have NPM.
It's open source. Feel free to try it, browse the code and leave some feedback. If you want to work with me, it's open for contributions!
- silversmith 12y agoLooks really nice - especially the part where multiple networks are in the very first screenshot! How are you handling persistence tho? Straight up in-memory storage?
- erming 12y agoYes, right now it's only in memory. I've been thinking about storing the logs in .txt-files (with the option to turn this feature on/off). This way, I could let the user download the logs directly via the browser.
- hexscrews 12y agoI'm not familiar with how difficult it may be, so please tell me if I'm off base. But couldn't you offer the option for either text logs or HTML logs? I know that when given the option, I opt for HTML logs for the ease of reading.
- erming 12y agoHi! Didn't see your question until now. While I haven't implemented the logging yet, I'm thinking about storing them in the JSON-format. Messages are already stored as JavaScript object, so I think this is my best option. And exporting them as .txt on demand, shouldn't be a problem either. Thank you for the feedback
- cjbprime 12y agoLooks great! Would love text logs and support for multiple users each with their own config.