-
Notifications
You must be signed in to change notification settings - Fork 39
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
Issue using make -C server/envs/dev on Ubuntu Server 16.04 #16
Comments
Hi! Yeah apparently the readme on building is incomplete, I'll have to amend it a bit. Sorry about that! You need to install this https://github.com/elazarl/go-bindata-assetfs , just as follows:
As to MariaDb, honestly I have totally no plans supporting it. And given that I have a ton of pending improvements to Geekmarks already, which I'm unable to implement due to lack of time, it's highly unlikely I'll be able to implement it. I could review PRs though. And yes, some basic authn is one of the improvements I'd like to see here, sooner or later. |
How dare this free project you've dedicated personal time to, not meet my every wish and desire? I call shenanigans! Sounds great, I'll give this a test on fresh box, and if it works correctly, I can submit a pull/merge request to update the readme. I'd offer to help with the rest, but I need to get a bit better at Go first. I appreciate you making the app in the first place, and being so responsive on the Issue. |
Haha :)
Great, thank you! |
Okay, so, originally the issue reoccurred, but I realized that in addition to doing these
I need to also ensure that $PATH included ~/go/bin, in addition to /usr/local/go/bin. That's the good news. Now it at least tries to make. once I run make-C server/envs/dev though....
This is a bit weird to me... bindata.go isn't present when you initially clone the repo, and a rudimentary search on Github doesn't appear to compile such a file, but it's present after running the Make. It's the only change in the server/server/ directory. Thoughts? |
This may also be related to Feature Request: be able to use both go-bindata and go-bindata-assetfs at the same time #20 in the go-bindata-assetfs package. I'm going to see if I can make enough sense of things (without knowing Go) to get closer to the problem. |
For debugging, it looks like server/bindata.go is built at Line 8 of server Makefile.
That command, run separately, works fine. It tanks at the go build command, specifically building the server/server section. I also (just for giggles) removed GoLang 1.10, and installed GoLan 1.8.1 to determine if it was a Golang incompatibility, but the same behavior occurs. Still continuing to investigate, but trying to add data as it's available. |
Okay. Cheese and crackers. I think I have a solution, or at least, a potential one. Literally adding one compiler flag to say "ignore the errors" seems to make the thing compile and run. I can at least get something to appear on the hosted sever at port 4000. I will test to confirm it functions in general, and if so, I will re-roll on a fresh box and test it. If that fixes it, I'll put in a PR. |
@IronTooch thanks for the time you're investing here; sorry I'm so busy these days so I can't even try to reproduce it. Probably will manage to do that at weekend. |
Man, I should really check the issues tab before I dive in. Fell into the same hole - sent out #17 and after the page reloaded saw this PR. Looking forward to the fix about the compilation. I tried editing |
@dimonomid Of course! I don't know if it's actually helping, but it's also helping me work on my containerized-go diagnostics and knocking the rust of some old skills, so I'm on board. So spun up new server, made the change to the makefile (plus added a little more chatter to see what was going on), and kicked it off. Currently, make still fails. I think it's because go build is passing back out an error code, even though it's still doing the builds due to the '-e' flag, so make assumes that stage fails and stops the build. So I added '-' to the command, to say continue executing in spite of errors. Changes reflected here. That gets us all the way to the server/Dockerfile., where it bombs out at ADD geekmarks-server / Full output below
|
@IronTooch can you push your branch to your fork? I'd love to play around with this as well, if you're open to that. |
Changes are reflected in the fork, let me know if you don't see them? |
Found them! Will try to get some time in the next few days to play with it. |
I'm a little late to the party but the problem appears to be: geekmarks/server/server/server.go Line 4 in 28e8cb0
This will run bindata "again" (one already exists in the repo currently). I found this via stracing the make process and searching for bindata:
I'm unfamiliar with go, so I wasn't aware that the comments would get parsed: https://blog.carlmjohnson.net/post/2016-11-27-how-to-use-go-generate/ Basically, I commented that out, and I was able to get passed that error. Still no clean build, but working on it. I think a longer term fix would be to remove the bindata-assetfs.go file that's generated in the repo, and let it get generated on build? |
I had some docker permission problems (user needed to be in the docker group) and being lazy and doing sudo make meant that it wasn't finding the project in the $GOPATH of the root user... So for anyone following along, you can change geekmarks/server/server/server.go Line 4 in 28e8cb0
to something like |
Good evening! I'm really looking forward to using geekmarks, but I seem to be having some difficulty building it.
This is the error message that appears when running make -C server/envs/dev in /home/USER_REDACTED/go/src/dmitryfrank.com/geekmarks
Go version is 1.10 linux/amd64
Docker version is 18.03.0-ce, build 0520e24
Docker Compose version is 1.19.0, build 9e633ef
PATH environment variable:
/home/USER_REDACTED/bin:/home/USER_REDACTED/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/go/bin:/home/USER_REDACTED/go:/home/USER_REDACTED/go/bin
Output of "go env"
Of course, I'm happy to provide any other outputs or inputs as needed to troubleshoot.
Additionally, just as an enhancement feature, it would be awesome to be able to use a MariaDb database as opposed to Postgres, as I have a separate DB server, and it would help for portability. I would also second the request for some kind of basic auth. Thanks!
The text was updated successfully, but these errors were encountered: