Feature Requests

・Permissions to release and deploy on a project basis. ・If the above permissions are not granted, the status can be changed to "Release Request Pending." The status change to "Release Request Pending" and cancellation can be done regardless of whether the permissions are granted.

Occasionally it is essential to have the users data when reproducing the steps they are taking to see their problem. If there was a way to migrate data from a production file - or a backup - it would eliminate the need to use the production files to identify the issue.

Can the Devin App be ran on Windows? I see the request for Windows Server support (which I upvoted), but can the app be ported to Windows? I love the idea of this project!

Getting a version of Devin that works in a non-internet-connected environment, both for Prod and Dev servers (anonymous request).

Since Devin commits are not built upon one another as Git is, modifying past commits is as simple as modifying fields in the Devin commits table, or changing the clone in /opt/Devin/commits Commits can be saved as full-backups, that can be nice for reverting while keeping the necessary development/base record data The thing is, as the commit tree gets larger, the usefulness of having saved a full-backup commit is offset by the storage it takes up I'd like to be able to: commit --amend - Modify the version tag and commit description Convert full-backup commits to clones An ideal extra feature is also to be able to edit the FileMaker solution itself: Copy commit file into fms databases directory and open for editing Override stored commit when amend confirmed, and remove from the databases

"By default, the Data Migration Tool sets the target file locale to the system on which the migration happens. However, the data migration tool actually does support specifying a locale as a CLI flag" Since modules are their own solutions and code can break when running on the wrong locale, Devin should allow configuration of the module's locale (Perhaps also recognize it automatically), and retain it between clones and migrations For example: A solution of mine was created with the en_IL locale, but my Devin server was using en_US.UTF-8 After migration, when running in a calculation context, Date functions were formatted as MM/DD/YYYY instead of DD/MM/YYYY You can imagine the chaos

Ability to implement a Devin log API into our test or production scripts. Log levels could include INFO, TRACE, DEBUG, ERROR, FATAL etc. The idea is that these logs would appear in a separate tab in the Runner window for a real time view of errors on client files etc. For test scripts, this would allow easier debugging. For production logging, it would allow a realtime logging monitoring of all our prod files.

Ability to link commits to jira tickets

Show metrics like current and historic CPU, Memory, Network and Storage usage directly in the Monitor window.