Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Channel/connection persistence between restarts and other fun fixes #131
Hoping to get more actively involved in the development of Subway. I'm currently in the process of building out enough functionality to be able to drop my ZNC bouncer for Subway.
These commits include the scrollable channel list, wrap fix for channel names, mongodb models broken out into a separate file, channel/connection persistence between subway restarts, storing logs based on server/user, fix for nick changing, and an issue with case sensitivity/channel names.
pushed a commit
this pull request
Jul 2, 2012
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
Hmm, are you proposing moving the fields that are in there to the users model? The original thought behind that was so we could support multiple IRC server connections per user login. I suppose this is really a fundamental question regarding Subway's goal as a project. Focus on bouncer functionality for auth'd users or an excellent replacement for web IRC clients? For me I was most interested in implementing the bouncer side of the project so that I could replace ZNC/Irssi. Thoughts?
@ericbarch I am fine with subway being used either way(as a webclient or a bouncer, or in some cases both). I am working on migrating from mongodb to sqlite. I hadn't dug into the backend code for a bit so I was wondering what the purpose of the connection model was.