Upload a photo from your local files, camera or your favorite social networks like Facebook, Google Photos or Instagram
Uploadcare Widget: file uploader.
Source code handling classes for webpack
Fine Uploader core ES6 class wrappers that provide additional features.
Building blocks for Uploadcare products integration
the processing and queuing engine for react-uploady
Smart Config Loader
Drag and drop sans the GUI
A cross-platform React file uploader component that provides a button to select files, displays selected files, and allows removing them.
Tree utilities which provides a full-featured extend and object-cloning facility, and various tools to deal with nested object structures.
An uploader elements to be used with Mux Direct Uploads
An uploader element for React that handles Mux Direct Uploads and a visual progress bar for you
placeholder package for now
Register font and emoji source for react-pdf document
Parses the images in png or jpeg format for react-pdf document
wrapper&context component to expose and provide react-uploady functionality
Uploader library implements html5 file upload and provides multiple simultaneous, stable, fault tolerant and resumable uploads
Blazing-fast, zero-dependency uploader for CloudKu. Supports auto-conversion, chunked uploads, and TypeScript. Easily upload images, videos, audio, and documents via Node.js.
React component for file uploads using Uploadcare
Multiple file upload plugin with progress-bar, drag-and-drop, direct-to-S3 & Azure uploading, client-side image scaling, preview generation, form support, chunking, auto-resume, and tons of other features.
TypeScript definitions for webpack-sources
[](https://github.com/paralleldrive/aidd)[](https://paralleldrive.com)
Converts a source-map from/to different formats and allows adding/changing properties.
Framework-agnostic file upload widget for Scaleflex VXP
provides a `has_video_encodings` class method to your models that allows you to configure and set up any Zencoder settings you will need to create multiple output video container formats (mp4, ogg, wmv, etc) from a single uploaded source file. Uses the Zencoder API (zencoder.com) and (as of now) expects you to have an S3 bucket where we can ask zencoder to place the generated files.
Chef-Berksfile-Env ================== A Chef plugin which allows you to lock down your Chef Environment's cookbook versions with a Berksfile. This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`. View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed. Installation ------------ /opt/chef/embedded/bin/gem install chef-berksfile-env Usage ----- In your chef repo create a Berksfile next to your Chef environment file like this, chef-repo/environments/[ENV_NAME]/Berksfile This is the default location that will used by the plugin. We have to put the Berksfile in its own directory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247). The berksfile should include any cookbooks that your nodes or roles explicitly mention for that environment, source "https://supermarket.getchef.com" cookbook "java" cookbook "yum", "~> 2.0" ... Next we need to generate our Berksfile's lock file, berks install Your environment file must by in `.rb` format and look like this, require 'chef-berksfile-env' # The name must be defined first so we can use it to find the Berksfile name "my_env" # Load Berksfile locked dependencies as my environment's cookbook version contraints load_berksfile ... Now our environment will use the locked versions of the cookbooks and transitive dependencies generated by our Berksfile. Upgrading to the latest dependecies is now as simple as, berks install Our Berksfile also provides an easy way to ensure all the cookbooks and their versions that our environment requires are uploaded to our chef-server, berks upload How the Plugin Finds the Berksfile ---------------------------------- If you are curious how the plugin knows to find the Berksfile in `chef-repo/environments/[ENV]/Berksfile`, you want to put your Berksfile somewhere else or you have run into this error `Expected Berksfile at [/path/../Berksfile] but does not exist`, this section will explain how this works and ways to tweak the path or fix your error. `load_berksfile` has an optional argument which represents the path to your Berksfile. This path can be pseduo relative (explained in a moment) or absolute. By default the value is `environments/[ENV_NAME]/Berksfile`. By pseduo relative I mean that its a relative path but the plugin will check to see if the directory we are executing from partially matches our relative path. So if we are running knife from `/home/chef-repo/environments` and our relative path is `chef-repo/environments/dev/Berksfile` the plugin will see that the relative path is partially included in our execution directory and will attempt to merge the two to come up with `/home/chef-repo/environments/dev/Berksfile`. If we can't make any match at all we attempt to guess the path by just joining the relative path with our execution directory. So why do we do this? Well the only way to use this plugin is if your environment is in Ruby format. Chef's `knife from file ...` uses Ruby's `instance_eval` in order to do this. This means the code on Chef's end effectively looks like this, env.instance_eval(IO.read(env_ruby_file)) which means that any context about the location of the environment file is lost. So we have no great way to discern the location of our environment Ruby file, so instead we guess.