-
Notifications
You must be signed in to change notification settings - Fork 17
ddp-apollo and Meteor 3.0? #414
Comments
Any progress? |
I've gotten ApolloGraphQL working with Meteor 3.0, without Swydo, but it was like 50+ hours of work. I don't know how to write a Meteor package, but I'd be happy to contribute this code to it. |
So you are not using DDP at all for GraphQL anymore? over HTTPS? was it hard to implement accounts and authentication |
It still uses websockets. It was hard to get the Meteor user object into GraphQL context, but I was able to do it partly via code that was part of swydo ddp-apollo. |
@Cliffzz, if this package is no longer maintained and updated, maybe it's time to publicly archive it? So people know what to expect. I'm the original author, but no longer work at Swydo nor with Meteor. I do think there is potential in updating this package to make it work with Meteor 3, but I do not plan to do so myself. Maybe someone from the community can fork it and launch it under a new name. Anyway, cool to see that people are still using this! ❤️ |
@jamiter, this package was a life-saver for me when I was first adding Apollo to my Meteor app. Thanks for all your great work on it! |
@jamiter I've got a question for you. This works fine in development:
But in production, I believe it has to be an https server, rather than an http server. I've been trying to provision a LetsEncrypt certificate for the httpsServer, using GreenLock, and I'm getting nowhere. How did you handle this in swydo/ddp-apollo? Can you copy-paste some source code? Unless... Can I just run ApolloGraphQL on the same port as Meteor, and listen for calls to the /graphql endpoint this way?
UPDATE Yes, that's working. :) |
Fair enough, will do. We indeed no longer use this nor plan to maintain it. And even if it could work with Meteor 3.0 I wouldn't recommend to go this route. |
Are there plans yet to release an update of ddp-apollo to work with Meteor 3.0?
The text was updated successfully, but these errors were encountered: