No problem!! Yes serving external files with a proxy server is always like
this - lots of assumptions that lead to lots of confusion. It's a bit
outside most use cases I guess. Using nginx to serve media files outside
TW is absolutely the way to go though IMO the performance is way worth it.
On Thursday, December 10, 2020 at 2:44:46 PM UTC-5 duche...@gmail.com wrote:
> Re my last paragraph above I now understand that '<source
> src="media/BigBuckBunny_...' refers to *the root statement of your nginx
> site configuration file, * so no need to provide the full path of the url
> (https://...).
>
> Too bad this wasn't documented.
>
> Anyway this now works fine and your assistance has been very useful,
> thanks digit!
>
> Le jeudi 10 décembre 2020 à 10:54:40 UTC-5, duche...@gmail.com a écrit :
>
>> Yes, it works that way, i.e. when I input the url of a file located on my
>> ngnix server to the 'source src=' .
>>
>> However I thought that I could also address a video located within the
>> tiddlywiki folder, as we do with images. And Tiddlywiki shows right such a
>> video as it does for an image using the transclusion syntax:
>> {{video.mp4}}. The only problem is that the plugin isn't used hence no
>> control on the size of it.
>>
>> Isn't it what the statement ' <source
>> src="media/BigBuckBunny_SampleVideo_1280x720_1mb.mp4" type="video/mp4"/>'
>> from TwTube Github page
>> <https://thediveo.github.io/TwTube/output/twtube.html> suggests?
>>
>> Thanks again digit!
>>
>> Le mercredi 9 décembre 2020 à 20:07:12 UTC-5, digit...@gmail.com a
>> écrit :
>>
>>> So I don't think it will work this way - trying to access it by tw
>>> import. You have to think of it this way - *nginx is serving the file*
>>> within tiddlywiki. nginx has to be able to serve the file separately on
>>> its own. Here is the code I put in for the video you see in my wiki:
>>>
>>> ```
>>> <$videojs controls="controls" fluid="fluid" width="800">
>>> <source src="https://digitalap3.com/christinemessages_0.mp4";
>>> type="video/mp4">
>>> </$videojs>
>>> ```
>>>
>>> So I put the video in a place that I can directly access it from nginx
>>> if I copy paste the address in the src into the address bar. It is the
>>> same for external images. External images or any files are not imported
>>> directly into tiddlywiki. Nginx is serving the file to the browser inside
>>> of tiddlywiki. This is what makes relative addresses as your src tricky.
>>> Nginx is looking relative to the webroot in the website's config file.
>>>
>>> On Wednesday, December 9, 2020 at 10:42:06 AM UTC-5 duche...@gmail.com
>>> wrote:
>>>
>>>> I'm getting closer!
>>>>
>>>> One thing I missed was to import the videos using tiddlywiki import,
>>>> rather than just copying them from the server file system into mywiki
>>>> directory. So I was missing the .meta file.
>>>>
>>>> Now if I put this imported name within the <source
>>>> src="BigBuckBunny_SampleVideo_1280x720_1mb.mp4" type="video/mp4"/>
>>>> statement, I get an error message.
>>>> If I just put the imported video name within {{ }} then I can play it,
>>>> but without any controls of the visual.js / Twtube plugin, see below.
>>>> BTW I can play without issue your video that I copied into my test
>>>> tiddler, probably because this is a network location rather than a server
>>>> file.
>>>>
>>>> So all of this seems to lead to a file location or permission problem.
>>>> I'll have to play with Firefox Web Developer tools to find the address /
>>>> file location that is asked.
>>>>
>>>>
>>>>
>>>>>>>>>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/bec2b0db-f066-42bc-bc64-6f4ed8947592n%40googlegroups.com.
