| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This means that anyone serving up the webapp to users as a service
(ie, without providing any git-annex binary at all to the user) still needs
to provide a link to the source code for it, including any modifications
they may make.
This may make git-annex be covered by the AGPL as a whole when it is built
with the webapp. If in doubt, you should ask a lawyer.
When git-annex is built with the webapp disabled, no AGPLed code is used.
Even building in the assistant does not pull in AGPLed code.
|
| |
|
|
| |
And add a form to add another, unrelated repository
|
| |
|
|
|
|
|
|
|
|
|
| |
Now other repositories can configure special remotes, and when their
configuration has propigated out, they'll appear in the webapp's list of
repositories, with a link to enable them.
Added support for enabling rsync special remotes, and directory special
remotes that are on removable drives. However, encrypted directory special
remotes are not supported yet. The removable drive configuator doesn't
support them yet anyway.
|
| | |
|
| | |
|
| |
|
|
| |
wow, that was easy!
|
| | |
|
| |
|
|
|
| |
for use by other configurators.. probably should be moved to a utility
module somewhere
|
| |
|
|
| |
also broke out webapp types into a separate module
|
| | |
|
| |
|
Joey Hess