Simple manual for util?

2024-12-28 16:18:35

adminsforum@hubzilla.org

_jayrope schrieb den folgenden Beitrag Sat, 28 Dec 2024 16:14:51 +0100

Simple manual for util?

@!Hubzilla Support Forum Hi everyone, hope you are having relaxed days between the years.
Is there a simple and concise manual for the various functions of util?

I do only know and use util/udall.

Thanks all in advance!

• sent from #Hubzilla at #Fediverse.

show all 13 comments

2024-12-28 16:34:16

od@zotum.net

> util/udall

Have not seen this to work; always get the response that the domain could not be updated.

If would be better if new bugs (sorry, features) could be paused until documentation is written for these functions.

Why should a volunteer use her/his time to write, if there is going to be a change?

2024-12-29 23:23:45

*_jayrope

jrp@hub.kliklak.net

Anyone?

• sent from #Hubzilla at #Fediverse.

2024-12-29 23:54:20

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

I think most of the stuff in util/ is automated. At the source, it doesn't look like there's so much that's meant to be launched manually.

2024-12-30 01:08:38

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

There is a whole range of cli apps in util that you can and should use. I'm going to start documenting them between the years as far as I can (there's already a small section on config). It contains really important and useful things for configuration with the command line... e.g. the (system-consistent) adding of addon repos, widget repos and theme repos, as well as the updating of these repos, the configuration of several things or an admins tool with which you can add or remove additional users as admins... or have all admin accounts listed.

@od

If util/udall doesn't work for you, something is wrong with your installation. Have you installed the hub with the git sources (git pull ...)? If not, udall won't work either. However, I have never seen an error message of this kind (‘the domain could not be updated’).

2024-12-30 01:45:38

Markus

markus@hubzilla.markusgarlichs.de

@od The error message 'domain could not be updated' seems to have a different cause.

2024-12-30 09:57:28

od@zotum.net

@Der Pepe (Hubzilla) ⁂ ⚝

Have you installed the hub with the git sources (git pull ...)?

Personal preference is not to use git, but to extract the source code 'tarball' file.

@Markus

If the cause is different, then it is not known what to do. The error message appears only in the command terminal.

2024-12-30 10:27:30

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@od

Personal preference is not to use git, but to extract the source code 'tarball' file.

Ok, that explains why udall is not working for you. The update script fetches the changes from the repo via Git during an update. However, the .git directory is missing from a Hubzilla extracted from the tarball... git is also not initialised.

2024-12-30 11:33:13

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@od

The procedure for tarball installations is explained here: Admin-FAQ

How do I update a non-Git install?

Backup .htconfig.php
Backup everything in store/
Backup any custom changes in mod/site/ and view/site
Delete your existing installation
Upload the new version.
Upload the new version of themes and addons.
Restore everything backed up earlier.

2024-12-30 16:30:52

od@zotum.net

@Der Pepe (Hubzilla) ⁂ ⚝

Backup any custom changes in mod/site/ and view/site
Upload the new version of themes and addons.

This advice seems to contradict previous observations of bugs with themes and css|
https://zotum.net/display/308e0517-0985-40bb-9fd6-74676f102f16

2024-12-30 16:57:17

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@od

This advice seems to contradict previous observations of bugs with themes and css

No, on the contrary. The post is about the basic structure of a theme repo, for example, and which files and directories must be present there. Anyone who creates such a theme repo must map the files and directory structure mentioned in the post. The utils for installation and update have nothing to do with this. They only serve the purpose of moving such a theme repo to the correct location in the working directory of the Hubzilla installation and, if necessary, creating symbolic links so that Hubzilla can find it reliably.

This makes it extremely easy to maintain an external theme because you don't have to manually copy a series of files and directories into the Hubzilla directory and make sure that everything is in the right place.

2024-12-30 17:18:48

od@zotum.net

If symbolic links are created (usual problem, incomplete documentation), these would be expected to disappear if the tarball extraction overwrites

2024-12-30 17:45:45

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@od

Don't be angry: The installation with the tarball is a makeshift solution for hosting where shell access is not possible or only possible to a limited extent (simple web hosting). I also ran it like this for a while on an ebshosting server... it wasn't such a good experience. The installation with the git repo is therefore also expressly recommended in the installation instructions.

If you are able to do so, we recommend using git to clone the source repository rather than to use a packaged tar or zip file. This makes the software much easier to update.

2024-12-30 23:23:17

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@_jayrope

👉 CLI Tools (utils)