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
Thanks for the tool, it was useful with little tweaks for the version we are using.
However, I am bit confused on the paths used for attachment. My apologies to ask this question here instead of RocketChat Forum, as I was unable to get any response there. Could you kindly help me with the below query?
Is url in rocketchat_uploads collection in mongodb supposed to have an absolute path like https://site.com/\<path> or just <path>?
In one of our test instances running rocket chat version 1.x, it is using relative paths, but another instance of 3.x version is using absolute paths.
So I wonder if it is our misconfiguration in the 3.x instance, as my understanding is that the absolute paths will break once the site’s ROOT_URL is changed.
So which is the supposed way and what could cause the absolute paths in URL instead of relative paths?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for the tool, it was useful with little tweaks for the version we are using.
However, I am bit confused on the paths used for attachment. My apologies to ask this question here instead of RocketChat Forum, as I was unable to get any response there. Could you kindly help me with the below query?
Is url in rocketchat_uploads collection in mongodb supposed to have an absolute path like https://site.com/\<path> or just <path>?
In one of our test instances running rocket chat version 1.x, it is using relative paths, but another instance of 3.x version is using absolute paths.
So I wonder if it is our misconfiguration in the 3.x instance, as my understanding is that the absolute paths will break once the site’s ROOT_URL is changed.
So which is the supposed way and what could cause the absolute paths in URL instead of relative paths?
Thanks in advance!
The text was updated successfully, but these errors were encountered: