devctl features (V1.0)

[bcaldwell]

• auto set on cd nvm and chruby
• cd
  • work with projects not in the default location (v2.0)
• up
  • start docker containers
• down
• server
• init
• update (with git)
• could we do something to help when you get the annoying "your port is in use" thing
  @karanthukral

[karanthukral]

When you say not in the default location do you mean fuzzy search the entire comp?

[bcaldwell]

Ya kind of. I was thinking we can keep a database file to store where all the projects are. Perhaps we could have a devctl add to add it. Might be cool to do it after a git clone

[karanthukral]

you could piggy back off the post clone hook

[bcaldwell]

Ya that would be cool

[bcaldwell]

As a first pass we could use docker compose to manage the containers for us. It would save us from having to configure containers for the mvp

[karanthukral]

We should use an etcd cluster to store where each folder is stored lol

[bcaldwell]

#webscale!

[karanthukral]

it actually might not be a horrible idea actually :P

[bcaldwell]

seems like overkill though. It's kind of shitty to rely on a VM to work

[karanthukral]

Not a VM. Run just simple etcd in a docker container and mount the logfile directory

[bcaldwell]

Docker still requires a VM to run it. Docker seems like an unnecessary dependency

[karanthukral]

Agreed but most of the actual features like booting up stuff have to rely on docker already.

[bcaldwell]

The difference is you expect devctl up to reply on docker whereas I wouldnt expect devctl cd reply on it. Having said that we could do something like this:

• https://blog.docker.com/2016/06/building-serverless-apps-with-docker/
• https://github.com/bfirsh/serverless-docker

Although this adds unnecessary complexity. We would also have to wait for the container to spin up and would require the docker daemon to be running

[karanthukral]

well if you wanted to go all out you could build the vm on top of hypervisor as part of the initialization and not rely on docker. We don't have to use etcd. It was just an idea to see how we could keep this config clean

[bcaldwell]

I was just thinking of using a textfile but I'm not sure thats the best solution. Think theres room for brainstorming here, on how to do this. Might be something to save for future versions.

It would be cool to use etcd though. The way to do it I think would be through serverless docker structure. Might be fun to experiment with

[karanthukral]

I was trying to stay away from the text file thats why I was thinking something like etcd. Lets keep spit balling here

[karanthukral]

https://github.com/coreos/coreos-xhyve

[bcaldwell]

That looks cool

I agree text files are icky
One cool thing that a textfile that could be cool that you can potentially copy it to a new machine and run devctl setup and have it read that file and setup all the projects where they were before. Same could of course be done with other methods

[karanthukral]

Ya etcd is backed by a simple log file too

[karanthukral]

cool too: https://github.com/kelseyhightower/confd

[bcaldwell]

For a project that is

is a very new project, expect bugs!

xhyve is rather dead :(

I've head of confd. It looks cool!!!! Didn't know that it was done by kelsey.

[bcaldwell]

Dev uses ~/.devconfig to setup the default clone path