This should close issue #42
Reviewed-on: https://git.mills.io/prologic/tube/pulls/43
Co-authored-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
Co-committed-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
This changes the handling of external thumbnails as mentioned in issue #41
If there is an external thumbnail file, it is going to be used, even if there is an embedded thumbnail in the mp4 file.
Reviewed-on: https://git.mills.io/prologic/tube/pulls/44
Co-authored-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
Co-committed-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
This works for me, but for a more public site, I think I'll also add a boolean attribute named "upload_allowed" and "writable" to Config.Library..
Something to allow you to configure which directories can receive new uploads, and which directories we consider writable for other purposes (like editing meta data in yml, creating new thumbnails, ...)
Co-authored-by: Heinrich Langos <gumbo2000@noreply@mills.io>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/39
Co-authored-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
Co-committed-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
This change introduces the ability to read additional
or modified metadata like title or description from a
YAML file.
Just like thumbnails are read from "filename.jpg", we now
look for "filename.yml" and override the meta data that
is embedded in the video file.
This is my very first look at golang, so please tell me if, or rather "where" I went wrong. ;-)
Co-authored-by: Heinrich Langos <gumbo2000@noreply@mills.io>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/37
Co-authored-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
Co-committed-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
I hope this PR closes#9
Co-authored-by: Heinrich Langos <gumbo2000@noreply@mills.io>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/38
Co-authored-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
Co-committed-by: Heinrich 'Henrik' Langos <gumbo2000@noreply@mills.io>
This fixes#28.
Since we only use a single FontAwesome, I decided to just use the SVG (which FontAwesome considers the code comment within appropriate attribution). I further decided "screw it, let's inline it", because it avoids unnecessary complexity, and we can always punt it out to another file later if we need to.
Co-authored-by: Jacob Weisz <inbox@jacobweisz.com>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/30
Co-authored-by: Jacob Weisz <ocdtrekkie@noreply@mills.io>
Co-committed-by: Jacob Weisz <ocdtrekkie@noreply@mills.io>
I am not quite done here, I need to finish some of the packaging metadata, and I am going to maybe take a pass at permissions prior to release. Opening the pull request so you can easily track the progress.
Note that Sandstorm app metadata is supposed to be less than 1 MB total, so I optimized your screenshots. I dare you to tell the difference with the naked eye.
Co-authored-by: Jacob Weisz <inbox@jacobweisz.com>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/26
Co-authored-by: Jacob Weisz <ocdtrekkie@noreply@mills.io>
Co-committed-by: Jacob Weisz <ocdtrekkie@noreply@mills.io>
just some basic docker make file stuff to make it easier for local dev.
Co-authored-by: gedw99 <gedw99@gmail.com>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/17
Co-authored-by: gerard webb <gedw99@noreply@mills.io>
Co-committed-by: gerard webb <gedw99@noreply@mills.io>
Gitea doesn't play nicely with absolute links in markdown, and requires relative links for things to resolve. Otherwise you get a 404.
Co-authored-by: Tai Groot <tai@taigrr.com>
Reviewed-on: https://git.mills.io/prologic/tube/pulls/1
Co-authored-by: taigrr <taigrr@noreply.git.mills.io>
Co-committed-by: taigrr <taigrr@noreply.git.mills.io>
