Connect to Development Server
This guide helps setup the one-time connection between Devin App and Devin Engine.
Last updated
Was this helpful?
This guide helps setup the one-time connection between Devin App and Devin Engine.
Last updated
Was this helpful?
Install Devin Server on a dedicated Development server and read the Network Considerations before continuing.
Enter the URL of your Development Server to connect to the Devin Engine (see About the Devin Engine).
If the connection to the Devin Engine isn’t verified, such as if FileMaker Pro on your computer has not connected to this server before, FileMaker Pro will block access. This prevents the Devin App from connecting to the Devin Engine.
When prompted for allowing the connection, select Always permit connection to this host and click Connect. This setting prevents the need to grant permission each time FileMaker Pro restarts.
If FileMaker Pro asks you to log in to view hosted files on this server, you can skip it. Just click Cancel on the login prompt and then Cancel on the Hosts window. After that, return to the Devin App and retry the connection to Devin Engine.
The Devin Engine is an fmp12 file that’s automatically installed on your Development Server. It stores all project and server metadata, so nothing lives locally and everyone on your team can access it. It also serves as both the database and the routing layer for communication between the Devin App and Devin Server APIs.
Devin App connects to the Devin Engine via FileMaker’s default External Data Source protocol — FMNET (port 5003) by default, and HTTPS (port 443) if HTTPS tunneling is enabled. To use custom FMNET or HTTPS ports, click the Advanced popover button in the connection dialog.
