Spawn codiad container for existing projects about docker-codiad HOT 6 CLOSED

I'm not sure I understand what the issue is. I haven't used this container, but can't you simply browse to the mounted volume and open your existing project?

from docker-codiad.

@tobbenb the only mountabe volume is 'config'. There is no easy way to mount existing projects.

from docker-codiad.

You can mount what you want. Just use the -v option when you create the container.
In codiad you can browse through the the mount point you chose.

from docker-codiad.

The way I understand it - after mounting a folder you'll still need to create a codiad project and then inspect data/projects.php file to see how the pathing is laid out and modify that php file manually. Or replace the project folder created with codiad with a symlink to your own folder. However if you have multiple projects this quickly becomes painful.

from docker-codiad.

I played with codiad a little now and see what you mean. But I don't really see how to make this a one solution fits all.
You either have to copy the files into the correct folders inside /config or edit the config.php.
Might be better to ask the codiad developers to make an easy export/import function. Might even be a plugin for that already.
I see you can import from a git repo when creating a new project, so that might be the best option.

from docker-codiad.

Agree, ideally codiad would support this better.
This docker container here perhaps could simply start with a pre-configured project where the project folder is a volume that can optionally be mapped to a container folder?
The just-spawn-and-go short setup instructions would make it very attractive for codiad newbies.

from docker-codiad.