U
Right, that's easy however rather than http:// I need file:// to work.
Also note this is visually the intended result which can be achieved however the image itself is served from the provided http source.
In my use case it's intended the http source go away. I have at a OS file system level the contents of the old http source of the images. I would like to use file:// so that nodebb 'owns' the source files rather than just have content of http hyperlink
PS. that's a darn good looking burger.
Looking to solve this problem as well.
Seems this method only creates a hyperlink as the content of the Topic post
Where is this guys solution at least renders the image as the body within the content of the Topic post.
both of these presume the image source is available via HTTP.
What if the file are on the filesystem? file:// doesn't seem to work as the [img] doesn't invoke the upload process.
From a review of the API it seems to post via API one has to upload the image first to assure the file is in the assets directory then a second API call to associate the asset URI to a Topic.
Since ![image-url] and [img] are limited i'm not seeing a clear path forward as i'd like nodebb to 'own' the content.
We've hobbled together a script to mass post via ![image-url] and visually it's what we'd like but again it's function is deponent upon the provided HTTP server being available. -no sad panda.
pls advise
