Autopublishing 3rd party libraries

Dan Dascalescu / @dandv
& Luca Mussi / @splendido

Meteor Devshop SF 2015-Feb-26

Follow-up from Dec '14

Luca Mussi

@splendido

Built autopublish

• Too many wrappers for 3rd party libraries
• ...because "the others were outdated"

Why?

autopublish.meteor.com

(no connection with the autopublish package)

3rd party library has new release?

Autopublish package on Atmosphere!

How it
works

Successful integrations

• d3
• Bootstrap
• Font Awesome
• Semantic UI
• Materialize

grant autopublish access
to create GitHub webhooks
 

OR if you're paranoid...
 

create the webhook yourself
(+ one manual step from us)

Requirements for package maintainer

• meteor admin get-machine  # to build

• git clone latest release of upstream repo
• update package.js with latest version number
• run tests if any

• meteor login  # to build machine
  

• meteor publish

Webhook flow

• robustness
• binary packages - using different build machines
• permanent access to build machines
• approval/quality process

Next steps

• official blessing by MDG
• OAuth flow extension

Help wanted

Takeaway

Want to package a 3rd party library?

Use autopublish.meteor.com