Do you want to request a feature or report a bug?
Bug
What is the current behavior?
This .gitignore of your sample app contains the complete amplify folder including critical files like project-config.json. This prevents the app to be built successfully on the cloud where the amplify folder isn't present.
It seems to me this folder is necessary because, according to your official Getting Started guide, the project build settings should also contain a backend build-step like
`backend:
phases:
build:
commands:
'# Execute Amplify CLI with the helper script'
amplifyPush --simple`
amplifyPush --simple in the cloud errors out when the folder amplify and it's contents are not present.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Deploy this application to the Amplify console. In my case I have used AWS CodeCommit as the source directory, but that won't make a difference. On the UI connect backend with frontend. Add above mentioned build step to 'Build Settings' on Amplify Console. Trigger a build. Build will fail with the message
Importing Amplify environment: master (amplify env import) 2020-10-15T08:05:58.784Z [WARNING]: /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13 throw up; ^ Error: You are not working inside a valid amplify project.
Which implies some file/folder is not present.
Will probably fix it: Remove lines 1-6 from .gitignore
Do you want to request a feature or report a bug? Bug
What is the current behavior? This .gitignore of your sample app contains the complete
amplifyfolder including critical files likeproject-config.json. This prevents the app to be built successfully on the cloud where theamplifyfolder isn't present. It seems to me this folder is necessary because, according to your official Getting Started guide, the project build settings should also contain a backend build-step like`backend: phases: build: commands:
amplifyPush --simplein the cloud errors out when the folderamplifyand it's contents are not present.If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Deploy this application to the Amplify console. In my case I have used AWS CodeCommit as the source directory, but that won't make a difference. On the UI connect backend with frontend. Add above mentioned build step to 'Build Settings' on Amplify Console. Trigger a build. Build will fail with the message
Importing Amplify environment: master (amplify env import) 2020-10-15T08:05:58.784Z [WARNING]: /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13 throw up; ^ Error: You are not working inside a valid amplify project.Which implies some file/folder is not present.
Will probably fix it: Remove lines 1-6 from .gitignore