mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 23:31:56 +00:00
122 lines
7.5 KiB
HTML
122 lines
7.5 KiB
HTML
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>CUCC Expedition Handbook: Uploading files/photos</title>
|
|
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
|
|
</head>
|
|
<body>
|
|
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
|
<h1>Uploading Photos</h1>
|
|
|
|
<h2>The end-result you are trying to achieve</h2>
|
|
What you are trying to do is to get your happy holiday snaps appear properly indexed with all the others from the previous decades of expo history. You can see them all here: <br /> <a
|
|
href="http://expo.survex.com/photos/">http://expo.survex.com/photos/</a><br />
|
|
which is the end result. But all you have to do is to upload the photos to the right place.
|
|
A hidden script does the hard work to make it all look nice.
|
|
|
|
<p>If you are really lazy (or really a beginner) you can use the initial simple method (using /uploads/ )
|
|
for the photos you have taken of cave entrances for cave survey and prospecting purposes. But please
|
|
rename the filenames of the photos intelligently, e.g. "big-hole-near-path-to-fgh.jpg", or
|
|
"2018-ad-07-entrance3.jpg" (rather than "DSC31415926.jpg"), and explain to an admin/nerd what you have done.
|
|
Please use lower-case for all filenames.
|
|
|
|
<p>If you are looking for how to upload a GPS track, those instructions have <a href="gpxupload.html">been moved to here</a>.
|
|
<h2>Simple instructions</h2>
|
|
|
|
<ol>
|
|
<li>Email a photo or two to someone who knows how to do it. <br>
|
|
(If you are doing more than a few photos, email will be clunky, so use another method).
|
|
<li>Use the Expo laptop in the tatty hut. Get someone to show you how to do it.
|
|
</ol>
|
|
<p>That's it. There used to be other ways of doing it using browser extensions but these either don't work anymore [since 2017] or the instructions to install them properly have become too complicated.
|
|
<p>Beginners should always put all their files into the folder <b>/home/expo/expofiles/uploads/</b> and ask an admin to move them to the right place.
|
|
<p>Now go to <a href="#init">using Filezilla initially</a> - still using the Expo laptop.
|
|
|
|
<h2 id="morecomplex">More complex instructions</h2>
|
|
<p>Using your own laptop on expo, or after you return from expo:
|
|
<ol>
|
|
<li>Download and install <b>Filezilla</b>.
|
|
</ol>
|
|
|
|
<p>You do need to know the expo password.</p>
|
|
|
|
<h3 id="install">Installing Filezilla</h3>
|
|
<p>This software works identically on both Windows and Linux.
|
|
<p>Filezilla is an "FTP client". This means that it connects to servers using a venerable service called "file transfer protocol" i.e. FTP. It looks a bit like copying files from one folder to another on your desktop but it works between different machines.
|
|
<ul>
|
|
<li> Download the software from here <a href="https://filezilla-project.org/download.php?show_all=1">Filezilla Downloads</a>. ( Obviously Linux users will use their usual package management system instead of doing this download.)
|
|
<li>Now install the software following <a href="https://wiki.filezilla-project.org/Client_Installation">the instructions here</a>.
|
|
<li>Now configure it to connect to the expo server using the instructions <a href="fzconfig.html">on this expo handbook page</a>
|
|
</ul>
|
|
|
|
<h2 id="init">Using Filezilla initially</h2>
|
|
<p>The expo website has a big section under 'home/expo/expofiles/' that is <b>not under version control</b>. This is dangerous as there is no backup. If you overwrite some important files with your holiday snaps then we are in big trouble. This is where we store big files that we don't want to keep multiple versions of which is why it is not under verson control.
|
|
|
|
<p>So beginners should always put all their files into the folder
|
|
<pre>/home/expo/expofiles/uploads/</pre> and then ask an admin to move them to the right place. The configuration which you just did (if you followed <a href="fzconfig.html">the instructions</a>) will set you up pointing at the correct folder automatically.
|
|
<p>
|
|
To make the admin's life easier, create your own folder in <pre>/home/expo/expofiles/uploads/</pre> with your name like this: <pre>/home/expo/expofiles/uploads/YourName/</pre> and put your files into that folder. ("YourName" should have no spaces, hyphens or underline characters.) So that the admin knpows who is responsible. And for goodness sake please don't upload lots of duplicate photos: cull them first to just the good ones.
|
|
|
|
<h2 id="experienced">Experienced users</h2>
|
|
<p>OK the admin/nerd you have been asking to move the files to the right place is getting fed up and now wants you to put the uploaded photos in the right place yourself. This is where they go:
|
|
|
|
<pre>
|
|
directory: /home/expo/expofiles/<b>photos</b>/2018/YourName/
|
|
</pre>
|
|
or, for GPS logs (GPX files):
|
|
<pre>
|
|
directory: /home/expo/expofiles/<b>gpslogs</b>/2018/YourName/
|
|
</pre>
|
|
<p>Obviously replace 'YourName' with your actual name (no spaces!).
|
|
It is important that you get this right as this specific way of writing
|
|
your name is standardised across the website
|
|
(this is known as "<a href="https://en.wikipedia.org/wiki/Camel_case">CamelCase</a>").
|
|
<p style="margin-left:20px">This is the only place in the whole system
|
|
that you should use some capital letters. Absolutely everywhere else you should use
|
|
only lower-case letters, no spaces, and hyphens (not underlines) when creating filenames, folder names or variable names of any sort.
|
|
<p>
|
|
Use the year that the photo was taken or the GPStrack logged.</p>
|
|
|
|
<p>Note that uploading photos does not automatically update the view
|
|
at <a href="http://expo.survex.com/photos/">http://expo.survex.com/photos/</a> immediately. An update script needs to be run. This should run automatically once/day around midnight UTC (2017 and earlier) or a couple of minutes after you do the upload to the right place (2018 if Wookey gets this sorted out in time) but may be broken. Prod a web admin if nothing is updated by the next morning..</p>
|
|
|
|
<h2>Experts only</h2>
|
|
<p>If you have been using FTP since the last century or are particularly keen on doing everything using the command-line, read on.
|
|
|
|
|
|
<h3>Using scp</h3>
|
|
|
|
<p>Works on Windows (using winscp), Linux (using scp), and no doubt
|
|
mac and android with other tools. If you have Windows 10 and <a href="https://msdn.microsoft.com/en-gb/commandline/wsl/about">have installed bash</a>, then you can use scp.</p>
|
|
|
|
<p>If you don't have winscp installed you can get it from here:
|
|
<a href="http://winscp.net/eng/index.php">http://winscp.net/eng/</a>.</p>
|
|
|
|
<p>quick start guide:
|
|
<a href="http://winscp.net/eng/docs/getting_started">http://winscp.net/eng/docs/getting_started</a></p>
|
|
|
|
<p>screenshots:
|
|
<a href="http://winscp.net/eng/docs/screenshots">http://winscp.net/eng/docs/screenshots</a></p>
|
|
|
|
<!-- WedDAV no longer works because the effective user is "apache" and the permissions
|
|
for the folder /uploads/ no longer allow it to write anything because we had to change it to allow Filezilla
|
|
to work.Philip & Wookey 11 August 2018
|
|
|
|
<h3>Using WebDAV - cadaver</h3>
|
|
<p>Command-line people can use the 'cadaver' client which is even
|
|
available for windows too:
|
|
<a href="http://www.phtagr.org/2009/04/01/cadaver-for-windows/">www.phtagr.org/2009/04/01/cadaver-for-windows/</a></p>
|
|
-->
|
|
|
|
<p>scp gives you an 'explorer-like' interface (although winscp can
|
|
give you a norton-commander-style 2-pane UI as well).</p>
|
|
|
|
<h3>Using WebDAV</h3>
|
|
This no longer works as we had to change the folder permissions for /uploads/. Sorry.
|
|
|
|
<h3>Using rsync</h3>
|
|
<p>No, don't use rsync for this. Really don't. It's too liable to delete everything or to overwrite files which are not changed at all because of the incompatibilities between Linux and Windows filename conventions (uppercase and lowercase are automagically converted and rsync gets it wrong).
|
|
<hr />
|
|
</body>
|
|
</html>
|