Throw error when ssl required?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 271
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Ley wasn't outputting anything, but would just stop when running `ley up`. I finally figured out I needed to add:
```js
// ley.config.js
export default { ssl: true }
```
Any way you could provide the error in the console?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the issue by running `ley up` without the `ssl` setting, then compare it with a `ley.config.js` containing `export default { ssl: true }`. Trace the `ley up` entry point to find where execution stops, and consider the issue done when the missing SSL requirement produces a console error instead of exiting silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100