-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add Render as deploy Option 4 #319
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
Merged
+47
−2
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
410d093
Add Render deploy option alongside Netlify, Vercel, and Docker.
ojusave 7a9bfb3
Clarify Render deploy uses this fork Blueprint, not upstream.
ojusave 85e0908
Simplify Render deploy: one gallery button, no Apply-time API key pro…
ojusave c3943c6
Reorder deploy options: Render as #4, From Source as #5.
ojusave 29b0dd6
Use :latest image and point Deploy button at this repo.
ojusave 0f4ce0e
Merge branch 'lissy93:master' into master
ojusave 47e1fa5
Fixes formatting error in render.yaml
lissy93 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| # yaml-language-server: $schema=https://render.com/schema/render.yaml.json | ||
| # | ||
| # Web Check on Render — Blueprint deploy | ||
| # Upstream: https://github.com/Lissy93/web-check | ||
| # Image: https://hub.docker.com/r/lissy93/web-check | ||
| # | ||
| # Pattern: image-wrapper (official lissy93/web-check image with Chromium). | ||
| # Optional OSINT API keys: add in Dashboard after deploy (see .env.sample). Do not | ||
| # declare them as sync:false here or Apply will prompt for every key. | ||
|
|
||
| previews: | ||
| generation: off | ||
|
|
||
| services: | ||
| - type: web | ||
| name: web-check | ||
| runtime: image | ||
| plan: standard | ||
| region: oregon | ||
| image: | ||
| url: docker.io/lissy93/web-check:latest | ||
| healthCheckPath: / | ||
| autoDeployTrigger: off | ||
| envVars: | ||
| - key: PORT | ||
| value: '3000' | ||
| - key: TRUST_PROXY | ||
| value: '1' | ||
| - key: CHROME_PATH | ||
| value: '/usr/bin/chromium' | ||
| - key: PUPPETEER_EXECUTABLE_PATH | ||
| value: '/usr/bin/chromium' | ||
| - key: PUPPETEER_SKIP_DOWNLOAD | ||
| value: 'true' | ||
| - key: API_ENABLE_RATE_LIMIT | ||
| value: 'true' | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Does render not have ability to declare them here, and have them filled in when the user clicks deploy? I only ask, since I think I've seen something similar done elsewhere.
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.
It can (sync: false), but then Apply asks for every key even when they're optional. Left them for the dashboard after so the deploy stays quick. Happy to add a couple of the common ones if you'd rather.