Best Practices for Wrangler Example
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- cloud
Research direction
Start by inspecting the existing wrangler.toml and repository ignore configuration. Create an example.wrangler.toml with the needed structure and ensure the account-specific wrangler.toml is ignored; done means the example is committed without exposing account configuration.
Written by the indexing model from the issue text.
Description
Your cloudflare account is still in the wrangler, which it probably should not be :P
We should probably put wrangler.toml in .gitignore and instead make a example.wrangler.toml file with the proper structure for people to reference.
I can do this later if you remind me 😉
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solidjs/solid-service-api
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in solidjs/solid-service-api
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·