Thank you so much Taher, Gil, Jacques for your valuable inputs and time.
All the shared information will be really useful for me, I will have look
into this.
Thanks again for your kind inputs! :)
- Best Regards,
Swapnil M Mane
On Fri, Nov 3, 2017 at 4:16 PM, gil portenseigne <
Hi Jacques,
Yes I'm interested to see Michael solution :)
There is a Jira about env variable configuration :
https://issues.apache.org/jira/browse/OFBIZ-9498
Gil
On 03/11/2017 11:40, Jacques Le Roux wrote:
Hi Gil,
Michael also has a solution, I suggested to create a Jira and share
our
Hi Gil,
Michael also has a solution, I suggested to create a Jira and share our
experiences to get a consensus :)
Jacques
Le 03/11/2017 à 10:00, gil portenseigne a écrit :
Hello Swapnil,
Your mail make me think about a proposal i made this summer about environment
configuration :
Hello Swapnil,
Your mail make me think about a proposal i made this summer about
environment configuration : https://s.apache.org/8mJh
This wasn't adopted in a first place, and i wanting to investigate in a
better way to do this, if no other opinions about it raised... (using
Hello Swapnil,
You'll find a related discussion in [1]. Essentially, my opinion on
the subject is to utilize the build system but try to avoid as much as
possible embedding additional "state" into the code base. You can read
the full thread for more details.
[1] https://s.apache.org/9wPk
On
Hello team,
Nowadays advance frameworks allow us to run the application in the
different mode, e.g. dev mode, production mode etc.
For dev mode, we may have the different set of configurations/settings and
for production, it may be different.
Here are few examples, there can be many
1.) Cache
