Strange--I totally wasn't able to get 'devstep run -c "blah"' to run yesterday. It's working today.

Aaron C. de Bruyn

@darkpixel

How do I set environment variables for every run or build? (I know I can probably use 'devstep run -c "DB_HOST=blah python manage.py runserver", but doing that every time would be a pain.) ;)

Aaron C. de Bruyn

@darkpixel

Er--oops. I was using 'devstep hack -c...'. I have one window that I pop up in tmux that basically runs 'git status' and then sits at the bash prompt. Any way to add the -c flag to the hack command so you can run an initial command in the container?

Fabio Rehm

@fgrehm

@darkpixel that can currently be set from a project specific .devsteprc or $HOME/.devsteprc, with the upcoming 0.2.0 release that configuration file will change to a yaml file but the docs will be kept at http://fgrehm.viewdocs.io/devstep/cli/configuration ;)

and the custom hack command, I've added it to the new cli issue tracker

if you need help with that configuration just LMK

Fabio Rehm

@fgrehm

@darkpixel just so you know, I've just cut a release of the new CLI and base image, let me know if you need help migrating your environments to this new version!

Aaron C. de Bruyn

@darkpixel

Looks like the /devstep file in your repo was blown away in the 0.2.0 release. I figure upgrading is as simple as downloading that missing file into ~/bin/devstep

Looks like this commit: fgrehm/devstep@86bba75

Aaron C. de Bruyn

@darkpixel

It looks like you were switching to the go version of the CLI, but the install instructions appear to be lagging behind.

The addition to devstep hack doesn't appear to be working though. When I ru n 'devstep hack git status', it dumps me into the devstep environment, but does not run the command. (http://dpaste.com/2TGGDCC)

Fabio Rehm

@fgrehm

@darkpixel the hack command still lacks the support for a custom subcommand =/ that will come out probably on the next release

Aaron C. de Bruyn

@darkpixel

Ahh. Ok. No worries. Things are working well though. I'm slowly integrating it in to my development process. It's handy because the process matches 'dokku' close enough that I can catch a few errors during development that I would normally only catch on a push to the test or live site. :)

I'd like to see a 'plugin' system similar to dokku where I can 'add on' various linked containers (like Postgres, Reddis, RabbitMQ, etc...) that get started along with the devstep hack container. Dokku uses PluginHook (https://github.com/progrium/pluginhook) to fire off builds sorta like the Heroku buildpack detection.

I might finally have to clone the repo and start playing... :)

Fabio Rehm

@fgrehm

@darkpixel yeah, for now you are probably best served with using fig to "orchestrate" your dev container and its dependencies

I do have plans to implement something like that but for now I'm just managing the linked containers on my own

btw, you know that we've got some automatic port forwarding in place right?

@dontdieych the latest binary is really 0.1.0, the latest image is 0.2.0 ;)

there are different projects now

dontdieych

@dontdieych

@fgrehm I see. Thanks.

btw, this chat service quite handy.

Aaron C. de Bruyn

@darkpixel

@fgrehm I need to run a bunch of commands simultaneously. For example in Django I need to have 'python manage.py runserver' running. I also need 'python manage.py mail_debug' to start a fake mail server for debugging e-mail sent by the application. My initial thought was have two terminal windows open with 'devstep run python manage.py runserver' and the second with 'devstep run python manage.py mail_debug', but obviously behind the scenes it starts two separate docker containers with no communication between the two. What's the best way to work around this? Instead of starting tmux externally, should I be starting it inside the docker container? If so, what's the best way to get my .tmuxinator config into the container?

Er...actually, that wouldn't work so well. I have a few processes that need to run on my local machine that wouldn't forward so well into a docker container. Maybe a way of linking with existing docker containers?

Fabio Rehm

@fgrehm

@darkpixel re tmuxinator into container: a volume should do the trick, dunno if you are aware of this but we are able to not only share folders with container but also files. so on your devstep.yml you can add:

@darkpixel just so you know, with the upcoming 1.3 release of Docker coming out with support for running commands on existing containers your workflow should become a lot easier after I'm able to figure out how we can leverage that from devstep ;)

Aaron C. de Bruyn

@darkpixel

I'll give it a shot. Thanks @fgrehm.

Hristo I Stoyanov

@hrstoyanov

Hi all, I bumped into this project looking for ways to integrate Netbeans with Docker. Working on building my dev stack , I started using Ansible as a way to script around Docker containers. This worked way better than shell scripts, just wanted to share that ...

Brenno Costa

@brennovich

Hello o/ I'm trying to use devstep now, and I'm still figuring out how to use it. I have a repo with multiple projects inside lib folder, but my .git only exits in the main proj. When I run devstep hack inside a sub project my-proj/lib/sub-proj I get the following error: fatal: Not a git repository (or any parent up to mount point /home/brennovich/code/auction)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

I'm still able to use it as my dev env, but this message is pretty annoying. And I need to have a devstep config per sub-project

Brenno Costa

@brennovich

Solved :) I mounted the main project in /workspace and the sub-proj as a sub folder of it ;)

Fabio Rehm

@fgrehm

awesome! glad you got it working :)

Brenno Costa

@brennovich

Hey guys o/

Sometimes I'm not able to get ruby installed

==> Creating container using'fgrehm/devstep:v0.4.0'
-----> Building project at '/workspace' with the following buildpacks:
- /opt/devstep/buildpacks/ruby
-----> Building with /opt/devstep/buildpacks/ruby
Unable to identify the project ruby version, setting to2.2.2
Downloading and installing ruby-2.2.2 (cedar-14)...
WARNING: 2.2.2 isnot available for Heroku's Cedar 14 stack, attempting to use the Cedar stack Ruby.
Downloading and installing ruby-2.2.2 (cedar)...
Error installing ruby!
tail: cannot open ‘/tmp/build.log’ for reading: No such file or directory