Author Archives: Dinis Cruz

About Dinis Cruz

Dinis Cruz is the main developer of the OWASP O2 Platform and TeamMentor

Beginning Development on Team Mentor

Originally posted on Code Clueless:
Installed Git, cloned the Master source code repository and loaded some XML data with help from Kofi Sarfo. I’m really liking the rawness of the app. For example, when editing a user, there’s a JSON representation…

Posted in Uncategorized | Leave a comment

On TeamMentor’s Event-Driven architecture

Following Arvind’s questions at Studying TM architecture I just replied at TeamMentor’s Javascript-based Event Driven Architecture

Posted in Architecture, JQuery | Leave a comment

Pulling a Code update into TM Documentation Repository

This PDF shows how to Pull a Code update into TM Documentation  Couple notes: Both repositories are syncronized, but have different content TeamMentor/Master is the ‘master’ code base with it s changes propagated into other repositories TeamMentor/TeamMentor-Documentation contains the code from … Continue reading

Posted in Uncategorized | Leave a comment

TeamMentor 3.2 ‘Pinned Filters’ feature

This video show the new TM 3.2 capability to lock down filters (via the top-left filters list and the URL)

Continue reading

Video | Posted on | Leave a comment

Updating TM Documentation Repository with 3.2 version

Here is a PDF on how I just Updated TM Documentation Repository with 3.2 version To make changes to this repositories, create a fork of the repository and if you want to submit changes send in pull requests

Posted in Uncategorized | Tagged | Leave a comment

Syncing TM Documentation with its GitHub repository

Here is a PDF with how I just  Synced TM Documentation with its GitHub repository This also shows a workflow for the cases where changes made to a TM site need to be ‘pushed back’ into the original repository (note … Continue reading

Posted in Uncategorized | Tagged | Leave a comment

Creating a Code+Content version of TeamMentor

The current TeamMentor code/deployment set-up is based on the concept that Code (the app) and Content (the libraries) should be separated (with everything hosted on GitHub)  In practice this means that we will need 3 GitHub repositories: one for the … Continue reading

Posted in Uncategorized | Tagged , , | Leave a comment