| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
| |
It's possible for the file to get duplicate lines in it, and if so, we want
to ignore the dups.
|
| |
|
|
|
| |
One reason to do this is that on OSX, it doesn't jump to the web browser
when opening a new page. Linux seems ahead in usability here... :P
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If the autostart file lists a repository, for which a directory exists,
but there's not actually a valid git repo in there, the web app used to
try to use it, and see it wasn't valid, and then try to autostart again.
The ensuing runaway loop also ate memory, although not as fast as I was led
to belive was happening to someone on IRC yesterday. So that guy may have
had a different problem. But this seems otherwise a reasonable fit for the
circumstances described, if git-annex was started before something that
occurred during desktop login that made the repository available.
|
| | |
|
| |
|
|
| |
git config --list --global exits nonzero when there's no global config
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
They work fine. But I had to go to a lot of trouble to get Yesod to render
routes in a pure function. It may instead make more sense to have each
alert have an assocated IO action, and a single route that runs the IO
action of a given alert id. I just wish I'd realized that before the past
several hours of struggling with something Yesod really doesn't want to
allow.
|
| | |
|
| |
|
|
|
| |
Currently waits for a new transfer slot to open up, which probably needs to
change..
|
| | |
|
| |
|
|
| |
remote setup still todo
|
| |
|
|
|
|
|
|
| |
git annex assistant --autostart will start separate daemons in each
listed autostart repo
running the webapp outside any git-annex repo will open it on the
first listed autostart repo
|
| |
|
|
| |
Remove --foreground and --stop options from it.
|
| | |
|
| |
|
|
|
|
|
|
| |
This prevents multiple runs of the assistant in the foreground, and lets
--stop stop foregrounded runs too.
The webapp firstrun case also now writes a pid file, once it's made the git
repo to put it in.
|
| |
|
|
| |
Some of the trickiest code I've possibly ever written.
|
| |
|
|
| |
My $HOME is in git, let's make it work :)
|
| |
|
|
|
| |
Maybe later it can prompt if they want to use the repo with git-annex, but
for now this is a sane easy choice.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This avoids forking another process, avoids polling, fixes a race,
and avoids a rare forkProcess thread hang that I saw once time
when starting the webapp.
|
| |
|
|
| |
I've seen 10 be too short under load.
|
| |
|
|
|
|
| |
the pid file
fixes a possible race
|
| | |
|
| |
|
|
| |
--force could enable other, unwanted behavior
|
| |
|
|
| |
Useful for testing..
|
| | |
|
|
|
Also, starts the assistant if it wasn't already running.
|
Joey Hess
Joey Hess