summaryrefslogtreecommitdiff
path: root/docs/mail/hacking.rst
diff options
context:
space:
mode:
authorKali Kaneko (leap communications) <kali@leap.se>2017-04-27 20:00:50 +0200
committerKali Kaneko (leap communications) <kali@leap.se>2017-05-01 16:13:14 +0200
commit8a0c8b2a0cfa2ad84113d1e041fa4ce4c8704ffc (patch)
tree3a7f26e0486ee5dbc6586b89313b5ffb879d694a /docs/mail/hacking.rst
parent5009f2c227ab55d70022f24f7f32299e26fd11ea (diff)
[docs] update the manhole documentation
Diffstat (limited to 'docs/mail/hacking.rst')
-rw-r--r--docs/mail/hacking.rst22
1 files changed, 0 insertions, 22 deletions
diff --git a/docs/mail/hacking.rst b/docs/mail/hacking.rst
index 27087e52..10e3dbcb 100644
--- a/docs/mail/hacking.rst
+++ b/docs/mail/hacking.rst
@@ -6,28 +6,6 @@ Hacking on Bitmask Mail
Some hints oriented to `leap.mail` hackers. These notes are mostly related to
the imap server, although they probably will be useful for other pieces too.
-Don't panic! Just manhole into it
----------------------------------
-
-
-If you want to inspect the objects living in your application memory, in
-realtime, you can manhole into it.
-
-First of all, check that the modules ``PyCrypto`` and ``pyasn1`` are installed
-into your system, they are needed for it to work.
-
-You just have to pass the ``LEAP_MAIL_MANHOLE=1`` enviroment variable while
-launching the client::
-
- LEAP_MAIL_MANHOLE=1 bitmask --debug
-
-And then you can ssh into your application! (password is "leap")::
-
- ssh boss@localhost -p 2222
-
-Did I mention how *awesome* twisted is?? ``:)``
-
-
Profiling
----------