The ul here is meant to serve as a quick
way to check what videos are being served
as well as removing videos
+ category::VideoMeta::as_li built for admin video list
This is basically how we spit this out onto
the DOM
There may be more changes that could be
added to improve documentation however
this is meant to be a good start.
!+ There is also a new redirect endpoint for /admin/dashboard
This just a convenience thing so that people
don't have to remember the '/dashboard'
part of the admin route.
This is primarily for organizational reasons
however it should make things easier to
track as the complexity increases with
features getting filled out.
Doing this means we only have to serve up a single js
file across all pages, reducing the amount of fuckery the backend
has to do. Also we can start marking the js to require much heavier caching
Features implemented thus far are proven to be working however
they will be left as optional features until they are more properly
tested in some kind of staging environment
These are only compiled with the --features admin flag so placing these
alongside the normal feature dependencies is totally safe and won't
increase compile times as they are not compiled in default builds. They
are however downloaded so some extra overhead is spent fetching them
for builds.
This is mostly to remove the extensions which mess with OpenGraph meta fetching
Most services like Discord/Twitter/Facebook/Linkedin will not bother using the
Available opengraph metadata if an extension is detected as its assumed to be
a plain file
*! Async requests for category pictures
With async requests in place HTTP2 should be defaulted more often now
It is recommended now however to enable it with the reverse proxy of choice
Usage of this role is still sketchy however at least all the
required playbooks are in place
Main issue at the moment is the interfacing with these playbooks
This should make building much more straight forward in the future
as currently builds have to follow a much stranger method
- Removed fluff storage file
No longer going to support uploading API. This is with the assumption that
most who use this software are going to know how to upload files to their
server anyway
