Best practice / package management
Monkey Forums/Monkey Programming/Best practice / package management
| ||
| What is the best practice for keeping up to date between your projects, Monkey and all libs? There is no package management (yet) to do this, so how do you do it? Or you just overwrite current modules and fix what broke (if anything)? |
| ||
| I overwrite and fix. This is OK for active projects. Another solution that I can recommend for more "inactive" projects is to drop a copy of the current module version you are using into the game-folder, in that case it will more likley run even in the future. |
| ||
| Yeah that's what i'm doing now , but it kind of is not very manageable; one project might run monkey v53 with modules such and such and another monkey v66 with different module versions, so I need to play around with directories much or just have a copy of the entire monkey environment for every project. Also not handy for versioning with github. |
   |