robbi5
404 Not Found
The website goes to a 404 page
[martini] listening on :3000 (development) [martini] Started GET / for [::1]:53342 [martini] Completed 404 Not Found in 76.374µs [martini] Started GET /favicon.ico for [::1]:53342 [martini] Completed 404 Not Found in 82.935µs [martini] Started GET / for [::1]:53342 [martini] Completed 404 Not Found in 77.525µs [martini] Started GET / for [::1]:53342 [martini] Completed 404 Not Found in 37.631µs [martini] Started GET / for [::1]:53342 [martini] Completed 404 Not Found in 45.485µs [martini] Started GET / for [::1]:53342 [martini] Completed 404 Not Found in 47.339µs [martini] Started GET / for [::1]:53342 [martini] Completed 404 Not Found in 43.431µs
The soundboard needs to be started from within the source directory, that helped in my case.
Why printing an error message if this is a bug that can be fixed? I think it should rather be fixed than closed, but I'm not a Go guy...
Why printing an error message if this is a bug that can be fixed? I think it should rather be fixed than closed, but I'm not a Go guy...
Well technically it was never broken. You just need to start it in the correct working directory. I don't see how this could be fixed, but as @lnjX said, an error on the command line would be helpful to understand what is going on.
A chdir() to the correct directory would be a hacky fix, but would avoid printing an error message for a bug that can definitely be fixed. But I technically see no reason why cwd actually plays an role.
Take another example: If I'd like to start firefox, I don't want 'cd /usr/bin' every time I'd like to start it.
Well okay that's actually right, it could just search for the files using a relative path from the binary. However a proper error message would be better than nothing for now.