Sputnik¶
Summary¶
Sputnik is a Python IRC bouncer written using asyncio and backed by Redis. It is intended as a lightweight, zero-configuration bouncer capable of deployment on cloud providers such as Heroku. Sputnik is written in pure Python, so adding custom functionality is relatively straightforward.
Features
- Automatic Network Reconnection
- Channel Saver
- Buffered Message History
- Multi-Client Connections
Getting Started¶
You can easily deploy a Sputnik instance on Heroku using the button below.
Alternately, you can manually create and deploy your own Heroku app, or run Sputnik on your own computer or server. To do so requires a Python 3.4 interpreter and Redis (optional), if you want persistence between restarts or crashes.
Documentation¶
Sputnik documentation is built using Sphinx and publicly hosted at http://sputnik.readthedocs.org/. You can also build and serve the documentation locally.
git submodule update --init --recursive
cd docs && make dirhtml && cd _build/dirhtml
python -m SimpleHTTPServer
Then visit http://localhost:8000 in a browser.
License¶
The MIT License (MIT)
Copyright (c) 2014 Kevin Fung et al.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Modules¶
bouncer module¶
client module¶
Sputnik Client Implementation
This module provides the Sputnik Client implementation. This is a subclass of a Connection, and defines an interface to IRC client applications implementing _RFC 2812: https://tools.ietf.org/html/rfc2812 .
-
class
client.Client(bouncer)[source]¶ Bases:
connection.ConnectionAn instance of a connection from an IRC client.
A Client is the product of an asyncio protocol factory, and represents an instance of a connection from an IRC client to the listen server. It does not implement an actual IRC client, as defined in _RFC 2812: https://tools.ietf.org/html/rfc2812 .
-
bouncer¶ sputnik.Bouncer
A reference to the Bouncer singleton.
-
broker¶ sputnik.Network
The connected Network instance.
-
network¶ str
The name of the IRC network to connect to.
-
ready¶ bool
Indicates if the Client has connected to a Network.
-
connection_lost(exc)[source]¶ Unregister the connected Client from the Bouncer.
Removes the Client from the set of connected Clients in the Bouncer before the connection is terminated. After this point, there should be no remaining references to this instance of the Client.
-
connection_made(transport)[source]¶ Registers the connected Client with the Bouncer.
Adds the Client to the set of connected Clients in the Bouncer and saves the transport for later use.
-
data_received(data)[source]¶ Handles incoming messages from connected IRC clients.
Messages coming from IRC clients are potentially batched, and need to be parsed into individual lines before any other operation may occur. Afterwards, we split lines according to the IRC message format and then perform actions as appropriate.
-
connection module¶
Sputnik Connection Implementation
This module provides the Sputnik Connection implementation. This is a base class that defines several helper functions for common tasks related to transport-level interactions, such as message encoding and message passing.
-
class
connection.Connection[source]¶ Bases:
asyncio.protocols.ProtocolA generic instance of a network connection.
A Connection is a base class that represents an instance of a network connection. The Connection implements commonly used actions that may be performed on messages.
-
decode(line)[source]¶ Attempts to decode a line as UTF-8, with fallback to Latin-1.
We try to maintain a full-Unicode presence where possible. However, not all IRC servers are encoding using UTF-8, so we shadow str.decode() and provide a fallback to Latin-1 when needed.
Parameters: line (str) – A byte-string message to decode. Returns: A decoded message. Return type: str
-
normalize(line, ending='\r\n')[source]¶ Ensures that a line is terminated with the correct line endings.
The IRC protocol specifies that line endings should use CRLF line endings. This ensures that lines conform to this standard. In the event of a server that does not conform to the specification, we preserve the ability to provide an alternative line ending character sequence.
- Args:
- line (str): A message to be sent to the IRC network. ending (str, optional): The line ending. Defaults to ``“
“``.
-
send(*args)[source]¶ Writes a message to the connected interface.
Messages are typically of the form
<command> <message>. This encapsulates the IRC messaging protocol by concatenating messages and checking their line endings before encoding the message into raw bytes, as part of the asyncio transport mechanism.Parameters: args (list of str) – A list of strings to concatenate.
-
datastore module¶
handlers module¶
Sputnik Request Handlers
This module provides Tornado Request Handlers for the Sputnik Web Interface.
-
class
handlers.AddHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe RequestHandler that serves the add network page.
The add network page uses a form to receive new network settings. If a network already exists using the provided name, the network is not added.
-
class
handlers.BaseHandler(application, request, **kwargs)[source]¶ Bases:
tornado.web.RequestHandlerA base handler that stores the Bouncer singleton.
-
class
handlers.DeleteHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe RequestHandler that handles delete network requests.
-
class
handlers.EditHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe RequestHandler that serves the edit network page.
The edit network page uses a form to receive updated settings from users. When a network is editted, it is disconnected and then recreated using the new settings.
-
class
handlers.LoginHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe RequestHandler that serves the login page.
The login page prompts the user for their password and authenticates them when the password matches the one stored by the bouncer in its database.
-
class
handlers.LogoutHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe RequestHandler that handles log out requests.
Redirects to the homepage after clearing authentication.
-
class
handlers.MainHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe main RequestHandler that serves the home page.
The home page displays the current list of networks.
-
class
handlers.SettingsHandler(application, request, **kwargs)[source]¶ Bases:
handlers.BaseHandlerThe RequestHandler that serves the settings page.
Allows users to change their password.
network module¶
Sputnik Network Implementation
This module provides the Sputnik Network implementation. This is a subclass of a Connection, and defines an interface to IRC server networks implementing _RFC 2813: https://tools.ietf.org/html/rfc2813 .
-
class
network.Network(bouncer, network, hostname, port, nickname, username, realname, password=None, usermode=0)[source]¶ Bases:
connection.ConnectionAn instance of a connection to an IRC network.
A Network is the product of an asyncio protocol factory, and represents an instance of a connection from an IRC client to an IRC server. This could be either a single IRC server, or more likely, a network of servers behind a load balancer. It does not implement an actual IRC server, as defined in
-
??? (revisit this later)
-
attempt_reconnect(attempt=0, retries=5)[source]¶ Attempts to reconnect to a network that unexpectedly disconnected.
This is only called if we drop the connection to a network and the connected flag is set, to distinguish from intentional disconnects.
Parameters:
-
connection_lost(exc)[source]¶ Unregisters the connected Network from the Bouncer.
Removes the Network from the dictionary of connected Clients in the Bouncer before the connection is terminated. After this point, there should be no remaining references to this instance of the Network.
-
connection_made(transport)[source]¶ Registers the connected Network with the Bouncer.
Adds the Network to the set of connected Networks in the Bouncer and saves the transport for later use. This also creates a collection of buffers and logging facilities, and initiates the authentication handshake, if applicable.
-
data_received(data)[source]¶ Handles incoming messages from connected IRC networks.
Messages coming from IRC networks are potentially batched and need to be parsed into individual lines before any other operation may occur. On certain occasions, incoming data may overflow the transport buffer, requiring additional logic to reconstitute the messages into a single stream. Afterwards, we split lines according to the IRC message format and perform actions as appropriate.
-
server module¶
Sputnik HTTPServer Implementation
This module provides the Sputnik HTTPServer implementation. It is responsible for serving the web interface, and interfaces with the Bouncer singleton to connect to and disconnect from networks.
-
class
server.HTTPServer(bouncer)[source]¶ Bases:
tornado.web.ApplicationAn Asynchronous HTTP Server that diplays the frontend.
The HTTPServer renders the frontend and accepts commands used to control the Bouncer singleton. For development purposes, it may be helpful to set the DEBUG environment variable. e.g. export DEBUG=True