Proper etiquette when enabling/disabling extensions in production mode?

[itimdavid27272]

What is the proper protocol for enabling a custom built extension during production mode?

When I run php bin/magento setup:upgrade I get the following error:

The directory "/chroot/home/af3d0522/45913c4122.nxcli.net/magento/generated/code/Magento" cannot be deleted Warning!rmdir(/chroot/home/af3d0522/45913c4122.nxcli.net/magento/generated/code/Magento): Directory not empty

Should I be deleting the code within generated/code and then running the above command so that Magento acknowledges the extension? I'm going to re-try tonight to enable my own custom extension along with a few others that are disabled. If anyone can provide a run-down on best practices I would really appreciate it. It's a M2 2.3.4 store.

[Sanjay Jethva]

@itimdavid27272 

Give a try to the below commands after enabling/disabling the module:

chmod -R 777 var generated
 
[php/php7.2/php7.3] bin/magento s:d:c