@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.) hq.recaptime.dev/wiki/Phorge
phorge phabricator
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Remove Lamson documentation

Summary:
Fixes T11054. This project's website has been down for more than a year:

<https://github.com/zedshaw/lamson/issues/36>

It hasn't received any new commits for three years (March, 2013):

<https://github.com/zedshaw/lamson/commits/master>

Instructions like this are a good candidate for community ownership rather than upstream maintenance. I don't think we'd accept these instructions upstream today.

Test Plan: `grep -i lamson`

Reviewers: chad

Reviewed By: chad

Maniphest Tasks: T11054

Differential Revision: https://secure.phabricator.com/D15990

-36
-36
src/docs/user/configuration/configuring_inbound_email.diviner
··· 216 216 That will forward all mail to @yourdomain.com to the Phabricator processing 217 217 script. Run `sudo /etc/mail/make` or similar and then restart sendmail with 218 218 `sudo /etc/init.d/sendmail restart`. 219 - 220 - = Local MTA: Configuring Lamson = 221 - 222 - Before you can configure Lamson, you need to install Mailparse. See the section 223 - "Installing Mailparse" above. 224 - 225 - In contrast to Sendmail, Lamson is relatively easy to configure. It is fairly 226 - minimal, and is suitable for a development or testing environment. Lamson 227 - listens for incoming SMTP mails and passes the content directly to Phabricator. 228 - 229 - To get started, follow the provided instructions 230 - (<http://lamsonproject.org/docs/getting_started.html>) to set up an instance. 231 - One likely deployment issue is that binding to port 25 requires root 232 - privileges. Lamson is capable of starting as root then dropping privileges, but 233 - you must supply `-uid` and `-gid` arguments to do so, as demonstrated by 234 - Step 8 in Lamson's deployment tutorial (located here: 235 - <http://lamsonproject.org/docs/deploying_oneshotblog.html>). 236 - 237 - The Lamson handler code itself is very concise; it merely needs to pass the 238 - content of the email to Phabricator: 239 - 240 - import logging, subprocess 241 - from lamson.routing import route, stateless 242 - from lamson import view 243 - 244 - PHABRICATOR_ROOT = "/path/to/phabricator" 245 - PHABRICATOR_ENV = "custom/myconf" 246 - LOGGING_ENABLED = True 247 - 248 - @route("(address)@(host)", address=".+") 249 - @stateless 250 - def START(message, address=None, host=None): 251 - if LOGGING_ENABLED: 252 - logging.debug("%s", message.original) 253 - process = subprocess.Popen([PHABRICATOR_ROOT + "scripts/mail/mail_handler.php",PHABRICATOR_ENV],stdin=subprocess.PIPE) 254 - process.communicate(message.original)