Extended User bean : how to manage on a fresh install

Hello,

We're having in our environnement a customized User with custom fields and amongst them an id referencing a whole other "CustomUser" entity.

If we're configuring git accordingly to Sugar recommandations, we won't provide the file custom/application/Ext/Include/modules.ext.php after un git clone.

BUT, as our user needs the CustomUser bean parts, we're then stuck in a loop :

- impossible to login due to null bean for CustomUSer (as the EXT files are not yet generated)

- impossible to repair to generate the correct file because this needs a login...

To fix it, we provide manually some working custom/application/Ext/Include/modules.ext.php file, but in a CI/CD environment I would love to see a better way.

So, is there something we're doing the wrong way here ? Some hidden mechanics to avoid this ? Any help would be greatly appreciated.

Thanks in advance,

Vincent

Parents Reply Children
No Data