Michael

I like it. I noticed that the model is already setup to handle flagging a url as spam, so this should be pretty easy. Psyched to be learning more about rails!

I admit monit is not doing what we want. But you can't separate using monit to watch a process and the restarting of that process. In other words if we want monit to watch the mongrels at all we have to tell it when to start and stop the mongrels as well. We can't go behind its back because it will just detect that the process has died and attempt to start it up again.

I would prefer to use another tool, but so far monit is the best one out there that I have learned how to use. I think god could be a better tool, but I have not had enough time to grock it yet.

You are right... basically you tell monit to do something and it returns and then goes and does it. Mongrel can take a few seconds to stop and start so sometimes monit gets out of sync with mongrel.

You should be able to login with duff@next.theconnectedrepublic.org. I added your public ssh key to ~/.ssh/authorized_keys so you should not get a password prompt. Your password is in ~/password.txt.

Duff, now that you have a way to install gems via the rake task do you still have a need for sudo access? I prefer not to grant sudo access if possible because then I have more control over what happens on the box. If you still feel that it would be useful let me know and I'll set you up.

The other way you could have installed the gem is by adding it as a dependency in environment.rb and running `cap deploy` which calls install_rake_tasks. The republic user has sudo permissions to run any rake task.

I know that wordpress has them. It is basically a way to be notified when someone links to you. See http://codex.wordpress.org/Introduction_to_Blogging#Trackbacks and http://codex.wordpress.org/Introduction_to_Blogging#Pingbacks.

Username and password will be emailed to team.

I'm not a rails expert, but it seems strange that the bookmarklet and the form have different parameters.

Just pushed a fix for this.

I figured you would say something like that :)

Actually we can check before deploying. Just run `rake asset:packager:build_all && script/server -e production`

So this was due to me installing the asset_package plugin.

I had changed the default configuration so that it was looking for compressed javascript and css in development mode as well as production. The reason that you were seeing the error after updating was because for asset_packager to work properly you have to run `rake asset_pacakger:build_all` which generates the compressed assets. I turned off asset_packager in development so you dont have to run rake and will not see this problem anymore: http://github.com/kohlhofer/rubyurl/commit/5fe689eec74fe86415fca6c93cf700e460e2310a

The only downside to turning this off in development is that it does change the css and javascript so sometimes it can cause problems that would only show up in production. We could turn it back on for development mode too, and add some code to script/server to automatically run the rake task. The only downside is that the server would have to be restarted every time you changed a javascript or css file.

I'm only seeing this on a freshly cloned repository. I'll see what's up.

I think that probably is the problem commit. I've rolled back the code on the server, and will create a fix.

installed monit instead