Wire up passing credentials from FediPanel to the Mastodon configuration #189
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: sysadmin
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
#178 provision admin accounts for deployed services}
Fediversity/Fediversity
#192 Write a test that validates Mastodon credentials are indeed valid}
Fediversity/Fediversity
Reference: Fediversity/Fediversity#189
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a Fediversity user,
I want to choose my initial user credentials,
so that I can log in to my Mastodon instance.
Test:
Given that I am in the panel,
when I am filling the deployment form,
then I should be able to specify my initial credentials such that I can log in to my deployed instance.
c.f.:
the manual command from the wiki seems not to work:
(would this relate to
ProtectHome
in the Mastodon systemd services?)fix: log in to the
mastodon
user bysudo su - mastodon -s $(which bash)
, then try the wiki commands without thesudo -u mastodon
would it work better to try this from nix as we did for pixelfed?
this post presumes you create the account by the web interface, but by default ours seems to have registrations disabled, tho none of the env vars regulating registration seem set so far, nor in the module afaict. hm.
edit: allegedly the nix service does limit mastodon to single-user (why? can the related env var undo this?).
@kiara wrote in #189 (comment):
This is only explicitly enabled in the example from the wiki. I also can't find any indication that anything forces this on our end.
to reproduce:
I could reproduce already, I just wanted to confirm that I don't see an obvious cause for this.
The command we have in Taeer's documentation is:
which differs only on the
--role=Owner
thing. I haven't tried it recently though.Re single-user, a lot of services disable user creation by default, so maybe that is just what is happening here?
@Niols wrote in #189 (comment):
i don't see this configured in nixpkgs or (as @fricklerhandwerk noted) on our end, but don't have a better explanation myself
out of scope for now as per #327