Hey Errol, I finally had a chance to check out some of your additions. You've made some great progress. I haven't written much code lately (weddings, business, moving, etc.) but I can't wait to get my dev PC back up and running to test out your RSVP code.
> From the feedback so far, comments and reminders seem like the next > things to do. I agree. It's funny, as it seems these are the remaining 2 things from my list that you haven't already implemented (P.S. thanks!) > I should be able to figure out comments. I think the only thing I > need to change is the way events are accessed. I think they need to > have an owner in the url like this: /myuser/events/32. At least, > that's how it appears to me from looking at the code. Am I right, or > have I missed something? I'm not sure why it would be necessary to have the owner in the url. But, its possible the comments code assumes there is one as posts, photos, clippings, etc. all have an owner. It's probably best to structure things this way anyway. > As for reminders, I need some kind of daemon that sends the emails at > the appropriate time. This looks promising: > http://github.com/tobi/delayed_job/tree/master I agree. I think I remember seeing something about this on Hacker News recently. A quick search and I see that Heroku is advocating it and I know some people here are deploying with Heroku (but $15/month? http://blog.heroku.com/archives/2009/7/15/background_jobs_with_dj_on_heroku/ ). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
