Matias Woloski woloski

wt create webtask.js --auth0

When browsing the webtask URL, the user will get a page with Lock. Once logged in, the result of the webtask will be shown.

bcrypt: A bcrypt library for NodeJS.
pg: PostgreSQL client - pure javascript & libpq with the same API
q: A library for promises (CommonJS/Promises/A,B,D)
node-uuid: Rigorous implementation of RFC4122 (v1 and v4) UUIDs.
optimist: Light-weight option parsing with an argv hash. No optstrings attached.
aws-sdk: AWS SDK for JavaScript
validator: String validation and sanitization
cheerio: Tiny, fast, and elegant implementation of core jQuery designed specifically for the server
knox: Amazon S3 client
consolidate: Template engine consolidation library

DRY

Labor specialization helped spur the Industrial Revolution and the technology-driven world in which we live. I firmly believe that startups are the equivalent of this century, providing the the building blocks for today's apps:

Sendgrid spent years thinking about e-mail delivery.
Stripe has been processing payments for 4 years.
Twilio has cracked all the details of guarranted SMS delivery across the world.
Auth0 has experts on the subject that went through every detail of authentication, authorization and user management.
... and so on

Why developers fall in love with your product?

1. Awesome docs

What do we do the first time we want to use a library? We read the Github README or the Wiki. Why? First and foremost, because we can do what we know best: Copy & Paste code snippets. Also, it gives us an overview of how we can use the library and the APIs it has. If the APIs weren’t good, we’d just search for another one.

Products should follow this same idea. We should have documentation from which we can copy and paste. For a product, that means tailored documentation for every user.

Another thing we love is reading code. It’s literature for us!That’s why it’s nice if every document includes an up-to-date sample for every major platform/technology that we can just download, run locally and read its code.

Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client-organizations (tenants)

Let's start by enumerating some multi tenant applications and understand how they handle it.

Slack

Authentication:

Create a Client ID and an API Key on Google API Console. Set the Allowed Origins (e.g. localhost:3000).
Create an app in Auth0 and set the Allowed Origins (e.g. localhost:3000) and the callback to https://yours.auth0.com/mobile

Install deps

go get github.com/gorilla/mux
go get github.com/astaxie/beego/session

Run





	┌──────────────────┐ ┌──────────────────┐
	│ │ webtask token │ │
	│ Website │◀──(w/id_token)────▶│ Auth0 │
	│ │ │ │
	└──────────────────┘ └──────────────────┘
	▲

	PUT https://YOUR-ACCOUNT.auth0.com/api/connections/YOUR-CONNECTION-NAME
	content-type: application/json
	authorization: Bearer ACCESS-TOKEN

	{
	"options": {
	"bareConfiguration": {
	"test": "foo3"
	},
	"enabledDatabaseCustomization":true,