Moving Into Serverless Project?

[davidwilcox]

Hey,

I was wondering what the developers here would think about moving this into a serverless project (in particular, a project that is usable under the serverless framework here http://serverless.com/). It would probably simplify a lot of the config and deploying that we have here.

What would you guys think about that? I'm probably going to make a fork of it myself into a serverless project anyway for what I need to get done. Would that be something you would want to integrate into mainline?

Thanks.

[danilop]

I would definitely support this, for any framework! I actually talked about
a contribution/merge with the Serverless Framework team long ago (they were
still JAWS) and I do not see any blocker, if not my lack of time.

On Sat, Aug 6, 2016 at 10:49 PM, David Wilcox notifications@github.com
wrote:

Hey,

I was wondering what the developers here would think about moving this
into a serverless project (in particular, a project that is usable under
the serverless framework here http://serverless.com/). It would probably
simplify a lot of the config and deploying that we have here.

What would you guys think about that? I'm probably going to make a fork of
it myself into a serverless project anyway for what I need to get done.
Would that be something you would want to integrate into mainline?

Thanks.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#53, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeoO5b8UHEm-DIjncE4xl0dHNRW0VYTks5qdQFjgaJpZM4JeX3y
.

[hassankhan]

Just as an aside, Serverless uses CloudFormation templates to set up resources on AWS, and as far as I know, CF has various limitations (you can't create Cognito Identity Pools, for one).

Personally, I'd love to see this using Serverless as well, but given that they've just released v1 betas, I would hold off till it's stable (the API changed massively from pre-v1).

[pmuens]

Hey guys,
Philipp from the Serverless team here. I would really like to see this project using the Serverless framework as authentication is a tedious, but often inevitable feature!

We've just introduced Serverless v1 beta.1 recently and are about to introduce the second beta next week. The final, stable Serverless v1 will be ready soon.

I'd love to see this project running on Serverless. The docs are a good starting point to understand the new Serverless concepts and will hep you get things up and running quickly (the guide is a simple tutorial which will walk you through a Serverless service project from installing Serverless, to creation, deployment and removal).

Let me know if you have any questions or need any help when you're about to move it to Serverless v1.

[hassankhan]

Thanks for the quick update @pmuens! I was looking through the milestones on the project's Github page, and saw stuff relating to KMS in the upcoming beta (which is why I suggested waiting).

Do you have any best-practice recommendations on setting up a Cognito Identity Pool from Serverless? Or would that be something better handled by a Serverless plugin?

[flomotlik]

@hassankhan as you mentioned CF is not natively supporting Cognito yet, so it would have to be integrated in some other way. Our Plugin API is pretty simple so getting something in place that can support Cognito together with LambdaAuth should be straight forward I think

[pmuens]

@hassankhan here's a link to the plugin documentation where you can read more about plugin developmen: https://github.com/serverless/serverless/blob/master/docs/developing-plugins/building-plugins.md

Furthermore you might also want to look into our core plugins to see some real world examples.
E.g. here's the implementation of the package plugin which will zip the service for Serverless: https://github.com/serverless/serverless/tree/master/lib/plugins/package

[hassankhan]

I've written plugins for Serverless 0.5, seems like things have changed again :(

Is there a list of plugins that will by supported by core, so we can avoid duplicating work? I would love to help out but I don't want to step on anyone's toes :)

[pmuens]

Hey @hassankhan yes, the plugin system was updated / re-written from scratch. But is way more flexible now.

We've just started to announce our plans for our milestones in separate issues.
You can find them with the help of the "milestone-discussion" label:

https://github.com/serverless/serverless/labels/milestone-discussion

Furthermore we've introduced the "help-wanted-easy" and "help-wanted" labels we use to tag functionality where we need help from our awesome community:

https://github.com/serverless/serverless/labels/help-wanted-easy
https://github.com/serverless/serverless/labels/help-wanted

Would be great if you could look around and jump into the issue discussions (like you already did 🎉 !)

[ghost]

+1000

[mobal01]

+1

[Tazer]

+1 👍

[nascit]

+1