You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Nextcloud bot 02b0f85818
[tx-robot] updated from transifex
3 days ago
.github Add the issue template 2 years ago
.tx Fix tx config 1 year ago
appinfo Update version on master 3 months ago
build bumb dependencies 1 month ago
css fix scrolling not loading new entries 5 months ago
img Add icon (use same as versions app icon), fix #38 2 years ago
js fix typo 1 month ago
l10n [tx-robot] updated from transifex 3 days ago
lib Also get the very first log line 1 month ago
screenshots update info.xml 3 years ago
templates fix search for nc14 1 year ago
tests fix phpunit config 1 month ago
webpack fix hmr 5 months ago
.babelrc remove dependency on bluebird 1 year ago
.gitignore travis config 1 month ago
.travis.yml fix frontend build test 1 month ago
Makefile simplify dev server setup 1 year ago
README.md Update README.md 1 year ago
composer.json travis config 1 month ago
composer.lock travis config 1 month ago
package-lock.json npm audit fix 1 month ago
package.json bumb dependencies 1 month ago
postcss.config.js bumb dependencies 5 months ago

README.md

Log Reader

screenshot

Log reader for Nextcloud with clean exception display, infinite scrolling and more.

Install instructions

Installed by default

Log Reader is installed by default in recent versions of Nextcloud so you don’t have to do anything else to use the app.

Install the latest sable release manually

  • Download the last pre-build release
  • Extract the tar.gz into the apps folder

Install from source

  • clone the repo in the apps folder
  • Run make in the logreader folder

Developing

For building the app node and npm are required

Building

Building the app can be done using the Makefile

make

Automatic rebuilding during development

During development the webpack dev server can be used to automatically build the code for every change.

Since the compiled source from the webpack dev server need to be injected in the regular Nextcloud sources a proxy setup is needed to combine things.

If your local Nextcloud setup runs at http://localcloud an nginx configuration for the proxy would look like the following:

server {
    listen 81;
    server_name localcloud;

    location /apps/logreader/build/main.js {
        proxy_pass http://localhost:3000/build/main.js;
    }
    location /apps/logreader/build/main.css {
        return 404;
    }
    
    location /build {
        proxy_pass http://localhost:3000;
    }
    location /__webpack_hmr {
        proxy_set_header Host $host;
        proxy_pass http://localhost:3000;
        proxy_set_header Connection '';
        proxy_http_version 1.1;
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
    }

    location / {
        proxy_set_header Host $host;
        proxy_hide_header Content-Security-Policy;
        proxy_pass http://localcloud/;
    }
}

This will run the proxy at http://localcloud:81/

With the proxy configured you can start the webpack dev server and specify where the Nextcloud proxy is.

PROXY_URL="http://localcloud:81/ make watch