JREBEL LIFERAY REMOTE SERVER HOW TO

To simplify the configuration, providing the full context path in the remote server URLs (within the IDE configuration) is now optional.

JREBEL LIFERAY REMOTE SERVER HOW TO

Please refer to the the migration instructions below to learn how to set up the new security.Дropping context paths from remote server URLs It does need to be initialized on the server. The new password-based implementation is scoped per server and does not depend on projects that are deployed to that server. This meant that it would be spread around on multiple remote servers, and that it would get updated with every project redeployment. Previously, the public key was defined in rebel-remote.xml within the deployed. We have re-implemented this feature, replacing the complicated public/private key configuration with a simple password. Do keep in mind that a remote server running in your internal network (or otherwise protected by the network layer) does not really need this extra security.ДЇor users that do wish to use additional security, we have good news. We provide optional security for the communication protocol between the IDE and the remote server. This becomes increasingly useful as the number of your remote projects grows.

This means adding the remote servers once and reusing the configuration for the projects deployed to that server.

The new JRebel plugin introduces central remote server management. Until now, you had to separately configure the remote server URL and other settings for each project. Centralized remote server management in your IDE

Jrebel liferay remote server