πŸ™οΈA Modern Workflow

By following these steps, teams can leverage Devin to enhance their FileMaker application development lifecycle, from initial development through to deployment and update rollouts, in a structured and efficient manner:

  1. Create a Project:

    • Initiate a new project for each client or project that you are working on. This serves as a container for your application's lifecycle, including development, testing, deployment, migrations and monitoring stages.

  2. Add Team Members to the Project:

    • Invite collaborators to your project to facilitate a collaborative development environment.

  3. Add Modules (fmp12 files) to the Project:

    • Add one or multiple FileMaker Pro 12 (.fmp12) files to the project as modules.

  4. Create a Development Branch:

    • Branching enables team members to work on features, fixes, or enhancements in isolation, without affecting the mainline or each other’s work until they're ready to release into main.

    • Start off by creating a branch for development off of the main branch. Now you and your team can use this for all development. Then, if someone wants to test or work on something that should not affect the others' work, another branch can be created off of the development branch, and so on.

    • A current limitation is that branches cannot be merged. This will become a future feature, but currently, if multiple developers have made changes on separate branches, they must agree on a single branch to be the truth for what will be released back to the main branch.

  5. Create New Versions and Track Changes Between Them:

    • As development progresses, save versions of your development files. Document and track changes made in each version to maintain a clear history of development. This practice is crucial for understanding the evolution of your application and troubleshooting issues.

  6. Release Back into Main, with a Full Overview of Your Changes:

    • Once development and testing of changes in branches are complete and verified, release these changes back into the main branch. Provide comprehensive documentation of the changes to maintain transparency and ease the integration process. This overview is vital for assessing the impact of the new features or fixes.

  7. Automatically Deploy and Migrate the New Main Version to Your Staging or Production Servers:

    • Utilize Devin's capabilities to automate the deployment of the updated main version of your fmp12 files to staging or production environments. This step ensures that your application is consistently and safely deployed across your servers, reducing manual errors and speeding up the delivery of new features or fixes to end-users. Data Migrations are 100% Automated.

Last updated