dot.uber.space

todo list

2019-11-12T19:20:00+01:00

I am in the process of moving from two uberspace v6 account into one v7 account. The first account was mainly used for e-mail and for a seafile installation. I thought these two would use most of the space which is provided by uberspace per account. (10GB)

The sharing via seafile is not neccesary right now and I plan to archive most of my mails offline.

Here a list of stuff still running or configured on my old uberspace a.k.a. todo list:

some wordpress blogs (individual installations)
munin (not needed anymore)
pikwik, now matomo (i think i will not install it again, not sure tho)
koken (photo gallery, not maintained anymore :/, will be replace by lychee probably)
fever (not developed anymore, replace by miniflux)
known (my last active blog and a test install (?))
ikiwiki (meant as personal knowledge base, not really used)
old ghost installation ( –> save content)

changes to my uberspace account i made

2019-10-02T12:17:03+02:00

In this post I will note all the changes I made to my uberspace, just to keep track of them. Maybe this will come in handy later. Not in the order I made, but somewhat grouped.

Security

set a password to my account (D’oh!)
set an ssh password (for now, maybe to be removed after moving to keys everywhere?)
set up a ssh key for my notebook ssh instructions

Directories

added directory git for bare repos (the jekyll blog)
added directrory jekyll for my local checkout of this blog
added directory ghost for a blog with ghost
added directory postgresfor postgres
added directory backupfor updates to ghost
added symlink domainsto /var/www/virtual/dot
added folder for new domains into domains

Installs

installation of packages with npm (for ghost)
installation of some gem (for jekyll)
download & installation & configuration of postgres
download binary for miniflux to ~/bin
download & installation & configurastion of wordpress

Setup

added a domain for mail
added another domain for mail (mailboxes are shared)
setup a web domain with uberspace web domain add <domain-name> for ghost
setup a web domain for miniflux
setup other web domains
setup of a port for web backend with uberspace web backend set <domain>/ --http --port <port> for ghost(Attention: don’t forget the domain, otherwise this blog doesn’t work anymore.)
setup of a port in web backend for miniflux
setup & started a daemon in ~/etc/services.d/ for ghost
setup & started a daemon for postgresql
setup & started a daemon for miniflux
opened a port in the firewall for mosh
changed version of php to v7.2 for a wordpress plugin

Create

created an additional db (Beware: name must start with username_ (for me dot_example)) for ghost
created an additional db for wordpress
scp‘ed mailbox related files from old uberspace (v6)
created a user in the postgres cluster for miniflux
created a db in the postgres cluster for miniflux

Update

update to ghost for new version 2.37.0, 3.0.3

how I transfered my mails from uberspace v6 to v7

2019-10-02T12:17:03+02:00

I thought I read somewhere a blog post or forum entry about how to tranfer mailboxes with all mails an configuration from an uberspace v6 account to a uberspace v7 account. I could not find anything later on.

I just asked the excellent support on twitter and got soon a reply:

kopiere die Datei ~/passwd.cdb und den Ordner ~/users inkl. Unterodner vom alten auf den neuen Uberspace, lege die Domain(s) dort an und ändere den/die MX-Record(s).
— Uberspace Support (@hallouberspace) October 9, 2019

So I just went to work. (See later tweets about qmail files etc.)

[dot@johnson ~]$ scp <old-user>@<v6-hostname>.uberspace.de:~/passwd.cdb .
[dot@johnson ~]$ scp <old-user>@<v6-hostname>.uberspace.de:~/.qmail* .
[dot@johnson ~]$ scp -r <old-user>@<v6-hostname>.uberspace.de:~/users/* ~/users
[dot@johnson ~]$ scp -r <old-user>@<v6-hostname>.uberspace.de:~/ezmlm/* ~/ezmlm

Then I added the domain for mail with this simple command: uberspace mail domain add <domain> and went to my domain registrar to change the MX-Record and add an TXT-Record for SPF. I also removed the domain from my old uberspace account.

I copied after some hours the files in ~/users/again to make sure all mails are up to date in the new place.

In the e-mail client I had to change the server name for IMAP and SMTP and the user name. (server name = <hostname>.uberspace.de, user name = <uberspace-username>-<mailaddress> )

Installation of jekyll on MY uberspace

2019-09-26T10:17:03+02:00

It is really easy to install a jekyll blog on your uberspace. I followed the instructions and I was up and running.

Here are the essential commands:
gem install bundler jekyll
cd jekyll
jekyll new dot.uber.space
cd dot.uber.space
bundle install --path vendor/bundle
bundle exec jekyll build --destination ~/html

Et voilá: the blog is alive.

For now, i just edited some basic stuff in the _config.yml file and left everything else untouched. I will have to read the Jekyll docs sometime.

(I post these here more for myself. Read the uberlab guide for full documentation, please.)

Hello World!

2019-09-25T20:01:03+02:00

Welcome to my latest blog.

This post is written by hand in vim.

-matze

ps.: this I added in Visual Code to test the git-commit-publish workflow….

Welcome to Jekyll!

2019-09-25T17:01:03+02:00

You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.

Jekyll requires blog post files to be named according to the following format:

YEAR-MONTH-DAY-title.MARKUP

Where YEAR is a four-digit number, MONTH and DAY are both two-digit numbers, and MARKUP is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.

Jekyll also offers powerful support for code snippets:

def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.

Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll Talk.