You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Situation: I have an existing golink installation, running on a Pi
locally. There are about 200 links there. I also have a brand new fly.io installation of golink, following the instructions in the README.
I'd like to migrate the data from my old install to the new one.
One approach is simply to recreate the links, taking as input
the go/.export file and looping around a curl command that
does a PUT as described in go/.help . I think I can do that
with jq, awk, and sh.
A second would be to log into the fly.io console, upload some
files, then modify the Dockerfile to use the -snapshot approach
to get things started. I'm less clear on all of the details there.
Any other options I'm missing? I am pretty sure I'll lose use count
information in any circumstance. I have only a single user in this
tailnet so I won't lose who created the link.
The text was updated successfully, but these errors were encountered:
I used the first option here, with a script that looked like this.
In this case go is the first machine, and go-1 is the new
system. I'll resolve the name collision next.
You'd be encouraged to examine the output of the jq|sed operation -
or even make it all jq, if you are better in the use of that tool than I am -
before feeding it into sh.
Thanks for sharing that script. The intent is certainly for the -snapshot flag to allow restoring snapshots like this. Though if you're simply migrating between instances, simply copying the sqlite file is probably simplest and would retain stats as well. The snapshot file is kind of a disaster recovery option in case you lose the sqlite file entirely or it somehow gets corrupted. Actually, I think /.export might even predate our use of sqlite, so maybe it made more sense when we had a directory of json files.
We've never had to restore our database like this, so I've just never gotten around to writing up instructions for it.
Situation: I have an existing golink installation, running on a Pi
locally. There are about 200 links there. I also have a brand new
fly.io
installation of golink, following the instructions in the README.I'd like to migrate the data from my old install to the new one.
One approach is simply to recreate the links, taking as input
the go/.export file and looping around a curl command that
does a PUT as described in go/.help . I think I can do that
with jq, awk, and sh.
A second would be to log into the fly.io console, upload some
files, then modify the Dockerfile to use the
-snapshot
approachto get things started. I'm less clear on all of the details there.
Any other options I'm missing? I am pretty sure I'll lose use count
information in any circumstance. I have only a single user in this
tailnet so I won't lose who created the link.
The text was updated successfully, but these errors were encountered: