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

Show conference logs in a more convenient way #27

Open
rexim opened this issue Mar 14, 2015 · 4 comments
Open

Show conference logs in a more convenient way #27

rexim opened this issue Mar 14, 2015 · 4 comments
Assignees

Comments

@rexim
Copy link
Member

rexim commented Mar 14, 2015

Please get rid of that frame! It's ugly and inconvenient!

@ForNeVeR
Copy link
Member

Well, there's a plan to reuse horta-web API here. We should discuss how do we plan to reuse it - whether we want to replicate all logs from the horta database or lazily replicate it on demand or simply send browsers to horta-web itself.

@ForNeVeR ForNeVeR self-assigned this Oct 17, 2016
@ForNeVeR
Copy link
Member

Okay, currently the plan is to update Yog-Sothoth archivarius bot to be netcore-compatible. To do that, we'll need netcore-compatible XMPP library, and I'm actively working on port of Jabber-Net library.

The task will have a positive impact on both netcore ecosystem and cross-platform XMPP stack availability, so that's a very good thing.

At the same time, netcore stack is still evolving, so I hope we'll be able to benefit from upcoming netstandard 2.0 stuff that should make the porting process easier.

@ForNeVeR
Copy link
Member

ForNeVeR commented Dec 8, 2016

Alright, the current idea is to:

  • pack the beta shit from SharpXMPP and upload to NuGet (Publish to NuGet vitalyster/SharpXMPP#7)
  • implement a simple logger robot (not Yog-Sothoth but a simpler one) and run it as part of ctor web service
  • push the logs into a PostgreSQL database (no more NoSQL, sorry)
  • implement a simple scriptless page that will show the current logs from the database

ForNeVeR added a commit that referenced this issue Dec 8, 2016
ForNeVeR added a commit that referenced this issue Dec 10, 2016
ForNeVeR added a commit that referenced this issue Dec 11, 2016
ForNeVeR added a commit that referenced this issue Dec 11, 2016
ForNeVeR added a commit that referenced this issue Dec 11, 2016
ForNeVeR added a commit that referenced this issue Dec 12, 2016
@ForNeVeR

This comment was marked as off-topic.

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