This post is very old and contains obsolete information.
I wanted to move my ssb installation over to a new computer, and the easiest way was to setup a pub server, invite the old and the new computer to the pub, and then swap out the keys. Here's how to do it.
- Create a server & name
- Create the docker image
- Setup directories, config, and easy shell commands
- Start up a container
- Publish yourself as a
- Connect your client
Create a server
I'm using debian 10 on digital ocean, but I'll let you get the system
on the internet. The only key thing is that it needs to have port
8008 accessible from the outside world.
I prefer to have things contained in a Docker container compared to polluting my environment. This just keeps things cleaner in the future so you don't have node or whatever floating around on your system. This may be overly complicated if you aren't already a docker user, or if you already have node installed on your system.
If you already have node, you can follow the setting up a pub directions straight from the mothership.
On the server, create a directory to work in, like
And then create a Dockerfile:
And then build this with
The reason that we are doing this in a seperate directory is to make sure that we don't send the whole pub data instance to docker build if we want to do this in the future.
You could also do this on your local machine and the publish the image to dockerhub, but this is really just to isolate the npm install not to make something publically available.
Setup directories and config files
~/pubdata/config, make sure to add your DNS name or ip
address in the external field.
And create a
~/ssb-server script that will let you interact with the
container that we will create in the next section:
Also be sure to
chmod +x ssb-server to make it runnable.
Create the container
|-d||Detach and run as a daemon|
|–name||Name of the container, which is the same as the instance|
|–restart||For reboots, etc|
Now check the logs to make sure that everything started up correctly.
If that looks good We can now test this by running command
./ssb-server whoami command to see if it's responding correctly.
If it's working, then publish an about entry for your pub. This is what I did:
Create an invite
Once this is working, it's time to create some invites so you can connect your local instance to this pub.
That will spit out an awesome looking string. We'll use that in our clients to connect.
Migrate your stuff over
You could also try oasis, which doesn't run in electron and so therefor is better, even if it is a but more minimalist.
Note that while they both share the same
.ssb data folder, if you want
to use both you'll need to start up patchwork first.
- On the old machine, invite yourself to the pub.
- Sync your stuff to the new pub.
- On the new machine, invite yourself to the pub.
- Follow your old user.
- Wait for things to sync
- On the new machine, close everything.
- Copy the old
.ssb/secretfrom the old to the new machine.
- On the new machine, delete everthing in
- Open up ssb-first-aid-kit and delete the index
- Restart patchwork and watch that sucker index everything in the whole world.
This really started to heat my machine up!
I found that the initial index worked in patchwork, and then it started pulling in more data and eventually exploded. I was able to run oasis instead, which seemed to be better at rebuilding the index.
Now I have my old profile on my new machine.