How do I create a project?

[clov3r]

This is a dumb question... but I can't mapToRemote without creating a project. How do I create a project? I have open the folder that I want to map...

[vahidvalian]

I have this problem too

[Mathahal]

I'm also in this situation.

[orlaqp]

I am having the same issue .. I also downloaded the Project Manager package and save the project but still getting the same message "Create a project before ..."

[clov3r]

Huh, glad it's not just me.

Atom 0.182.0, without project manager, project-ring or any other project manager package installed.

[orlaqp]

I could really use this feature but not sure what to do to make it work and at this point do not have time to look at the package source code. In the meantime I am still using FileZilla Client.

[akyoto]

I have the same problem. How do I create a project for sftp-deployment? I was thinking maybe it needs the Project Manager package but after creating a project there it still didn't change anything.

[xabispacebiker]

same here

[chantelope]

Also having this issue

[SharpEdgeMarshall]

same here!!!

[misterGF]

+1

[raugaral]

the same in Atom 0.184.0

[iamstarkov]

wtf is the project in atom without projects support?

[aary]

I can't seem to work around it either. Does anyone know how to fix this?

[reggi]

+1 this is madness

[reggi]

I dug into the DeploymentManager.js specifically this line which is throwing the Create a project before trying to create a config file. error.

By "project" the package requires that you have a folder opened with atom, and not just a file.

console.log(atom)
console.log(atom.project)
console.log(atom.project.path)

Of course atom.project.path is undefined. I did a find and replace for it and got the "MapToRemote" by doing a find and replace for atom.project.path and replacing it with atom.project.rootDirectories[0].path all that function did was create a file in my root directory called deployment-config.json but the app crapped out when I tried to upload.

The plugin doesn't seem to offer directory watching anyway :(

[Pooky]

I find quick fix. At DeploymentManager.js after line 15 put this code and it should work.

// Quick fix
if(atom.appVersion.split(".")[1] > 182){
  atom.project.path = atom.project.rootDirectories[0].path;
}

[Cipa]

Many thx to @Pooky

[alanhouser]

I concure; thanks @Pooky. BTW: at first the fix didn't work. I had to restart Atom. Bingo.

[Pooky]

@alanhouser You don't have to restart whole atom, you can reload your view by VIEW->RELOAD in menu :)

[amoussard]

Hi guys,

Sorry for the long period of inactivity.

We are currently working on a new version : better code, more stable, and bug fixes. This bug will be fixed at the next release.

Thank you for using our work ! :)

[amoussard]

Hi guys,

A new version (1.0.0) was published tonight. Feel free to reopen if the problem is still there.

Enjoy ! :D