Users who work on remote locations and who are connected to Studio Server through a slow connection can suffer from poor performance such as long waiting times when saving files.
To improve the performance, a distinction can be made in Studio Server between 'local' and 'remote' users and subsequently used by features such as offloading heavy InDesign tasks such as file generation for local users.
Configuring Studio Server
Info: Performing the described step requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.
Whether a user is considered to be local or remote is controlled by defining the user's IP address — or a range of IP addresses — in the configserver.php file of Studio Server through an 'include' and 'exclude' option.
It works as follows:
- Remote users are all users who are defined in the 'include' option.
- Local users are all users who are defined in the 'exclude' option.
Note:
|
Step 1. In the configserver.php file (recommended: config_overrule.php file) of Studio Server, locate the Remote users section.
// ----------------------------------------------------------------------
// Remote users
// ----------------------------------------------------------------------
Step 2. Define the IP addresses of the users who should be treated as a remote user under the INCLUDE option (for details about defining these addresses see below):
define( 'REMOTE_LOCATIONS_INCLUDE', serialize( array(
)));
Step 3. Define the IP addresses of the users who should be treated as a local user under the EXCLUDE option (for details about defining these addresses see below):
define( 'REMOTE_LOCATIONS_EXCLUDE', serialize( array(
)));
Defining IP addresses
Use any of the following notations:
IP range | Matches with |
---|---|
'192.0.0.1' | '192.0.0.1' only |
'192.0.0.*' | ['192.0.0.0'...'192.0.0.255'] |
'192.0.*.*' | ['192.0.0.0'...'192.0.255.255'] |
'192.0.0.0/16' | ['192.0.0.0'...'192.0.255.255'] |
'192.0.0.0/24' | ['192.0.0.0'...'192.0.0.255'] |
'192.0.0.0/255.255.0.0' | ['192.0.0.0'...'192.0.255.255'] |
'192.0.0.0/255.255.255.0' | ['192.0.0.0'...'192.0.0.255'] |
'192.0.0.0-192.0.0.255' | ['192.0.0.0'...'192.0.0.255'] |
'192.0.0.0-192.0.255.255' | ['192.0.0.0'...'192.0.255.255'] |
'2001:db8::1' | '2001:db8:0:0:0:0:0:1' only |
'2001:db8::/32' | ['2001:db8:0:0:0:0:0:0'...'2001:db8:ffff:ffff:ffff:ffff:ffff:ffff'] |
'2001:db8::/64' | ['2001:db8:0:0:0:0:0:0'...'2001:db8:0:0:ffff:ffff:ffff:ffff'] |
'2001:db8::-2001:db9::' | ['2001:db8:0:0:0:0:0:0'...'2001:db9:0:0:0:0:0:0'] |
'2001:db8::-2001:db8::ff' | ['2001:db8:0:0:0:0:0:0'...'2001:db8:0:0:0:0:0:ff'] |
Examples:
|
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.