Skip to content

Add Render as deploy Option 4 - #319

Merged
lissy93 merged 7 commits into
lissy93:masterfrom
ojusave:master
Jul 31, 2026
Merged

Add Render as deploy Option 4#319
lissy93 merged 7 commits into
lissy93:masterfrom
ojusave:master

Conversation

@ojusave

@ojusave ojusave commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds Render as Deployment Option 4 (From Source moves to Option 5)
  • Adds a root render.yaml Blueprint using the official lissy93/web-check image
  • Deploy button points at the gallery template render-examples/web-check-render-template

Closes #318

Notes

  • Optional enrichment API keys are intentionally not declared as sync: false in the Blueprint, so Apply does not prompt for them. They can be set in the dashboard after deploy if needed.
  • Service uses Standard plan (Chromium / Puppeteer needs a bit more than free-tier defaults).

Test plan

  • Confirm Deploy to Render button opens the gallery template flow
  • Apply Blueprint / template and reach a healthy service on /
  • Confirm no optional OSINT API keys are required at Apply time
  • Spot-check README TOC anchors for Option 4 (Render) and Option 5 (From Source)

ojusave added 4 commits July 14, 2026 18:22
Includes a Blueprint render.yaml using the official lissy93/web-check image so one-click deploy works from this fork.
Upstream may not include render.yaml yet; point to the gallery template as well.
…mpts.

Optional enrichment keys belong in the Dashboard after deploy, not sync:false in the Blueprint.
@netlify

netlify Bot commented Jul 15, 2026

Copy link
Copy Markdown

Deploy Preview for web-check ready!

Name Link
🔨 Latest commit 47e1fa5
🔍 Latest deploy log https://app.netlify.com/projects/web-check/deploys/6a6c71de350147000814f7f8
😎 Deploy Preview https://deploy-preview-319--web-check.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@ojusave
ojusave marked this pull request as ready for review July 15, 2026 01:45

@lissy93 lissy93 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, overall. But the image version is old. And can you confirm that this did actually work for you with those options? And that the link is correct

Comment thread render.yaml Outdated
plan: standard
region: oregon
image:
url: docker.io/lissy93/web-check:2.1.10

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we put this as :latest, it should always get updates

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, switched it to :latest.

Comment thread render.yaml Outdated
Comment on lines +29 to +30
- key: CHROME_PATH
value: "/usr/bin/chromium"

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually not sure that this will work, on render? But I could be wrong. Did you get it working with that path?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it works. Same path the image already sets internally, and screenshots came through on the deploy.

Comment thread .github/README.md Outdated

Click the button below, to deploy to Render 👇

[![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy-template/api/github/start?template_repo=web-check-render-template)

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the right link though? I'd of thought it would need to point to this repo

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated. Button now goes to render.com/deploy?repo=https://github.com/Lissy93/web-check so it deploys from this repo.

Comment thread render.yaml Outdated
Comment on lines +35 to +36
- key: API_ENABLE_RATE_LIMIT
value: "true"

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This wouldn't work on render, you won't have the right headers I don't think. Since the X-Forwarded-For header will be the render IP, not clients.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be alright with TRUST_PROXY=1. That's what makes Express pick up the real client IP from X-Forwarded-For instead of Render's.

Comment thread render.yaml
Comment on lines +8 to +9
# 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.

Copy link
Copy Markdown
Owner

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.

Copy link
Copy Markdown
Contributor Author

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.

@ojusave

ojusave commented Jul 31, 2026

Copy link
Copy Markdown
Contributor Author

Pushed a couple updates:

Image → :latest
Deploy button now points at this repo (render.com/deploy?repo=…)
Re: the other bits: Chromium path works on Render (same path the image already ships with). Rate limit is fine with TRUST_PROXY=1. Left the optional API keys out of Apply on purpose so it doesn’t prompt for a pile of blanks. Live instance still up at https://web-check-n02a.onrender.com/check

@lissy93
lissy93 merged commit 7ccdad9 into lissy93:master Jul 31, 2026
11 of 12 checks passed
@liss-bot

This comment was marked as low quality.

@liss-bot liss-bot added ✅ Fixed 🛩️ Released 2.2.2 Included in release v2.2.2 labels Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✅ Fixed 🛩️ Released 2.2.2 Included in release v2.2.2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Add Render as a one-click deploy option

3 participants