Somes modules/plugins require an URL'ish/to edit the reverse proxy
-
As I used Dolibarr a while ago, I was pleased to see it available in Cloudron.
But as I remember, but not truly able to express properly (that explain the tittle which 'ish and /)
domes modules require to add lines in the web engine (Apaches or NGINX).Also, such as like with Element/Matrix, I think extra DNS pointer need to be done.
Here few modules which I believe need extra configuration and I wonder how to make it happen.
-
members: such as the plugin members could publish Public self registration form but when it is active the link point to http://localhost/public/members/new.php
-
ticket: could have a Public interface
http://localhost/public/ticket/index.php -
website
-
WebDAV which point to: local host/dav/fileserver.php
and potentially
- recruitment
- DMS/ECM the electronic documents
- scheduled job
- API/Web (REST, SOAP)
- oAuth
- FTP/FTPS
-
-
Is this about the generation of those additional public links, currently defaulting to
localhost
? I don't really know dolibarr, but wouldn't that come from some config file?Do you have a link to the corresponding documentation on how to configure those URLs?
-
@nebulon said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
documentation on how to configure those URLs?
Let's take one module at time
For example of the website module the instructions are here under Deploy | Publish your website (the last part)
https://wiki.dolibarr.org/index.php/Module_Website -
@nebulon said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
localhost
OK it might ne easier like you said, or at least for most of the modules I pointed out they seams to take their source from the config file
inside /app/data/conf.php
the first variable point to localhost which probably should be sub.domain.tld of the container. -
@JOduMonT said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
app/data/conf.php
So I just replaced the first line from localhost to my sub.domain.tld then restart the app and that did the job for the modules membership, ticket and WebDAV
But the module website still need something more
-
@nebulon
the localhost issue is easy to fixbut what about the rest?
Do you think it is something fixable?
How I could point multiple domain into one container such as
dolibarr.domain.tld is the backend
and www.domain.tld is the website generated by dolibarr through is module web -
@JOduMonT for multiple domains, we would need to enable
multiDomain
https://docs.cloudron.io/packaging/manifest/#multidomain for that app then. I think we were not aware of that requirement for Dolibarr. Alternately, depending on what is wanted, you can also setup redirect domains for the app to be reachable on other domains. -
@nebulon said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
multiDomain https://docs.cloudron.io/packaging/manifest/#multidomain
I saw Cloudron released a new version of Dolibarr 2 weeks ago but few issues, like this one still remain.
It it something we could work on it ?
this and the less important/urgent that one ? -
@JOduMonT said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
inside /app/data/conf.php
Still point to localhost which is not great because some modules relay on that information.
also that variable should point to https:// subdomain . domain . tld
instead of http:// subdomain . domain . tld -
-
@girish said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
I will look into the issues.
If you wonder why I show so much interest into Dolibarr; how my motivation; it's because, soon I'll move in France and Dolibarr is the only active open source project I found which respect the French law NF525 and others law related to business tax.
-
@girish said in Somes modules/plugins require an URL'ish/to edit the reverse proxy:
@JOduMonT yes, I think it's great you are reporting the issues here. Dolibarr was initially contributed, so we didn't do as complete a vetting as we would like to. I will look into the issues.
@girish did you had any chance to look at it ?