Posted by
dscho on
Apr 13, 2011; 3:55pm
URL: http://imagej.273.s1.nabble.com/Fiji-Updater-for-deploying-ImageJ-was-Re-JarUpdater-An-easy-way-to-distribute-plugin-updates-tp3685016p3685021.html
Hi,
On Sat, 9 Apr 2011, Jarek Sacha wrote:
> Great thanks to Gavin for providing the instructions.
Indeed!
The fascinating part for me was that I expected questions about this and
that, and instead saw the tutorials on the Fiji Wiki!
Thanks, Gavin!
> I was trying to setup an update site for the IJ-Plugins Project hosted
> at SourceForge. I create a directory as described. I started the "Add
> update site" dialog and filled up fields:
>
> Name: IJ-Plugins Project
> URL:
http://sourceforge.net/projects/ij-plugins/files/fiji_update> SSH Host: frs.sourceforge.net
> Upload directory: home/frs/project/i/ij/ij-plugin/fiji_update
As can be seen in Gavin's description, you need a webserver that can serve
static files:
http://pacific.mpi-cbg.de/How_to_set_up_and_populate_an_update_siteSourceForge's File Release System instead serves redirections to mirrors.
No static files. Until somebody who needs this setup to be handled
implements support for it, the Fiji Updater will lack this support.
> When I click on OK am getting error: "Not a valid URL:
>
http://sourceforge.net/projects/ij-plugins/files/fiji_update". Any ideas?
The reason for this is that it is indeed not a valid URL. However, instead
of reporting that the plugin database was not found -- as would have been
the case if the webserver would serve static files -- it serves a
redirection page which Fiji's Updater cannot parse.
But SourceForge _can_ serve static files. In your case, the URL would look
something like
http://ij-plugins.sourceforge.net/fiji/The only problem there is that you cannot access that webspace with a
password-protected SSH account. It is only possible using a private/public
key pair.
So just for you, I now implemented a feature in the Fiji Updater that
let's you read the information stored in your ~/.ssh/config (which is
the typical setup for SSH) to reuse a private key.
Hopefully this feature works for you, and if it does not, hopefully you
will find my gift a useful start to make it work. I do not need that
feature myself at all.
Ciao,
Johannes
P.S.: as the only remark about SSH access was "I can upload files using
sftp" I assumed that you use OpenSSH in spite of your screenshots
suggesting that you are on a Windows machine. So maybe you use Putty, but
I can only guess! If it is Putty, then the private keys are stored
somewhere else, I am certain, and it might not be as straight-forward to
reuse them in the Fiji Updater. As I rarely develop on Windows, and as I
should really take care of problems that are my own, I do hope that you
manage to get this to work with little assistance from my side.