现代化的上传组件。 https://uppy.io/

Artur Paikin a1e33441af Second crack at reimplementing async.waterfall and async.parallel in Promises 9 jaren geleden
bin b34d3a5628 Merge 9 jaren geleden
examples 6f397c82e0 My name is Uppy now 9 jaren geleden
src a1e33441af Second crack at reimplementing async.waterfall and async.parallel in Promises 9 jaren geleden
test d07360a207 Rename to uppy 9 jaren geleden
website 79b0d964e2 Text improved 9 jaren geleden
.babelrc a57389fdc8 Styles and babel config for the future 9 jaren geleden
.editorconfig d257f8ff52 Add tests and eslint 9 jaren geleden
.eslintrc be4d3f07b7 Ideally it should just ignore window, document and such 9 jaren geleden
.gitignore b34d3a5628 Merge 9 jaren geleden
.travis.yml cdab835310 Automatically deploy website onto gh-pages (if master and not PR). Fixes #34 9 jaren geleden
.zuul.yml d257f8ff52 Add tests and eslint 9 jaren geleden
CONTRIBUTING.md 8a5ead84ee Markdown fixes 9 jaren geleden
LICENSE 320c8a16ef Getting a sandbox going with the worst possible layout 9 jaren geleden
Makefile e1a36bcf67 Automatically update the website with ./dist information 9 jaren geleden
README.md 4958cffb44 Design goals 9 jaren geleden
bs-config.js 2c8930c706 Playground fixes 9 jaren geleden
classes.es6 49c7c7e085 Files can be objects. Container can be initialized at runtime 9 jaren geleden
core.js 5014604589 added root core/plugins indexes 9 jaren geleden
package.json a1e33441af Second crack at reimplementing async.waterfall and async.parallel in Promises 9 jaren geleden
plugins.js 5014604589 added root core/plugins indexes 9 jaren geleden
uppy-core-plugins-architecture.jpg 19454ea75f Architecture updated 9 jaren geleden

README.md

uppy

A work in progress - nothing to see here.

Check open issues for our Minimum Viable Product.

Uppy Development

First clone and install the project:

git clone git@github.com:transloadit/uppy.git
cd uppy
npm install

Now to get a sandbox environment set up, type:

npm run preview

This will npm run build the project into ./build, and then serve that directory using a simple static http server.

Website Development

We keep the uppyjs.io website in ./website for so it's easy to keep docs & code in sync as we're still iterating at high velocity. For those reading this and screaming murder, HashiCorp does this for all their projects, and it working well for them on a scale vastly more impressive than ours.

The site is built with Hexo, and Travis automatically deploys this onto GitHub Pages (it overwrites the gh-pages branch at every deploy).

Content is written in Markdown and located in ./website/src. Pull requests welcome!

The website is currently a clone of Yuxi Evan You's Vue.js website (view license) - just so we can hit the ground rolling in terms of setting up Haxo etc. Obviously as soon as possible, we should start rolling out our own layout & content.

./website/update.js is called during website builds to inject the Uppy versions & filesizes into the documentation. website in an independent folder and so it cannot rely on anything from the root project, without update.js explicitly making it available (copying).

It's recommended to exclude ./website/public/ from your editor if you want efficient searches.

For local previews on http://127.0.0.1:4000 type:

make website-preview

FAQ

What does Travis do?

Travis should:

  • check out code
  • build project
  • run unit tests
  • run acceptance tests
  • copy/install the built project into any examples/*/
  • deploy the examples to our hackathon S3 bucket in a folder named by branch (http://hackathon.transloadit.com/uppy/master/index.html), so we can all play with the current state of the project & examples per branch, without installing everything locally.