chava

planeta tierra, Sun, 01 Jan 2023 00:00:00 -0800

Happy (Pacific Time Zone) New Year!
🌧️🍻🎉👋

#PreProgrammedPost
#streams

chava

california, Tue, 08 Nov 2022 09:07:17 -0800

Hold up.... was I hallucinating or did I just update this site by clicking on an update button on the admin interface?

Well, I know for a fact that I didn't util/udall over ssh in the last couple of days. Yet here we are on version 22.11.06.

#streams #fediverse #sorcery

show all 4 comments

chava

Tue, 08 Nov 2022 09:15:34 -0800

Nice!

Adam Robertson

Tue, 08 Nov 2022 12:27:41 -0800

I also just recently saw the new update button ..very nice!

Marshall Sutherland (Posting with Hubzilla)

Tue, 08 Nov 2022 14:14:00 -0800

I have a cron job that "pushes the button" for me nightly.

On Migrating from Zap to Streams

chava

Tue, 10 May 2022 07:08:17 -0700

#zap #streams #fediverse #activitypub #nomad

mike wrote the following post Mon, 09 May 2022 01:57:43 -0700

There are a few options.

Install streams and import/clone your channel or channels from zap. Only do this if you can run both at once.

install streams on top of your zap site using the existing database and file storage.

do a db backup of zap, install streams. Copy/move cache and store directories (but not .htconfig.php) to the new install and then db restore.

  (The files you might need to preserve from your zap site are .htconfig.php,, the cache directory, and the store directory.)
2 is the fastest, but you'll miss out on a few database optimisations which are included in the streams install.  I have a site running this way and it's perfectly fine.

3 is the highest performance, but read on...

For number 3, manually execute updates 1254, 1255 and 1257 after you have done the db-restore in order to upgrade all the imported channels. You can  do this by visiting

https://yoursite/admin/dbsync 1254
followed by
https://yoursite/admin/dbsync 1255
etc.

mike wrote the following post Mon, 09 May 2022 13:52:21 -0700

Here's what you'll need for a  full migration (you might want to copy/paste or otherwise save this):

Put your webserver to sleep.

----

cd [zapdir]
mysqldump -u [user name] –p [password]  --no-create-info [zap-dbname] > /backupdir/dump.sql
cp -rp cache store .htconfig.php /backupdir
cd ..
git clone git@codeberg.org:streams/streams
cd streams
util/add_addon_repo git@codeberg.org:streams/streams-addons addon
composer install --no-dev

mysql -u [user name] -p
    create database streams;
    use streams;
    source install/schema_mysql.sql;
    source /backupdir/dump.sql
    quit;

cp -rp /backupdir/cache .
cp -rp /backupdir/store .
cp -p /backupdir/.htconfig.php .

Edit .htconfig.php to change the db name to streams

----

Point your webserver at the streams directory and restart it.

Enjoy.

chava

Tue, 10 May 2022 07:17:59 -0700

Now to just find some time when I'm fully awake / well-rested to lower the probability of completely fucking this up.

😆

chava

Tue, 15 Nov 2022 20:38:07 -0800

mike wrote the following post Tue, 04 Oct 2022 14:25:44 -0700

Unfortunately it's no longer possible to just install streams on top of zap. But here's what you do:

backup everything

git clone the streams repository into a fresh directory and cd into it.

git checkout cfa5328c7042c68384169947a2c3f57dbb883942 - what this does is point you at a repository commit from back in February before the repositories and database schemas dramatically diverged.

Copy or move (move is preferable) ".htconfig.php", as well as the 'cache' and 'store' folders and all their contents from your zap base directory to your new streams base directory.

execute util/config system.db_version 1254 from the top level streams directory.

Point your webserver at the new folder or mv the zap folder to another name and rename the streams folder to what it was.

Visit your site. This should be uneventful. Just load a page. Behind the scenes, this will run one conflicting database update (1255).

"git checkout release" and visit your site again. This will run all the database updates between February and now. This may take a few minutes to display a page. Longer if you don't expire content.

Install addons and setup a cron job or schedule task per the instructions in install/INSTALL.txt

Visit the admin page and check the addons. They've changed a bit. Just make sure any you require are installed.

This should do it.

If your site only has one or two accounts/channels it would be preferable to install streams from scratch and clone/import those channels from your old site. The advantage is that the database schema has been tuned for higher performance than you can get by migrating the zap database. You'll need to have web access to both servers to do it this way. When importing, tick the box to make the new streams clone your "primary" location.

chava

Sun, 24 Apr 2022 22:25:28 -0700

Re: Clone Hubzilla to Zap/Streams

mike wrote the following post Sun, 24 Apr 2022 17:17:38 -0700

This has come up before. To make a Hubzilla export file compatible with Zap/Streams add a zap_compat=1 URL parameter to any uexport command. This is added automatically if you import from across the network, but if you export manually to a file, the file will be saved in Hubzilla format by default.

I'm not certain why you can't import across the network. This was working fine the last time I tried it.

[edit: and I just tested and it is still working here...]

#hubzilla #zap #streams
#NomadicIdentity

kris

Mon, 25 Apr 2022 11:59:29 -0700

I think this is not the last time.. For this question. Are we able to clone zap and hubzilla channel ?

Mon, 25 Apr 2022 15:33:00 -0700

You can import a Hubzilla channel to any later project (or anti-project), but you can't go backward.

chava

xavavu@sns.ekoms.top