I bought the ‘box’ for being a mobile computing tool. Germany’s “Base” mobile provider offers a ZTE Blade for 12 Euros a month, including an internet flatrate and insurance. It’s an Android device, so being based on Linux which initally drew me there.

Being used to Debian based desktop operating system first thing that knocked me out of my path was that the Android market is open for applications from just everyone, so noone who looks at the software in the first place and hardly a way to do so oneself: Which piece is good and which is malware? — I resorted to have installed as little as possible, but added FDroid as an alternative market, for Free Software applications. It’s only a guess that those apps offered there might be no malware since open source anyways and likely descendants of yet known and trusted packages. (Using FDroid you even can install the F/LOSS Frozen Bubbles arcade game but I consider it a bad idea to give it a shot and check out its performance — it works as expected, adapted to the needs of a phone, and you’ll likely will waste hours ‘checking it out’, so, although you can install it, stay away from it unless you’ve got hours to waste.)

Having set up the Blade it’s now my digital multitool: internet browser, mail reader including push notifications, newspaper, still camera, camcorder, Video playback and ‘TV’, music box, podcasts retriever and picture gallery. I also use it as a remote control for my music server mpd which looks very slick. There’s also a notepad somewhere and a terminal to connect to my servers via ssh.

Here’s what I use:
# First of all the phone mobile computing device has a global auto-completion which makes entering text very easy. Also, it can learn new words.
# Then, I use the Hacker Keyboard, to get around the virtual keyboard rather quickly and have cursor keys etc at hand. Additionally, the Hacker Keyboard supports dealing with several languages: I’m used to text in English and in German, and switching languages in the Hacker Keyboard is just a space key swift away. It’s so easy, thus a true time saver.
# For mail I still use GMail, which includes push notification of new mail. Note, as the Google+ realname debate shows Google may lock you out off your Google account and therefore out of your GMail account too, so make sure you’ll have a backup of your GMail data somewhere. Actually getting to a newly arrived mail is as easy as pulling down the top status bar once the mail notification symbol shows up there.
# For web access I still use the phone’s default browser. It’s accessible from every ‘desktop’ where there is a hoveringmain menu bar with browser access in there as a shortcut. As a launcher page I use serchilo.net which beams you down whereever you actually want to go to. Serchilo is a tool where you can enter a search tool shortcut into an input field, followed by the actual search request. So, for example, g Stuttgart gives you all Google search results regarding Stuttgart while w Stuttgart gives you the wikipedia page on Stuttgart, gm Stuttgart jumps you to Goole Maps with Stuttgart centered, wa Stuttgart weather forecast shows the forecast for Stuttgart at Wolfram Alpha and dbt Stuttgart, Berlin tells you shortcut the shedules for the next couple of trains from Stuttgart to Berlin. As using trains is quite expensive in Germany, you can also try mfg Stuttgart, Berlin which gives you the shared rides for the same leg. — So, Serchilo is rather useful. Hence, I use it as my launcher page.
# Entering a lot of text into a web form field my be jumpy in that default browser — entry field moves out of sight sometimes when trying to put the cursor to another location within the same entry field — hence I started using the default notepad the Blade gets shipped with to pre-edit the text there and cut and paste it to the browser entry field once I’m done. Having used the notepad, I learned it’s good at what it shall do — taking notes — but not as good at reissuing it: The notes go somewhere but you don’t find them at the SD card. So once you collected an amount of noted during a holiday tour while you couldn’t access your blog or whatever you had in mind to put the notes finally into, once you’ve taken it into the notepad you’ve got to copy-paste them out there one by one. Also, lacking notepad files, there aren’t timestamps to the notes either. Additionally, to put a couple of hundred lines of text to the GMail client to send it somewhere else, I saw the phone become reeally laggy. That appears to be a shortcoming of the GMail client, not being maded for longer texts.
# Next, for news (feed) reading, I tried Google reader. A lot of people like it, but I don’t. At home, my server updates rawdog a couple of times daily, and that’s where I usually read news too. So, at home I access the web server to get my current news collection. Also, I could download it to the ‘phone’ and reload it from there later on the go.
# On podcasts, I enjoy Google Listen though. It does what it shall do and it’s not overly complex either. Nor much resources drawing either, for all what I can say.
# For photo/video taking, gallery and video playback I just use the default tools installed on the phone. Nothing special to see here, though. Though learned from an earlier digicam, the Blade’s one also sees more than a human does. So having crashed into a corner of a table or something looking at it through ‘the eye’ of the Blade might reveal whether or not you’ll get a bruise early. The cam saw mine very clearly when I almost broke my foot and I myself didn’t see as much of the bruises yet.
# For remote controlling the mpd music server, I’ve got the alternatives of Droid MPD Client and MPDroid. I prefer the latter over the first one, so that’s the one I use.
# Finally, to remotely connect to my server, I use Connect Bot. It’s a SSH client that might be usable for http tunneling too, but I didn’t try yet to really figure it out.

So, that’s it for now. What do you think? Suggestions? Remarks? Let me know, below in the comments.

We start with an ikiwiki.setup edit, the usual way, i.e. I show you the changes I applied by diffing the resulting ikiwiki.setup file against the the untouched system-wide default one afterwards:

$ emacs -nw ~/.iki-test/ikiwiki.setup
$ diff ikiwiki.setup  /usr/share/doc/ikiwiki/html/ikiwiki.setup
14,15c14,15
<       srcdir => "/home/dagobart/.iki-test/bliki/s",
<       destdir => "/home/dagobart/public_html/bliki",
---
>       srcdir => "/path/to/source",
>       destdir => "/var/www/wiki",
17,18c17,18
<       url => "http://localhost/~dagobart/bliki",
<       cgiurl => "http://localhost/~dagobart/cgi-bin/ikiwiki.cgi",
---
>       url => "http://example.org/wiki",
>       cgiurl => "http://example.org/wiki/ikiwiki.cgi",
30c30
<       rcs => "git",
---
>       #rcs => "git",
63,69c63,68
<               {
<                       # The cgi wrapper.
<                       cgi => 1,
< #                     wrapper => "/var/www/wiki/ikiwiki.cgi",
<                       wrapper => "/home/dagobart/public_html/cgi-bin/ikiwiki.cgi",
<                       wrappermode => "06755",
<               },
---
>               #{
>               #       # The cgi wrapper.
>               #       cgi => 1,
>               #       wrapper => "/var/www/wiki/ikiwiki.cgi",
>               #       wrappermode => "06755",
>               #},
81,89c80,87
<               {
<                       # The git post-update wrapper.
<                       # Note that this will overwrite any existing
<                       # post-update hook script, which may not be
<                       # what you want.
< #                     wrapper => "/git/wiki.git/hooks/post-update",
<                       wrapper => "/home/dagobart/.iki-test/bliki/s/.git/hooks/post-update",
<                       wrappermode => "06755",
<               },
---
>               #{
>               #       # The git post-update wrapper.
>               #       # Note that this will overwrite any existing
>               #       # post-update hook script, which may not be
>               #       # what you want.
>               #       wrapper => "/git/wiki.git/hooks/post-update",
>               #       wrappermode => "06755",
>               #},

And that’s already is it. Now, let’s finish it by telling ikiwiki to act upon its setup file again and return home:

$ cd ~/.iki-test/ && ikiwiki -setup ikiwiki.setup -getctime && cd

Done.

First, we become root and make a backup copy of the cherokee config file and launch the Cherokee admin tool:

$ su
# cp /etc/cherokee/cherokee.conf /etc/cherokee/cherokee.conf.orig
# cherokee-admin

Then we direct a JavaScript capable browser to localhost:9090 and leave it at that for a moment.

In an other shell we set up the ikiwiki CGI. (While playing around with the existing setup it turned out that we cannot have the CGI in ~/public_html/bliki, so we overrule part of the old setup.)

First, create a common ~/public_html/cgi-bin, then edit the ikiwiki config file to reflect that.

$ mkdir -p ~/public_html/cgi-bin
$ emacs -nw ~/.iki-test/ikiwiki.setup
$ cd ~/.iki-test/ && diff ikiwiki.setup  /usr/share/doc/ikiwiki/html/ikiwiki.setup && cd
14,15c14,15
<       srcdir => "/home/dagobart/.iki-test/bliki/s",
<       destdir => "/home/dagobart/public_html/bliki",
---
>       srcdir => "/path/to/source",
>       destdir => "/var/www/wiki",
17,18c17,18
<       url => "http://localhost/~dagobart/bliki",
<       cgiurl => "http://localhost/~dagobart/cgi-bin/ikiwiki.cgi",
---
>       url => "http://example.org/wiki",
>       cgiurl => "http://example.org/wiki/ikiwiki.cgi",

As we’re at it, at the same time tell ikiwiki to make use of the CGI and where to find it [continuation of the above diff]:

63,69c63,68
<               {
<                       # The cgi wrapper.
<                       cgi => 1,
< #                     wrapper => "/var/www/wiki/ikiwiki.cgi",
<                       wrapper => "/home/dagobart/public_html/cgi-bin/ikiwiki.cgi",
<                       wrappermode => "06755",
<               },
---
>               #{
>               #       # The cgi wrapper.
>               #       cgi => 1,
>               #       wrapper => "/var/www/wiki/ikiwiki.cgi",
>               #       wrappermode => "06755",
>               #},

Now, make ikiwiki aware of these changes and return to the [user's] home directory (the trailing && cd):

$ cd ~/.iki-test/ && ikiwiki -setup ikiwiki.setup && cd

Now, back to the dangling end of the open browser window with the Cherokee admin tool in it. Direct your browser to http://localhost:9090/vserver either by entering that URL to the browser’s address bar or by just clicking the link here.

As the Cherokee admin web tool makes a lot use of JavaScript, I cannot give immediate URLs where to set up what. Hence, instead, I guide you there starting with/from the http://localhost:9090/vserver page yet mentioned above.

For quicker reading, I introduce a kind of guidance syntax here: a single > — like in Virtual Servers > Virtual Server List — means: On page/In the area labeled “Virtual Servers” look for an item labeled “Virtual Server List”.

Opposed to that, by a >> I refer to an action: menu >> Virtual Servers for example refers to: look at the menu, then click “Virtual Servers”.

Increasing amounts of asterisks at the beginning of a line refer to the depth/nesting you’ll face, like in

menu >> Virtual Servers
* Virtual Servers > ...

This tells you: Once you hit the “Virtual Servers” link in the menu, you’ll be down one level into it, facing a new page calles “Virtual Servers”.

So, the following guide should be pretty easy to read (if not: ask!). It is about making ~/public_html directories become places where you can put HTML content and ~/public_html/cgi-bin the location your ikiwiki CGI goes (or any other for that matter):

menu >> Virtual Servers
* Virtual Servers > Virtual Server List >> default
** Virtual Server > default >> Personal Webs
*** Personal Webs > Directory name: public_html
*** button at end of page
*** Personal Webs > Add new rule > Rule Type: Directory
*** Personal Webs > Add new rule > Web Directory: /cgi-bin
*** button at end of page
*** default – Directory: /cgi-bin > Handler > Handler: CGI
*** button at end of page
*** default – Directory: /cgi-bin > default
*** button at end of page
* Apply

Then. to verify everything went well, direct your browser to a URL your ikiwiki maintains: http://localhost/~dagobart/cgi-bin/ikiwiki.cgi?do=prefs. — If you get a form page — e.g. a login page –, everything went okay (not okay if you get asked whether you’d like to download ikiwiki.cgi).

Interrupt cherokee-admin now, we don’t need it any longer.

Then, there’s only one last step to perform to finish this distributed setup of an ikiwiki bliki.

For this here posting, we work on the local machine, i.e. the mobile computer.

First, as we already have set up ikiwiki’s core config file, we skip redoing that and instead just copy it from our remote machine to our local one, i.e. the mobile computer:

$ scp dagobart@remote-machine.com:/home/dagobart/.ikiwiki/ikiwiki.setup ~/.iki-test/
dagobart@remote-machine.com's password:
ikiwiki.setup                                                   100% 6836     6.7KB/s   00:00

SCP is the secure copy program. Probably yet installed on your machines if you use SSH (Secure Shell).

Now, let’s make sure we have a place where to put the ikiwiki script that’s going to get called whenever we’re changing the bliki by means of the web frontend:

$ mkdir -p ~/public_html/cgi-bin

…and then, go to the local ikiwiki directory and modify the ikiwiki.setup file so it’s going to meet our needs. — As before, I don’t direct you through the file to the things you need to update but rather just show the final diff between the untouched system original ikiwiki.setup file and the one we change:

$ cd ~/.iki-test/
$ emacs -nw ikiwiki.setup
$ diff ikiwiki.setup  /usr/share/doc/ikiwiki/html/ikiwiki.setup
14,15c14,15
<       srcdir => "/home/dagobart/.iki-test/bliki/s",
<       destdir => "/home/dagobart/public_html/bliki",
---
>       srcdir => "/path/to/source",
>       destdir => "/var/www/wiki",
17,18c17,18
<       url => "http://localhost/~dagobart/bliki",
<       cgiurl => "http://localhost/~dagobart/bliki/ikiwiki.cgi",
---
>       url => "http://example.org/wiki",
>       cgiurl => "http://example.org/wiki/ikiwiki.cgi",

You don’t necessarily need the -nw params for emacs — it’s just to keep emacs in the terminal window rather than allowing it to ‘pop out’ and spawn its own frame. Alternatively, you for sure can use your own preferred editor. If you need a simple one, try joe or nano, whereby in my opinion the latter one is too simple (so it becomes complicated again).

Then, we make ikiwiki aware of its changed setup file and examine the changes ikiwiki causes:

$ ikiwiki -setup ikiwiki.setup
$ ls -al
insgesamt 36
drwxr-xr-x  4 dagobart dagobart 4096 21. Mär 18:39 .
drwxr-xr-x 84 dagobart dagobart 4096 21. Mär 18:44 ..
drwxrwsr-x  9 dagobart dagobart 4096 21. Mär 17:45 bliki
drwxr-xr-x  8 dagobart dagobart 4096 21. Mär 18:08 .git
-rw-r--r--  1 dagobart dagobart   25 21. Mär 17:42 .gitignore
-rw-r--r--  1 dagobart dagobart 6833 21. Mär 18:39 ikiwiki.setup
-rw-r--r--  1 dagobart dagobart 6836 21. Mär 18:34 ikiwiki.setup~
$ ls -al bliki/
insgesamt 48
drwxrwsr-x 9 dagobart dagobart 4096 21. Mär 17:45 .
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 18:39 ..
drwxrwsr-x 2 dagobart dagobart 4096 21. Mär 17:45 branches
-rw-rw-r-- 1 dagobart dagobart  126 21. Mär 17:45 config
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:45 d
-rw-rw-r-- 1 dagobart dagobart   58 21. Mär 17:45 description
-rw-rw-r-- 1 dagobart dagobart   23 21. Mär 17:45 HEAD
drwxrwsr-x 2 dagobart dagobart 4096 21. Mär 17:45 hooks
drwxrwsr-x 2 dagobart dagobart 4096 21. Mär 17:45 info
drwxrwsr-x 7 dagobart dagobart 4096 21. Mär 17:45 objects
drwxrwsr-x 4 dagobart dagobart 4096 21. Mär 17:45 refs
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 18:47 s
$ ls -al bliki/s/
insgesamt 20
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 18:47 .
drwxrwsr-x 9 dagobart dagobart 4096 21. Mär 17:45 ..
drwxr-xr-x 8 dagobart dagobart 4096 21. Mär 17:45 .git
-rw-r--r-- 1 dagobart dagobart   25 21. Mär 17:45 .gitignore
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 18:47 .ikiwiki
$ ls -al /home/dagobart/public_html/
insgesamt 12
drwxr-xr-x  3 dagobart dagobart 4096 21. Mär 18:38 .
drwxr-xr-x 84 dagobart dagobart 4096 21. Mär 18:44 ..
drwxr-xr-x 17 dagobart dagobart 4096 21. Mär 18:47 bliki
$ ls -al /home/dagobart/public_html/bliki/
insgesamt 88
drwxr-xr-x 17 dagobart dagobart 4096 21. Mär 18:47 .
drwxr-xr-x  3 dagobart dagobart 4096 21. Mär 18:38 ..
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 blog
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:38 cgi-bin
-rw-r--r--  1 dagobart dagobart  371 21. Mär 18:47 favicon.ico
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 helponformatting
drwxr-xr-x 11 dagobart dagobart 4096 21. Mär 18:47 ikiwiki
-rw-r--r--  1 dagobart dagobart 1462 21. Mär 18:47 index.html
-rw-r--r--  1 dagobart dagobart   95 21. Mär 18:47 local.css
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 markdown
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 openid
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 pagespec
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 preprocessordirective
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 recentchanges
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 sandbox
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 shortcuts
-rw-r--r--  1 dagobart dagobart 5164 21. Mär 18:47 style.css
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 subpage
drwxr-xr-x  4 dagobart dagobart 4096 21. Mär 18:47 templates
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 wikiicons
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 18:47 wikilink

In one word: This just set up our local bliki.
 

Next: Let’s actually make the ikiwiki web frontend run.

The second advantage over a wiki like mediawiki (or a blog like wordpress) — in my first-sight opinion — is that you can update the bliki on your mobile computer while on the move and update the hosted bliki when back online — and in no time.

Now, after having set up a lightweight webserver for ikiwiki (Cherokee), having brought ikiwiki to initial life and managed to get a git underneath the ikiwiki, now I focus on setting up the replication infrastructure for the bliki:

I want the bliki reside on my hosted server (say, remote-machine.com). I want my local in-house server (homeserver) to “download” the latest version of the bliki on a regular basis. The idea is to have a backup at hand. And I want the bliki to reside on my main computer mycomputer (which happens to be a mobile one).

To sum it up:

• the main bliki shall reside on remote-machine.com,
• homeserver shall pull from remote-machine.com,
• mycomputer shall pull from remote-machine.com and push there also.

Both, mycomputer and remote-machine.com, shall be editable by web interface.

So, as we’re working with git, remote-machine.com will have two repositories — a bare one, since ikiwiki claims to have issues with a non-bare repository to work with, and a clone we’ll can actually work with. Similar applies for mycomputer — the box we’ll mainly work with to edit the bliki.

Suggested read: ikiwiki/ tips/ laptop wiki with git
 

First, let’s set up the backup computer. Therefore, we ssh there first. (As before $ indicates commands to be given as a common user, # commands that shoult be issued as root.)

$ ssh homeserver
dagobart@homeserver's password:
Linux homeserver 2.6.26-2-686 #1 SMP Wed Nov 4 20:45:37 UTC 2009 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have new mail.
Last login: Sun Mar 21 16:40:46 2010 from mycomputer-fritz.fritz.box
$ pwd
/home/dagobart
mkdir .ikiwiki && cd .ikiwiki/
$ pwd
/home/dagobart/.ikiwiki
$ git-clone remote-machine.com:/home/dagobart/.ikiwiki/bliki
Initialized empty Git repository in /home/dagobart/.ikiwiki/bliki/.git/
Receiving objects: 100% (3/3), done.
remote: Counting objects: 3, done.
remote: Total 3 (delta 0), reused 0 (delta 0) 

You might want to ensure you won’t have to issue a password when ssh-ing to remote-machine.com every time.

Now, what do we have by now? Let’s see…

$ ls -al
insgesamt 12
drwxr-xr-x  3 dagobart dagobart 4096 21. Mär 17:37 .
drwxr-xr-x 41 dagobart dagobart 4096 21. Mär 17:35 ..
drwxr-xr-x  3 dagobart dagobart 4096 21. Mär 17:37 bliki
$ ls -al bliki/
insgesamt 16
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:37 .
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:37 ..
drwxr-xr-x 8 dagobart dagobart 4096 21. Mär 17:37 .git
-rw-r--r-- 1 dagobart dagobart   25 21. Mär 17:37 .gitignore
$ ls -al bliki/.git
insgesamt 48
drwxr-xr-x 8 dagobart dagobart 4096 21. Mär 17:37 .
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:37 ..
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:37 branches
-rw-r--r-- 1 dagobart dagobart  262 21. Mär 17:37 config
-rw-r--r-- 1 dagobart dagobart   58 21. Mär 17:37 description
-rw-r--r-- 1 dagobart dagobart   23 21. Mär 17:37 HEAD
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:37 hooks
-rw-r--r-- 1 dagobart dagobart  112 21. Mär 17:37 index
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:37 info
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:37 logs
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:37 objects
drwxr-xr-x 5 dagobart dagobart 4096 21. Mär 17:37 refs 

Looks good.

Now, let’s see how a git-pull will work out:

$ cd ~/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki master
From remote-machine.com:/home/dagobart/.ikiwiki/bliki
 * branch            master     -> FETCH_HEAD
Already up-to-date.

That looks well as well.

Now, let’s ensure the backup will remain current all the time. For that let’s update the crontab:

$ crontab -e

This will open an editor.

Enter the following into the editor:

# backup ikiwiki bliki:
 1  0  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1  6  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1 10  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1 12  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1 14  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1 16  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1 19  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki
 1 22  *   *   *    cd /home/dagobart/.ikiwiki/bliki/; git-pull remote-machine.com:/home/dagobart/.ikiwiki/bliki 

Basically, this sets up to poll the remote wiki frequently to keep the backup up to the hour. The setup is focussed to match my working hours as closely as possible. For an explanation of the crontab format, in the command shell issue:

$ man 5 crontab

Above crontab prerequires that you can git-pull from remote-machine.com without a password, cf.above.

More suggested reads:

• $ man git-pull
• $ man git-clone
• and the yet mentioned ikiwiki/ tips/ laptop wiki with git

create mobile computer’s local wiki

For this, I assume, we’re back on the local computer.

$ cd
$ mkdir .iki-test && cd .iki-test
$ pwd
/home/dagobart/.iki-test

Since I initially only wanted to see how this was going to work out, I named the mobile computer’s ikiwiki directory .iki-test. — I could have search&replaced this in this walkthrough back to a more conform .ikiwiki, but actually it helps to remember on which machine and in which repository (bare or non-bare) you currently are. Therefore, .iki-test.

Now, clone the git repository from the remote machine to the local one — and let’s inspect what that made happen:

$ git-clone helbrecht.ws:/home/dagobart/.ikiwiki/bliki
Initialized empty Git repository in /home/dagobart/.iki-test/bliki/.git/
dagobart@helbrecht.ws's password:
remote: Counting objects: 3, done.
remote: Total 3 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (3/3), 239 bytes, done.
$ ls -al
insgesamt 12
drwxr-xr-x  3 dagobart dagobart 4096 21. Mär 17:42 .
drwxr-xr-x 83 dagobart dagobart 4096 21. Mär 17:41 ..
drwxr-xr-x  3 dagobart dagobart 4096 21. Mär 17:42 bliki
$ ls -al bliki/
insgesamt 16
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:42 .
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:42 ..
drwxr-xr-x 8 dagobart dagobart 4096 21. Mär 17:42 .git
-rw-r--r-- 1 dagobart dagobart   25 21. Mär 17:42 .gitignore
$ mv bliki/.git* .
$ ls -al
insgesamt 20
drwxr-xr-x  4 dagobart dagobart 4096 21. Mär 17:43 .
drwxr-xr-x 83 dagobart dagobart 4096 21. Mär 17:41 ..
drwxr-xr-x  2 dagobart dagobart 4096 21. Mär 17:43 bliki
drwxr-xr-x  8 dagobart dagobart 4096 21. Mär 17:42 .git
-rw-r--r--  1 dagobart dagobart   25 21. Mär 17:42 .gitignore
$ ls -al bliki/
insgesamt 8
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:43 .
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:43 ..
$ ls -al .git
insgesamt 48
drwxr-xr-x 8 dagobart dagobart 4096 21. Mär 17:42 .
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:43 ..
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:42 branches
-rw-r--r-- 1 dagobart dagobart  262 21. Mär 17:42 config
-rw-r--r-- 1 dagobart dagobart   58 21. Mär 17:42 description
-rw-r--r-- 1 dagobart dagobart   23 21. Mär 17:42 HEAD
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:42 hooks
-rw-r--r-- 1 dagobart dagobart  112 21. Mär 17:42 index
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:42 info
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:42 logs
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:42 objects
drwxr-xr-x 5 dagobart dagobart 4096 21. Mär 17:42 refs

Now, let’s re-setup those s and d directories we already used when setting up ikiwiki initially. Actually, we’re essentially going to re-do that step:

$ mkdir -p bliki/s bliki/d && cd bliki
$ pwd
/home/dagobart/.iki-test/bliki
$ ls -al
insgesamt 16
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:45 .
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:43 ..
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:45 d
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:45 s
$ ikiwiki-makerepo git s
Importing s into git
Initialized empty shared Git repository in /home/dagobart/.iki-test/bliki/
Initialized empty Git repository in /home/dagobart/.iki-test/bliki/s/.git/
Created initial commit 5bf1878: initial commit
 1 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 .gitignore
Counting objects: 3, done.
Writing objects: 100% (3/3), 244 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /home/dagobart/.iki-test/bliki
 * [new branch]      master -> master
Directory s is now a clone of git repository /home/dagobart/.iki-test/bliki
$ pwd
/home/dagobart/.iki-test/bliki
$ ls -al
insgesamt 48
drwxrwsr-x 9 dagobart dagobart 4096 21. Mär 17:45 .
drwxr-xr-x 4 dagobart dagobart 4096 21. Mär 17:43 ..
drwxrwsr-x 2 dagobart dagobart 4096 21. Mär 17:45 branches
-rw-rw-r-- 1 dagobart dagobart  126 21. Mär 17:45 config
drwxr-xr-x 2 dagobart dagobart 4096 21. Mär 17:45 d
-rw-rw-r-- 1 dagobart dagobart   58 21. Mär 17:45 description
-rw-rw-r-- 1 dagobart dagobart   23 21. Mär 17:45 HEAD
drwxrwsr-x 2 dagobart dagobart 4096 21. Mär 17:45 hooks
drwxrwsr-x 2 dagobart dagobart 4096 21. Mär 17:45 info
drwxrwsr-x 7 dagobart dagobart 4096 21. Mär 17:45 objects
drwxrwsr-x 4 dagobart dagobart 4096 21. Mär 17:45 refs
drwxr-xr-x 3 dagobart dagobart 4096 21. Mär 17:45 s

And finally, let’s make sure we can push from that local git repository to the one on the remote server:

$ git-push .
Everything up-to-date
$ # how to sync remote to local repo:
$ git-pull
dagobart@remote-machine.com's password:
Already up-to-date.