-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still Alive? -> Yes: zappajs :) #125
Comments
Well, according to what I've seen in the discussion on Google groups, I think it's totally ok to take over the Zappajs project while Maurice is on his worldwide trip. Do you plan to merge pending pull requests ? Most of them sound legitimate and should be easily merged. I'm also interested in making Zappajs work with Express 3 as soon as possible. |
+1 for keeping this project alive. |
@Hypee I've started pulling some of the pending requests manually; I'm planning to go through all of them. From what I've noticed so far, in some cases we'll have to come up with some updated solutions (because things have changed a little bit since they were submitted); I'll add comments in the ones where I notice problems. wrt Express 3 if you're interested in starting a branch off the zappajs code to look at the integration issues that'd be great; I haven't had a chance to look into it much yet (except to notice the View handling had changed a lot so the |
Ok, I will take a look at the monkeypatching code, we need it to have inline views in Zappa (and that's one of my favorite feature). If you have time, may you write a short note to tell what pull request you did integrate ? (Wiki page ?) |
Edit: now running at https://github.com/zappajs/zappajs
Trying to get a sense for where we're at, following the recent discussion on the list and the similar issue with coffekup that lead to coffeecup.
I just noticed off-the-shelf
npm install zappa
got broken with the release of express 3.0.0alpha1 so I'd be looking at putting something together rather rapidly.Has anyone already started on this track?
The text was updated successfully, but these errors were encountered: