Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
U
uppy-s3_multipart
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
open-source
uppy-s3_multipart
Commits
a4d5cd8a
Unverified
Commit
a4d5cd8a
authored
Oct 07, 2019
by
Janko Marohnić
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move "Configuration" and "Client" sections outside of "Usage"
parent
e0e99018
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
README.md
README.md
+2
-2
No files found.
README.md
View file @
a4d5cd8a
...
...
@@ -171,7 +171,7 @@ assignment** by default. Instead, it will just copy metadata that was extracted
on the client side. See
[
this section
][
metadata direct uploads
]
for the
rationale and instructions on how to opt in.
##
#
Configuration
## Configuration
This section describe various configuration options that you can pass to
`Uppy::S3Multipart::App`
.
...
...
@@ -315,7 +315,7 @@ Shrine.storages = {
}
```
##
#
Client
## Client
If you would rather implement the endpoints yourself, you can utilize the
`Uppy::S3Multipart::Client`
to make S3 requests.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment