Hi Vishal,
it makes sense to think global about your whole project for there are a couple of ways you could do things.
As mentioned especially for the image URL if you have the same relative paths you could use relative paths in your config file.
You cannot enter relative paths during setup but after having installed you can edit the config file and enter a reliative path.
If - as Andy said - you are using the same absolute file path on your server that should probably do what you want.
You could for example think of two Domains for you second install which point to the same server path.
you have your main install under https://www.main.domain/
you have you local setup under https://www.local.domain/
you have the same local setup under https://local.main.domain/
Not sure if you could make any benefit from that but defining Cookies beeing valid for main.domain instead of www.main.domain and redirecting users who are logging in to https://local.main.domain/ would allow you to navigate between both domains with different look and feel and just one login process.
I see no need for you to do that for what you describe but as I said thinking about your whole project makes sense because there are lots of options.
Regards
n||i||k||o
it makes sense to think global about your whole project for there are a couple of ways you could do things.
As mentioned especially for the image URL if you have the same relative paths you could use relative paths in your config file.
You cannot enter relative paths during setup but after having installed you can edit the config file and enter a reliative path.
If - as Andy said - you are using the same absolute file path on your server that should probably do what you want.
You could for example think of two Domains for you second install which point to the same server path.
you have your main install under https://www.main.domain/
you have you local setup under https://www.local.domain/
you have the same local setup under https://local.main.domain/
Not sure if you could make any benefit from that but defining Cookies beeing valid for main.domain instead of www.main.domain and redirecting users who are logging in to https://local.main.domain/ would allow you to navigate between both domains with different look and feel and just one login process.
I see no need for you to do that for what you describe but as I said thinking about your whole project makes sense because there are lots of options.
Regards
n||i||k||o