Create Your Own Posterous with Jekyll, PHP, Mailgun, and S3(blog.jazzychad.net)
blog.jazzychad.net
Create Your Own Posterous with Jekyll, PHP, Mailgun, and S3
http://blog.jazzychad.net/2012/03/12/create-your-own-posterous.html
11 comments
Very cool Chad. Appreciate the post. I'll also add that you could create the Route using the Mailgun Routes API: http://documentation.mailgun.net/api-routes.html
To validate that the mailgun response actually came from mailgun add this at line 17:
if($_POST['signature'] !== hash_hmac('sha256', $_POST['timestamp'] . $_POST['token'], MAILGUN_KEY)) { exit; }
if($_POST['signature'] !== hash_hmac('sha256', $_POST['timestamp'] . $_POST['token'], MAILGUN_KEY)) { exit; }
Also possible with Postmarkapp's Inbound hook, and they support image attachments. They even provide PHP, Ruby, Python libraries for saving attachments.
Could you not have used Cloudmine instead of a virtual machine slice to handle the email webhooks/content conversion?
I don't think so (though I'm not sure). Cloudmine looks like it is aimed at mobile app backends, and the amount of code used for this project would be too custom for what is afforded on those types of services.
chmod u+w /etc/sudoers
# edit file to add new user
This is _not_ how you do this! I stopped reading once I read that line. I can't take anyone serious who does this.
This is _not_ how you do this! I stopped reading once I read that line. I can't take anyone serious who does this.
Well, thanks for educating us as to how it should be done.
Sorry, I was in a bad mood. I should have written:
This is now how you edit that file. You should edit this file using `visudo`, which "locks the sudoers file against multiple simultaneous edits, provides basic sanity checks, and checks for parse errors" (quotes text from man page).
This is now how you edit that file. You should edit this file using `visudo`, which "locks the sudoers file against multiple simultaneous edits, provides basic sanity checks, and checks for parse errors" (quotes text from man page).
My apologies, please let me know how it should be done? You're right, though, all of my other technical knowledge has become null and void because I goofed this part up.
show us the way, o wise one.
Not the original commenter, but I'm guessing they meant two things:
1) You should technically only be editing /etc/sudoers through visudo.
2) You should also have an admin/root group. All you would need to do then is "sudo adduser <blah> admin/root". This group is the one you specified in /etc/sudoers to have root permissions.
1) You should technically only be editing /etc/sudoers through visudo.
2) You should also have an admin/root group. All you would need to do then is "sudo adduser <blah> admin/root". This group is the one you specified in /etc/sudoers to have root permissions.