-build-merge-requests: Track and deploy merge-requests (true by default).Platform integration:add -type =gitlab -token =GITLAB-ACCESS-TOKEN -base-url = -server-project =sandbox/my_application -project =PLATFORMSH_PROJECT_ID Copy the token and save it somewhere (you can’t see it again.).read_repository (to read the repository).Ensure the token has the following scopes:.Give the token a name such as “Platform.sh Integration”.In the Settings menu, choose Access Tokens.In GitLab, navigate to the project you want to integrate.Note that for the integration to work, your GitLab user needs push access to the repository. (you can use a personal access token but a project access token has more limited permissions). To integrate your Platform.sh project with an existing GitLab repository, Delete the environment when merging a pull request.Rebuild the environment when pushing new code to GitLab.Create a new environment when creating a branch or opening a pull request on GitLab.In this configuration, MirrorSync should be set to sync fairly often, such as every 5-10 minutes.The GitLab integration allows you to manage your Platform.sh environments directly from your GitLab repository. ![]() For instance, if you have an online storefront running with MySQL or Oracle at a remote data center, but you need to have instant access to all of the orders in a database running on FileMaker Server, MirrorSync can selectively sync certain SQL tables to FileMaker, even if the table and field names do not match. For integration with non-FileMaker databases, MirrorSync is the simplest and most efficient way to accomplish this. This means that each server only needs to work with 1/2 or less of the total users, and if one server goes down, the other server can take over the entire workload seamlessly. ![]() To maximize performance and reliability, MirrorSync can be used in a clustering configuration, where two or more servers are running at the same data center and synchronized so that they all contain the same set of data. In this configuration, MirrorSync should be set to sync very often, such as every 30-60 seconds.Ĥ. Each workgroup works at full LAN speed on their own FileMaker Server, and MirrorSync takes care of keeping the servers in sync with each other, so that each workgroup can see and edit changes made by the other group. For groups of users at multiple locations, MirrorSync should be used in server-to-server mode, where an identical copy of the database is installed on FileMaker Server in each location. The user could sync when they first came into the office, work on their local copy throughout the day, and sync at specified times (or on demand) to push and pull the latest data to the server.ģ. MirrorSync allows each user to take a local copy of the database which would run on the user's machine and not be affected by the WAN performance. If, for example, you have multiple users connecting to FileMaker Server over a wide area network (WAN) you could notice a substantial slowdown, as every change is immediately written back to FileMaker Server. For remote users who work on laptops, MirrorSync solves the problem of how to work productively on a hosted FileMaker database, regardless of network speed. ![]() Depending on their workflow, they could even specify a one-way sync where their information is pushed to the server, but no data is pulled down, or vice versa for users who need fast read-only information.Ģ. Each user can take a local copy on their iPad or iPhone, input the information from the field, and then sync when they regain a network connection. For mobile users who access the database with FileMaker Go on their iOS device, MirrorSync allows these users to work efficiently with limited or no connectivity to the server network. It is not a plug-in, and does not require any software installation on client devices.ġ. MirrorSync is only installed on the server computer. For servers, MirrorSync allows a database to run in multiple locations, or to integrate different databases and make sure that changes to each server are reflected in the other server. For mobile devices, users can sync the hosted file with their FMGo or Pro clients, go off network to make changes, and sync again when a connection is available. MirrorSync is an elegant synchronization product that can sync between any combination of FileMaker Pro, FileMaker Go, FileMaker Server, SQL database (MySQL, Oracle, SQL Server, or any database that supports JDBC), Salesforce, Amazon DynamoDB, and Amazon RedShift. No network? No problem! Sync between any combination of FileMaker Go or Pro, FileMaker Server, WordPress, Salesforce, or AWS
0 Comments
Leave a Reply. |