deploy-to-sfdx
deploy-to-sfdx copied to clipboard
ENOENT: 'config/project-scratch-def.json'.
Hi, Just got this error when installing on my Trial Dev Hub. Was asked to log an issue here... Thanks Fab
GUID: b016c28d-8ad2-83ff-8581-41dc99816b9b ERROR: ENOENT: no such file or directory, open 'config/project-scratch-def.json'.
- GUID: b016c28d-8ad2-83ff-8581-41dc99816b9b ERROR: ENOENT: no such file or directory, open 'config/project-scratch-def.json'.
- Set instance url to https://eu9.salesforce.com.
- Successfully cloned https://github.com/wadewegner/deploy-to-sfdx.
- No .salesforcedx.yaml found in repository. Using defaults.
Just being curious, from which repo did you try to deploy ?
from https://deploy-to-sfdx.com/... the BIG blue button...
Oh ok I understand. This button only works if the repo has a correct .salesforcedx.yaml file setup. Give it a try here: https://github.com/dreamforce17/purealoe
You can look to the setup file in the repo it's pretty straightforward, or have a look to the doc here: https://deploy-to-sfdx.com/repo
I think here it's not working because the site seems to take the previous page as a parameter, and acts like if it was the repo you want to deploy. Try to write the url yourself in a new tab, and you should see a list of the last repos deployed successfully.
Thanks for the explanation and, yes, I should have read the *@# manual!
You can close.
I'll keep it open as I think it should be made more obvious that we are not clicking on the link from a repo.
@fcathala @FabienTaillon Sorry, where's the big blue button on this repo?
@wadewegner Actually the issue is if you access to deploy-to-sfdx.com from another page than a repo.
The app will either take the url in the template
url parameter, or if it’s missing, the url we’re coming from.
So if I tell you: you should try to use https://deploy-to-sfdx.com, you will click on the link and it will try to deploy this page (https://github.com/wadewegner/deploy-to-sfdx/issues/31) even though it’s not a real repo. It’s confusing because as a user you just tried to access an url, not to deploy a repo.
The easiest way would be to make the template
url parameter mandatory, or it should be clearer that we’re trying to deploy something (maybe checking that there is a salesforcedx.yaml file before trying to deploy).