Development Training Resources

• Related Articles

• Development Best Practices

  Development Best Practices Code Review Checklist Code Review Checklist Subversion Best Practices Branches Always put in comments when checking into subversion Create one branch per task Name branch with Redmine task number and short description (Ex. ...

• Development Environments

  We have four main development environments. They are local, development, test, and production. Our local and development environments both provide places for the development team to test their code changes before they are complete. Our test ...

• Reading List / Training for Customer Portal

  Front-end Electron Electron Documentation - Starting page for official electron documentation. Sample apps for Electron - Example applications to illustrate the usage of Electron APIs. electron-builder - Tool for packaging and creating installers for ...

• Outlooks Rules for Development Team

  Outlooks Rules for Development Team Here are a list of Outlook rules that can be set up to help organize the inbox of the development team. Prometheus Alerts – Sender is alertmanager@fullcount.net Applications Alerts - Sender is alerts@fullcount.net ...

• Redmine Development Task Workflow - New Community Instance

  Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, Assignee of Development, and New Community Instance template. A member of the development team will check for new tasks under the development project as ...