You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example SOC II Type I policy types needed for an early-stage startup (you need to actually fill these in yourself)
Purpose:
To ensure responsible use of company-provided systems, devices, and data.
Policy:
Use of company resources should be for business purposes only. Use that introduces risk (e.g., file sharing of sensitive data via unapproved platforms) is prohibited.
nstead of showing country codes (ie US, CH, NL), show the flag emojis, 🇺🇸 🇨🇭 and 🇳🇱
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
Bash script to build a docker image, tag it, push to ECR, and deploy to ECS
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
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
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
Loopback v3.x boot script to automatically update schemas for any datasources that have models connected to them.
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
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
Cheatsheet for creating LoopbackJS relationships using the PostgreSQL connector
This is my cheatsheet, because the Loopback docs aren't the best and I spent way too long puzzling this stuff out.
Consider this a living document. If it helps you, too... great! If you want to make a suggestion, lmk.
First... the why.
It's a PostgreSQL best-practice to use lowercase names, using snakecase if you need to. ie, my_column_name. You CAN force CamelCase or all uppercase, but it's a really bad idea. Don't.
Also, since I'm using a JSON API client, I've installed the excellentloopback-component-jsonapi to handle the serialization stuff... but that just added additional complexities.
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
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