Closed paulczar closed 8 years ago
If you set it up on the top level route /
does it work? I think it's just a simple case of not using relative paths for the static assets.
I can confirm that setting up drone-wall as a top-level route works while setting it up as a route like /wall
does not work. I would prefer a route like /wall
to work though!
Per https://github.com/drone/drone-wall/commit/b4d0c95b1bb8f2f451d8e7388db4ef5ca6d65a7d, can now install in non-root directories, ala /wall
. See addition to README.
Will be included in 3.1.0
release.
if I run this behind nginx I only see the text and not the css etc to make it look pretty.
started with `/usr/local/bin/drone-wall --datasource=/var/lib/drone/drone.sqlite --repos=github.com/xxxx/xxxx --port=:8500'
nginx config is dead simple
viewing it on port 8500 looks fine, through the nginx proxy: