|
|
**THESE INSTRUCTIONS ARE STILL BEING WRITTEN AND SHOULD NOT BE FOLLOWED YET**. Users will receive instructions by e-mail when migration should be started.
|
|
|
|
|
|
The PEP code base has been restructured to facilitate the continued development, maintenance, and support of the PEP software. The rollout of the new structure started in April of 2022 and makes some changes to PEP's deployment mechanism. As a result, existing users will need to perform some one-time manual actions to migrate to the new situation.
|
|
|
|
|
|
We've tried to make things as simple and as backward compatible as possible, and we hope that the instructions on this page will provide sufficient guidance for users to migrate their setup to the new approach. But if things are unclear or don't work as expected, please don't hesitate to contact support@pep.cs.ru.nl so that we can improve the instructions. The support team can also be contacted to provide (e-mail) assistance translating the generic instructions to your specific situation.
|
|
|
|
|
|
**Only acceptance environments have been updated to the new situation** at this point. Users will be notified when the production environments are being migrated.
|
|
|
|
|
|
# Windows users
|
|
|
|
|
|
The PEP client software for Windows is distributed as an (MSI) installer package. Once the software (for a particular environment) has been installed, users that run the `pepAssessor` GUI application are prompted to upgrade their software if/when a new version becomes available. The upgrade can then be installed with minimal user intervention.
|
... | ... | |