Amplify-cli: changed laptops and amplify won’t recognise existing project

[dagda1]

I have changed laptops recently and when I run

amplify publish -c

I get this error:

Error: You are not working inside a valid amplify project.
Use 'amplify init' in the root of your app directory to initialize your project with Amplify

I created an aws cloudfront through amplify previously but is it possible to reinitialise amplify on a new machine.

i committed all files to source control so i can’t understand from the error message what is missing

[kaustavghosh06]

@dagda1 When you changed laptops did you run the amplify configure project command from the root of your project? If not, then please run that and then execute the subsequent commands.

[dagda1]

i have done this but all it did was create s new iam role. then when j try and publish i get the same error message

[kaustavghosh06]

@dagda1 That would be the amplify configure command. I was referring to the amplify configure project command.

[dagda1]

@kateglee I get the same message from amplify configure project

[dagda1]

Looking at the code:

function getProjectConfigFilePath(projectPath) {
  return path.normalize(path.join(
    getDotConfigDirPath(projectPath),
    amplifyCLIConstants.ProjectConfigFileName,
  ));
}

What is it looking for that it cannot find in getDotConfigDirPath(projectPath)

I have a amplify folder which has a backend folder with these child folders

amplify-meta.json awscloudformation/ hosting/

and in fact projectPath is undefined.

[dagda1]

so there is no .amplify folder. This is a hidden folder which is probably why it has not been persisted across my change of laptop.

WHat can I do to reconfigure without starting afresh. I have cloudfront and route53 etc. set up for many months and I'd hate to have to do all that again, never mind a DNS change.

[dagda1]

anybody help me with this. Is my amplify toast?

[kaustavghosh06]

@dagda1 What does your project structure look like? Do you see the amplify sub-directory in your app/project directory?

[dagda1]

@kaustavghosh06 here is what tree outputs

.
├── LICENSE
├── README.md
├── amplify
│   └── backend
│       ├── amplify-meta.json
│       ├── awscloudformation
│       │   └── nested-cloudformation-stack.yml
│       └── hosting
│           └── S3AndCloudFront
│               └── template.json
├── data

[kaustavghosh06]

Can you run the amplify status command from the root of your project?
Also which system are you using currently? and what's the version of the CLI that you're using?

[dagda1]

It is the same error every time

Error: You are not working inside a valid amplify project.

I've checked the code as I mentioned above, when amplify runs it looks for a hidden .amplify directory which does not exist because it did not survive my move to a new laptop.

If the directory does not exist then the error gets displayed

[kaustavghosh06]

@dagda1 We don't create a .amplify dir but create a amplify/.config directory which seems to be missing in your case. Would it be possible to retreive the amplify/.config directory?

[dagda1]

@kaustavghosh06 no, I think the fact that it is a hidden folder means it did not come across.

Is there anything else I can do?

[kaustavghosh06]

Which version of the CLI were you using? the one in mainline or @multienv? I can help you rebuild your .config folder manually.

[dagda1]

oh man, thank you so much.

I am on 0.1.45

[kaustavghosh06]

Here's the .config folder structure:
amplify
|_.config
|_aws-info.json
|_project-config.json

Here's a sample of these above mentioned config files. Plase fill/substitue it with your custom information.

aws-info.json

{
    "configLevel": "project",
    "useProfile": true,
    "profileName": "default"
}

project-config.json

{
    "projectName": "testbeta",
    "projectPath": "/Users/kaustavg/testbeta",
    "defaultEditor": "sublime",
    "frontendHandler": {
        "javascript": "amplify-frontend-javascript"
    },
    "javascript": {
        "framework": "none",
        "config": {
            "SourceDir": "src",
            "DistributionDir": "dist",
            "BuildCommand": "npm run-script build",
            "StartCommand": "npm run-script start"
        }
    },
    "providers": {
        "awscloudformation": "amplify-provider-awscloudformation"
    }
}

You can run amplify configure project command to modify any of these values int he future.

[dagda1]

brilliant, thank youi