borgbackup/borgweb

Web UI for Borg Backup

borgweb's Issues

Increase backup status poll time

-> 300 ms

Add/remove log file lines when resizeing window

Use infinite scrolling API from #31

Use infinite scrolling API from #31

Output information on the error

The web frontend could display tracebacks etc.

Raise 404 if log is not available

Provide success state value in `/logs` API

Implement `Beginning` and `End of file` buttons

Add a search field

1. As a user I want to search through *the displayed* log file.
2. As a user I want to search through *all* log files.

We do 1, should we also do 2? @ThomasWaldmann

Better log files

Just to link this up properly: borgbackup/borg/issues/58

Determine success state and have it in the log file for easy readout (see #35).

Display in log list if the respective log failed

Infinite scrolling API

old: /logs/idx/start_lineno:end_lineno

new: /logs/idx/offset:linecount

result of http://127.0.0.1:5000/logs/1/282:2:

}{
  "fname": "/home/tw/w/borgweb/logs/localhost-2015-06-18-16:45:19",
  "lines": [
    "A .git/hooks/pre-push.sample",
    "A .git/hooks/pre-rebase.sample"
  ],
  "offset": 342
}

After `Stop backup` block `Start backup` for ~250ms or so?

Just to keep users from accidentally activating another backup process. What do you think?

js: Show status for all log files

With some update to the backend code we can display the status of all log files in the log file overview on the left.

js: Flask down -> `no log available`

Better notify the user that server is down.

Highlight the currently shown log

In the log list on the left side, highlight the currently shown log.

js: `minifyify` sourcemap does not work correctly

In my case Chromium thinks that all error originate in dateformat.js when minifyify /w sourcemap generation is on.

Use Versioneer

Use icons for `next`/`previous`/etc.

• Use icons for next/previous/etc.
• Bigger buttons

feature request: take a look at duplicati 2.0 web interface for inspiration

Hi all,

I'm using borgbackup from command line and after looking for some alternative open source backup for windows, I came across duplicati 2.0 which is not released yet, but it had some amazing easy to use web interface for backup; worth checking out.

specifically,

how the UI guides you to setup the backup configs with ? to show you options
how it lists backup jobs and when clicked you can run the job, modify, restore etc.

http://www.duplicati.com/howtos/how-to-install-and-run-duplicati-2-0-preview

Thanks,

Bedros

Highlight log field shortly when updating it

Just to indicate that it actually was updated.

After site loaded: highlight the currently displayed log in the list

$('#log-files li:nth-child( n ) a').trigger('click')

Disable log file cache for dev purposes

Is there a flag one could use while starting flask? @ThomasWaldmann

Display kill message in browser log

The /backup/stop processing returns whether it could (softly) terminate the process (SIGTERM) or whether it had to use force (SIGKILL). Might be interesting to display or log.

Don't hardcode the name `borg`

Let's allow for easier project forking. Requested by @ThomasWaldmann.

Collapse grid later / when viewport is smaller

When no logs are present display a help file

... Make it easy for new users.

don't use a fixed, absolute pathes in URLs in html / js

/static is correct for the builtin server / when serving the app from /, but the wsgi app lets us serve it from any path and then /static is not correct any more.

Minify JS in release versions

`Start backup` button breaks after first usage

Pagination for log file list

Bad if the log viewer respects the window height but the log file list (on the left) does not.

Display the individual logs success state when opened

A bit margin between file list and log content in folded state

On first start display newest (not oldest) log

template structure needs improvement

tried to make a nice 404 page, rendering it somehow inside the "theme" using this templates/404.html:

{% extends "_layout.html" %}

{% block content %}
<p>404 Not found.</p>
{% endblock %}

But that somehow looks unexpectedly crappy...

After running a backup, automatically display it

Long file list screws up the px-distance between log and pagination

Stop button functionality

Use html5 pushstate?

Forward/backward buttons of the browser do not work meaningfully currently. Using html5 hooks we could.

Repo URL

Add https://borgbackup.github.io/borgweb/ as repo URL (next to the short description, top of the repo page). Only project owners can do that.

Highlight erroneous log lines

Modularise `index.js`

Provide the same attributes if possible for `/logs/1` and `/logs/1/0:10`

1. /logs/1
   json { "log_file": "...", "status": "success" }
2. /logs/1/0:10
   json { "fname": "...", "lines": [ ], "offset": 200 }

Why the difference?

Just test, test, test a bit

Display `Start` button when folded

Stop the text `BorgWeb` (top left) from getting smaller/jumping upward in folded view

See here how to set up dev environment: https://github.com/borgbackup/borgweb/blob/master/docs/installation.rst

Success state checking broken?

borg: Exiting with failure status due to previous errors
U __init__.py
...

yields

{
  "filename": "/home/pguth/github/borgweb/borgweb/logs/localhost-2015-06-22-18:46:29",
  "status": "success"
}

Less distance between lines for individual log file list entries

Internationalization

• Lay groundwork code wise
• Add a language switcher
• React to browser language settings
• See how transifex.com works

Last log page always blank

... should not be that way.

Fix burger button

It worked once.