-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Refactor to allow URL templating, instead of using prefix - Add support to view listing from different domain.
- Loading branch information
Showing
4 changed files
with
53 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,42 @@ | ||
window.vyw = | ||
/* | ||
/** | ||
* You may want to change this if your nginx | ||
* json listing was set in different location | ||
* json listing was set in different location, | ||
* `<PATHNAME>` will be replaced by its respective | ||
* path to the directory listing. Listing can accept | ||
* url with different domain, but the server should | ||
* support CORS. | ||
*/ | ||
prefix: '/.json' | ||
list-endpoint: '<PATHNAME>.json' | ||
|
||
/* | ||
/** | ||
* this prefix will be applied when accessing files | ||
* you can change this according to your real file location | ||
* as set in nginx | ||
* as set in nginx. Or you can specify file path with different | ||
* domain, as long as it's corresponds with `<PATHNAME>` value. | ||
*/ | ||
file-prefix: '/' | ||
file-endpoint: '<PATHNAME>' | ||
|
||
/* | ||
/** | ||
* specify thumbnailer service to use, | ||
* `<FILEPATH>` will be substituted with | ||
* its respective file path | ||
* `<PATHNAME>` will be substituted with | ||
* its respective file path, you can specify | ||
* `original-image` which essentially equal to specifying | ||
* `//<HOST><PATHNAME>`, but then displaying thumbnail will be | ||
* stricted to file with maximum size = <value of maxSize> | ||
* If host domain is needed in thumbnailer, | ||
* `<HOST>` and `<HOSTNAME>` is available to use. | ||
*/ | ||
thumbnailer: \//192.168.77.128<FILEPATH> | ||
thumbnailer: \original-image | ||
|
||
/* | ||
/** | ||
* this set max file size to allow thumbnail generation | ||
* `0` means no thumbnail. | ||
* Only used if thumbnailer value is `local` | ||
* Only used if thumbnailer value is `original-image`. | ||
*/ | ||
max-size: \100M | ||
|
||
/** | ||
* Image type supported by thumbnailer. | ||
*/ | ||
supported-image-type: [ \jpg \jpeg \gif \png ] |