|
|
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.
|
|
|
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 your PEP support contact 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.
|
|
|
|
|
|
At this point, **all PEP environments have been migrated to the new situation**. Older PEP client software versions can no longer connect to the environments. Instead new versions should be used, which are available at the locations detailed below.
|
|
|
|
... | ... | |