Box still looks at development path when binary deployed to server. about packr HOT 2 CLOSED

I might not have illustrated my problem sufficiently, but I fixed the issue and it wasn't a packr problem so I'm sorry to mark it as one. I was reading the query files into global variables, and the read was executed before the init() function that initialises the packr box.

I'm still learning Go and on a new project and I didn't realise the order of execution that was occurring.

from packr.

The ../ indicates you are going up your directory tree, packr only works going down your directory. The reason is that since it drops go files those files need to be in the path you’re about to compile. Go doesn’t compile up your path, only down it.

from packr.