- Mirth Connect to be installed locally
- VSCode task set up with paths pointed to the local Mirth instance (provided file are for default Windows locations)
vs_mirth.jsshould be placed in the location specified in line 14 of the build task (arg 4)- Executed file has to be based on a saved file NOTE: Changes don't have to be saved to execute as the build task will save the file if needed.
win3zz
/ GitHub-Leaked-API-Keys-and-Secrets.md
Last active
November 3, 2025 21:30
As a security professional, it is important to conduct a thorough reconnaissance. With the increasing use of APIs nowadays, it has become paramount to keep access tokens and other API-related secrets secure in order to prevent leaks. However, despite technological advances, human error remains a factor, and many developers still unknowingly hardcode their API secrets into source code and commit them to public repositories. GitHub, being a widely popular platform for public code repositories, may inadvertently host such leaked secrets. To help identify these vulnerabilities, I have created a comprehensive search list using powerful search syntax that enables the search of thousands of leaked keys and secrets in a single search.
(path:*.{File_extension1} OR path:*.{File_extension-N}) AND ({Keyname1} OR {Keyname-N}) AND (({Signature/pattern1} OR {Signature/pattern-N}) AND ({PlatformTag1} OR {PlatformTag-N}))
**1.
davestewart
/ estimation.md
Last active
September 18, 2025 07:31
This document is an attempt to pin down all the things you don't think about when quoting for a project, and hopefully provide a starting point for some kind of framework to make quoting, working and delivering small-medium jobs more predictable and less stressful.
wojteklu
/ clean_code.md
Last active
November 3, 2025 03:19
Summary of 'Clean code' by Robert C. Martin
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| alias.a add . | |
| alias.aliases config --get-regexp alias | |
| alias.bi bisect | |
| alias.ci commit -m | |
| alias.co checkout | |
| alias.colast checkout - | |
| alias.db branch -D | |
| alias.laf fsck --lost-found | |
| alias.last log -1 HEAD | |
| alias.nb checkout -b |
n3dst4
/ renaming.markdown
Last active
January 13, 2025 16:46
How to rename Visual Studio solutions and projects
- Don't.
- Close Visual Studio and don't open it again until I tell you. Visual Studio is not competent at renaming things.
- Assuming you're using git, clean the working folder to remove anything that's not in version control (this will help the search-and-replace step because it won't have to go through a bunch of generated files)
git clean -fdx
PurpleBooth
/ README-Template.md
Last active
November 3, 2025 11:24
A template to make good README.md