Problem: I have a small team working on a project that is using nopcommerce, one of the problems we are facing is that when one of our devs uploads a plugin using the nopcommerce dashboard and later down the week a different dev deploys their code to the save environment it overwrites that plugin and we lose that data.
How do you guys keep track of what's been installed on nopcommerce once the application has been deployed?
I know there is some kind of RDS settings we can set on nopcommerce to save the plugins.json file but can someone explain more about how this works?
Are there alternatives (perhaps saving the info on the database)?
TLDR; Looking for a solution to keep track of all plugins being installed on a deployed nopcommerce app. That way all dev members will always have up to date .dll and plugins.json info.
Bumping this post one more time, to help keep the thread alive
So we have 4 developers and we use BitBucket as our code source, we each make a copy of the code to our locals and each of our locals is pointing to a dev database. Whenever one developer makes a feature/bug change it gets committed to our bit bucket repo and then reviewed and merged into our code source.
The problem we are facing is that once we push our code to production anything on that environment gets wiped. Meaning If someone on the production environment downloads a plugin using the nopcommerce plugin management and they do not communicate it down to the tech department then their changes and plugin get wiped when the devs deploy the development code to production.
I am trying to find an autonomous solution that would help resolve this problem
Maybe im telling you something you already know here :)
I dont know bitbucket but when you say "push our code to production"
production being the website on IIS or where ever
Is that a function of bitbucket or are you doing it via another process outside of bit bucket ?
If it is outside of bitbucket then when uploading to IIS why does everything need to get uploaded ?
In the least case it could just be just uploadig one .dll or one .cshtml file
Sure there needs to be some rules about updating the core. But I would not have though everyone is working on the core each day and they would be working on plugins - or is that also not the case ?
Because working on a plugin you can either only upload just the plugin directory or have an install
package (no need to update everything)