Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow scriptsPath to be configurable for use with godep etc. #9

Closed
wants to merge 1 commit into from
Closed

Conversation

djcas9
Copy link

@djcas9 djcas9 commented May 13, 2015

I use godep for all of my project deps and godep has one other dir before src. (_wordspace). Not sure if this is the best solution for something like this but I guess it's a conversation starter.

@albrow
Copy link
Owner

albrow commented May 13, 2015

@mephux thanks for letting me know. I want to get this working for everyone. If possible, I'd like to avoid having users specify where the internal scripts are. It feels a little weird and goes against the goal of making Zoom as easy to use as possible.

I only have a little bit of experience with godep. I stopped using it because it messed with the work I was doing in my local repositories. Could you tell me exactly what your GOPATH looks like? Did you meant that your source files are in GOPATH/_wordspace/src? And any other information you feel would be helpful.

I also just wanted to let you know that https://github.com/albrow/jobs uses scripts in a similar way, so whatever solution we come up with here, I will likely port to jobs.

I'm going to investigate a few alternatives. I'd be happy to hear more ideas.

@djcas9
Copy link
Author

djcas9 commented May 13, 2015

@albrow well, I guess this wont work for my use case as I want just one binary to distribute. How about using go-bindata and packaging the scripts with the binary or whatever is being built?

@djcas9
Copy link
Author

djcas9 commented May 13, 2015

I'll build a poc reall quick and see what you think

@djcas9
Copy link
Author

djcas9 commented May 13, 2015

@albrow Closing this PR. I just created #10 - this is how I would solve it at least. This should work great for jobs as well.

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

Successfully merging this pull request may close these issues.

None yet

2 participants