-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
captain-definition file is not a valid JSON! #134
Comments
For those of you who don't want to download and extract the contents of the zip file, I've done this in a sandbox and provide the content of the captain-definition contained within:
The contents of the file include CRLF Windows formatted return lines. The file needs to have these changed to normal line feed, or just LF. This would be denoted as a \n or would appear as LF in some editors. |
How are you attempting to deploy your app? |
Byte Order Marked files have crept up periodically in the last 25+ years of my software development experience. Often, they appear after the corrupt file transfers over FTP or going between Mac and PC. I've also seen them created out of thin air by editing an existing file in Nodepad.exe in Windows. Super annoying. I'm glad it's solved. |
Now that you mention Windows Notepad.exe, I saw when the developer create the captain-definition file and, guest what? He use it to created the file. Please add a warning on the documentation that don't create or edit the files with Windows Notepad. Thanks so much for your help @maietta |
What is the problem?
When trying to deploy app via CLI, no matter all the format fixes we try, caprover cli keeps saying the definition file is not a valid Json
Steps to reproduce the problem:
Just try to run the command over the attached file on zip
caprover deploy
Windows 11
Caprover Cli Version 2.2.3
Node Version v18.14.0
Output of the following command on your server:
captain-definition.zip
The text was updated successfully, but these errors were encountered: