You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uploads are just put into a directory and then delivered through the upload url + /media.
Given this is just static content it could also be delivered directly by a webserver (that you might have to use anyway to front the ticker api) and thus not having another round-trip over the API and fetching the UUID from the db.
Currently, this is not easy as the uploads are stored in a timestamped directory tree.
IF the api would publish the uploaded media under a dedicated path (or would include the timestamped path in the media url) then you could just exclude the media/ path to be sent to the API process and deliver content directly.
The text was updated successfully, but these errors were encountered:
Uploads are just put into a directory and then delivered through the upload url + /media.
Given this is just static content it could also be delivered directly by a webserver (that you might have to use anyway to front the ticker api) and thus not having another round-trip over the API and fetching the UUID from the db.
Currently, this is not easy as the uploads are stored in a timestamped directory tree.
IF the api would publish the uploaded media under a dedicated path (or would include the timestamped path in the media url) then you could just exclude the
media/
path to be sent to the API process and deliver content directly.The text was updated successfully, but these errors were encountered: