Some of them could be overwritten.
I know for example we replace the 'watermark' logo with our corporate
logo, and that gets overwritten with the default jitsi one on each
update (I now have a script that puts it back).
Config file changes probably shouldn't get overwritten with an
upgrade/update. But that may also depend on what changes are happening
to jitsi meet at the time, but hopefully that should be handled nicely
in the upgrade process.
I would expect the index.html, css and language files to get
Best thing to suggest is to make the changes, make a note of what you
changed and then upgrade and see what has been overwritten and make a
plan/script/git repo/puppet manifest etc to put things back for you as
If you are making changes to language files because they are 'wrong',
I'd suggest that you make some changes to be committed back into the
source so further updates already have your correct translations in
On Sun, 2015-07-05 at 21:29 +0200, Frédéric wrote:
Le 01/07/2015 22:56, Frédéric a écrit :
> i installed jitsi meet with the deb packages (quick install)
> then i have made some change in some files index.html, language file,
> config files, etc.
> i would like to know what's is going to happen if i upgrade jitsi meet
> to the newest version
> will it reset all files to default version?
> i will have to make all my changes again or it will keep all my
> Thank you
users mailing list
Unsubscribe instructions and other list options: