-
Notifications
You must be signed in to change notification settings - Fork 18
Spawn codiad container for existing projects #10
Comments
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? |
@tobbenb the only mountabe volume is 'config'. There is no easy way to mount existing projects. |
You can mount what you want. Just use the -v option when you create the container. |
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. |
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. |
Agree, ideally codiad would support this better. |
This beautiful lightweight ide wrapped into a docker container doesn't easily adapt to an existing dev infrastructure. It is missing an easy way to spawn a docker-codiad container to manage existing projects. This should be as easy as mounting an existing projects folder as docker volume.
Is there a reason why this wasn't considered? Or am I missing something? Seems to be the natural thing
to do for a docker container. Would it be easy easy to add?
Peter
The text was updated successfully, but these errors were encountered: