enable and document using manage.py in online environment #260

Closed

kiara wants to merge 1 commit from kiara/fediversity:online-manage-py into main

kiara commented

2025-03-19 16:20:46 +01:00

Owner

allows e.g. making users from cli

fricklerhandwerk was assigned by kiara

2025-03-19 16:20:47 +01:00

kevin was assigned by kiara

2025-03-19 16:20:47 +01:00

lois was assigned by kiara

2025-03-19 16:20:47 +01:00

fricklerhandwerk commented

2025-03-20 09:33:41 +01:00

Owner

The existing code should work; what problem is this trying to solve?

kiara commented

2025-03-20 09:38:36 +01:00

Author

Owner

@fricklerhandwerk try it in the demo env - each of the currently mandatory env vars will error as they are set only in the service, not in external cli invocations

fricklerhandwerk commented

2025-03-20 10:09:49 +01:00

Owner

It's possible that the command is slightly broken because, as noted early on, all of this tends to be janky if not set just right. But ripping out a random part of that system and trying to run manual invocations is not the right approach.

I'll test and debug it later today.

That would be very surprising, this is the code where it's accounted for: https://git.fediversity.eu/Fediversity/Fediversity/src/branch/main/panel/nix/configuration.nix#L45 And the executable is added to the environment here: https://git.fediversity.eu/Fediversity/Fediversity/src/branch/main/panel/nix/configuration.nix#L139 It's possible that the command is slightly broken because, as noted early on, all of this tends to be janky if not set just right. But ripping out a random part of that system and trying to run manual invocations is not the right approach. I'll test and debug it later today.

👍 1

kiara commented

2025-03-20 10:21:25 +01:00

Author

Owner

i see, thanks for your feedback.
i now understand the manage command is exposed under the root user, while the environment could say be borrowed from the service by systemd-run.
that being said, the credential currently is exposed only to the service, which our settings.py currently requires while manual invocations of the manage command would typically be run from a shell, rather than from our service.

i see, thanks for your feedback. i now understand the `manage` command is exposed under the root user, while the environment could say be borrowed from the service by `systemd-run`. that being said, the credential currently is exposed only to the service, which our `settings.py` currently requires while manual invocations of the `manage` command would typically be run from a shell, rather than from our service.

kiara force-pushed online-manage-py from 62cdb566e6

/ check-pre-commit (pull_request) Successful in 23s

Details

/ check-website (pull_request) Successful in 8s

Details

/ check-peertube (pull_request) Successful in 20s

Details

to 34fca24bb1

/ check-pre-commit (pull_request) Successful in 25s

Details

/ check-website (pull_request) Successful in 11s

Details