Age | Commit message (Collapse) | Author |
|
|
|
instead of a boring table of contents, try to show our more exciting README file
it's still a wall of text, but at least all the buzzwords and highlights are there
ideally, the table of contents would be in the sidebar, but i don't know how to do that
|
|
|
|
also keep a symlink for backwards compatibility
|
|
include CHANGES.rst directly, use a symlink to keep backwards compat
|
|
|
|
|
|
This reverts commit 4dca50fafab302622eb5c98e0f26a6b34abe8ca6.
Conflicts:
docs/development.rst
|
|
|
|
|
|
|
|
|
|
this integrates the ideas in #214 to have a small checklist of things to send in the announcements on the mailing list and on the github release
|
|
mention that binaries should be signed
clarify where release milestones
reword all steps to be executive
|
|
link to the locations of different tools when I know them. i marked
the ones I don't know about specially so we can document those as
well.
point to the Github releases for the standalone binaries upload
|
|
|
|
|
|
this or any later 3.x or git master checkout should work.
|
|
|
|
we stop supporting them, because there are better alternatives:
- use a distribution package (from your linux distribution), if available
- use a pyinstaller binary provided by us (they include all you need in 1 file and
thus have better compatibility properties and are easier to install than a wheel)
- install from source (pypi or git) if everything else fails
|
|
while SSH options can be specified through `~/.ssh/config`, some users
may want to use a completely different SSH command for their backups,
without overriding their $PATH variable. it may also be easier to do
ad-hoc configuration and tests that way.
plus, the POLA tells us that users expects something like this to be
supported by commands that talk to ssh. it is supported by rsync, git
and so on.
|
|
|
|
add automatically generated API
|
|
this is a crude hack for now, and could use a better table of contents
but at least we have some way of linking and showing the different
internal functions
the next phase here is obviously to document that API through the
addition of docstrings. a static api.rst could also be easier to read,
but maybe that could go through some docstrings as well, to be tested
|
|
|
|
|
|
right now, the update_usage script regenerates the usage files at
every call
by moving this into the makefile, we make those files be generated
only when the source file change, which makes testing docs much faster
|
|
thanks to level323 for the vagrant docs
|
|
- reduce redundancy (platforms are documented in README.rst)
- reformat to 80 chars width
- clarify checkpoints
- remove workarounds for stuff that was fixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ACLs are implemented as xattrs, so libattr is pulled in as a dependency of libacl.
|
|
xattrs/ACLs need platform specific code and new have none (yet) for them.
|
|
xattrs and ACLs on OpenBSD and NetBSD need development or adaptation of
the platform-specific code.
|
|
use similar code as for openssl headers
|
|
UnicodeDecodeError exception due to non-ascii llfuse setup.py
|
|
|
|
BORG_REPO env var support
|
|
sets the default repository to use, e.g. like:
export BORG_REPO=/mnt/backup/repo
borg init
borg create ::archive
borg list
borg mount :: /mnt
fusermount -u /mnt
borg delete ::archive
|
|
do not use the files cache for such special files
|
|
outdated - it just showed different levels of zlib compression,
but not we additionally have "lzma", "lz4" and "none" compression.
the "usage" and "internals" docs give some hints about them, too.
|
|
a real fix for this is in development, but needs some time.
|
|
|
|
|
|
|