Skip to content

set default user via env vars - #342

Merged
pashidlos merged 2 commits into
Visual-Regression-Tracker:masterfrom
adabru:master
Jul 28, 2026
Merged

set default user via env vars#342
pashidlos merged 2 commits into
Visual-Regression-Tracker:masterfrom
adabru:master

Conversation

@adabru

@adabru adabru commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

Make the values

DEFAULT_USER_EMAIL=visual-regression-tracker@example.com
DEFAULT_USER_PASSWORD=123456
DEFAULT_USER_API_KEY=DEFAULTUSERAPIKEYTOBECHANGED

configurable via .env.

I think it's a security issue to have the default user created with default values. Without changing it from the start, I would need to locally change the credentials before I open up the server.

Related issues: Visual-Regression-Tracker/Visual-Regression-Tracker#114, #273 (comment)

@monotek @Thanoonazad

Related PR: Visual-Regression-Tracker/Visual-Regression-Tracker#476

@pashidlos
pashidlos self-requested a review July 28, 2026 19:32
@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@pashidlos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a4b12950-29f7-4081-a3e0-4c0740972ed9

📥 Commits

Reviewing files that changed from the base of the PR and between e583e5a and 6fb639c.

📒 Files selected for processing (3)
  • .env
  • docker-compose.yml
  • prisma/seed.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@pashidlos pashidlos left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

@pashidlos
pashidlos merged commit 190e17c into Visual-Regression-Tracker:master Jul 28, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants