If you are looking to enable this in a legacy Stingray project, here is the high-level process:
Stingray, in conjunction with Perforce, offers a powerful solution for software development teams seeking to optimize their version control workflows. By providing a native Perforce experience, Stingray enables developers to work more efficiently, collaborate more effectively, and deliver high-quality software products. Whether you're a seasoned Perforce user or just starting to explore the world of version control, Stingray is an excellent choice for unlocking the full potential of Perforce. stingray perforce full
For game development, "Stingray Full" wins. For plain text source code, Git LFS is sufficient. If you are looking to enable this in
Uses a Model-View-Controller (MVC) architecture and is fully integrated with the MFC document/view framework. For game development, "Stingray Full" wins
"name": "Suspicious large sync", "condition": "action == 'sync' AND total_file_size_mb > 500", "window_minutes": 5, "severity": "HIGH", "actions": [ "type": "email", "to": "security@company.com" , "type": "webhook", "url": "https://my-siem.com/event" ]
Stingray can write logs to storage or a separate, immutable database, meeting legal discovery requirements.
Even with the "Full" setup, there were headaches: