Skip to content
This repository has been archived by the owner on Jun 12, 2019. It is now read-only.

Spawn codiad container for existing projects #10

Closed
peter-hartmann opened this issue Dec 28, 2017 · 6 comments
Closed

Spawn codiad container for existing projects #10

peter-hartmann opened this issue Dec 28, 2017 · 6 comments

Comments

@peter-hartmann
Copy link

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

@peter-hartmann peter-hartmann changed the title Spawn codiad container for an existing project Spawn codiad container for existing projects Dec 28, 2017
@tobbenb
Copy link
Contributor

tobbenb commented Dec 28, 2017

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?

@peter-hartmann
Copy link
Author

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

@tobbenb
Copy link
Contributor

tobbenb commented Dec 28, 2017

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.

@peter-hartmann
Copy link
Author

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.

@tobbenb
Copy link
Contributor

tobbenb commented Dec 31, 2017

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.

@peter-hartmann
Copy link
Author

peter-hartmann commented Jan 2, 2018

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants