Hi Chinmay,
thanks for your input!
Just a brief thought: we have an Apache Webserver in front of every
productive system, connected with the integrated OFBiz Tomcat through ajp.
This allows fine grained configuration for the rendering of static
resources, caches, compression, request
Le 03/12/2019 à 20:06, Mathieu Lirzin a écrit :
Jacques Le Roux writes:
With OFBIZ-11302 Mathieu removed the ofbizDebug Gradle task, because "ofbiz
--debug-jvm" can be used instead.
This is now ‘gradlew "ofbiz" --debug-jvm’ with the --debug-jvm outside
of the double quotes.
g ofbiz
Hello,
>
> > I guess that using existent Github should be ok for official pull
> > request, if not, it's always ok to have and attached patch or
> > other gitlab reference.
>
> You mean "Github reference" I guess ?
>
For this one a really mean gitlab reference like the nereide public
gitlab
Hi All,
I wanted to bring attention to the handling of HTTP caching in OFBiz. We
can segregate three different areas(possibly more) which involve the cache.
These are listed below:
1. Cache Web resources in CMS.
2. View Rendering.
3. Request Redirects.
Furthermore, details are listed
Jacques Le Roux writes:
> Le 02/12/2019 à 18:18, Mathieu Lirzin a écrit :
>>
>> Jacques Le Roux writes:
>>
>>> With OFBIZ-11302 Mathieu removed the ofbizDebug Gradle task, because "ofbiz
>>> --debug-jvm" can be used instead.
>> This is now ‘gradlew "ofbiz" --debug-jvm’ with the --debug-jvm
Hello,
As far as I am concerned, I will never be enthousiastic regarding
adopting yet another proprietary platform.
Gil Portenseigne writes:
> +1 to use gitlab features to work around code, that will help
> collaboration.
>
> I don't know if there is an Apache alternative to get the features
