Deploy playground into website vs separate S3 bucket about uppy

[kvz]

Actually guys - does it make sense to store examples directly inside ./website? Then we get a local webserver, nice layout, deploys to GH pages, and no copying of files around for free.

[kvz]

However, we only deploy master. So we would not be able to easily preview different branches online ...

[kvz]

However, we only deploy master. So we would not be able to easily preview different branches online ...

I'm currently leaning towards screwing that usecase as I think this is pretty great to have: http://uppyjs.io/examples/index.html

If testing other branches requires running a command locally - so be it. (?)

[kvz]

I've made up my mind and want the examples inside the website for all to play with. @hedgerh May I ask you to take care of this?

If you just make website-preview, you can open http://0.0.0.0:4000/examples/dropbox.html for instance to try and get the Dropbox example to work there?

[hedgerh]

Sounds good

[kvz]

Excellent 👍 Just to be clear: The website is already automatically deployed to gh-pages by https://github.com/transloadit/uppy/blob/master/.travis.yml#L19.

That means this separete s3 bucket thing can be removed once examples work inside the website: https://github.com/transloadit/uppy/blob/master/.travis.yml#L26

[arturi]

This is how it works now, right? Reopen if I’m wrong.

[kvz]

👍