-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Pages]: Add binding instructions to remix sites #5120
Conversation
Deploying with
|
Latest commit: |
8aa2397
|
Status: | ✅ Deploy successful! |
Preview URL: | https://6f5374c5.cloudflare-docs-7ou.pages.dev |
Branch Preview URL: | https://update-remix-doc.cloudflare-docs-7ou.pages.dev |
Can we get an example on how to use the bindings? That's what brought up the initial ticket. these frameworks all have their own ways to use it and we should document it in here |
Co-authored-by: Kate Tungusova <[email protected]>
Co-authored-by: Daniel Walsh <[email protected]>
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
4092891 | Generic High Entropy Secret | a27daa1 | config.toml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Needs a DO code example.
- Has to be clear on where the binding code goes in Remix directory.
Co-authored-by: Greg Brimble <[email protected]> Co-authored-by: Kate Tungusova <[email protected]>
Co-authored-by: Greg Brimble <[email protected]>
PCX and Greg Co-authored-by: Greg Brimble <[email protected]>
add links
add aside back
This PR updates adding bindings instructions for Remix projects. Addresses #5094