Mastodon now requires that these variables are set:
ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY
ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT
ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY
Run bin/rails db:encryption:init to generate new secrets and then assign the environment variables.
Do not change the secrets once they are set, as doing so may cause data loss and other issues that will be difficult or impossible to recover from.
I don't know how to set these variables.
Any suggestions?
I think I have done everything correct. But when running:
`abra app cmd domain.dk app admin -- username user@email.tld`
I get this:
> Cannot find user role with that name
> No such account
> FATA
>
I have tried to run user generation this way:
`abra app cmd domain.dk app bash`
`RAILS_ENV=production bin/tootctl accounts create user --email user@email.tld --confirmed --role Owner` (from https://docs.joinmastodon.org/admin/setup/)
But I get:
> Mastodon now requires that these variables are set:
>
> - ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY
> - ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT
> - ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY
>
> Run `bin/rails db:encryption:init` to generate new secrets and then assign the environment variables.
> Do not change the secrets once they are set, as doing so may cause data loss and other issues that will be difficult or impossible to recover from.
I don't know how to set these variables.
Any suggestions?
Hmmmmm, I assume you're getting No such account because you don't have a user created with the email user@email.tld? However, perhaps, I'm missing something.
The reason you're seeing those env vars errors is because when you run abra app cmd ... this gets injected into the environment:
And then copy/pasta the file_env machinery so I can expose all those env vars manually in my shell session. Annnnd finally run the command. Which will perhaps give you the same error 😛
Good luck!
@jeppebundsgaard
Hmmmmm, I assume you're getting `No such account` because you don't have a user created with the email `user@email.tld`? However, perhaps, I'm missing something.
The reason you're seeing those env vars errors is because when you run `abra app cmd ...` this gets injected into the environment:
https://git.coopcloud.tech/coop-cloud/mastodon/src/commit/414f5acc71b2bb52779b45c33b080f4560a94bb2/abra.sh#L37-L49
I haven't run this recipe in ages but I'd probably just cat this file once I `abra app bash` in.
https://git.coopcloud.tech/coop-cloud/mastodon/src/commit/414f5acc71b2bb52779b45c33b080f4560a94bb2/compose.yml#L26
And then copy/pasta the `file_env` machinery so I can expose all those env vars manually in my shell session. Annnnd finally run the command. Which will perhaps give you the same error 😛
Good luck!
I learned a lot from your answer, thanks! abra calls the exact command I tried from bash, and the results are the same.
But it still doesn't work. It seems from "Cannot find user role with that name" that the user roles normally shipped with Mastodon are not enabled: https://docs.joinmastodon.org/admin/roles/.
But what do I do now?
I learned a lot from your answer, thanks!
`abra` calls the exact command I tried from bash, and the results are the same.
But it still doesn't work. It seems from "Cannot find user role with that name" that the user roles normally shipped with Mastodon are not enabled: https://docs.joinmastodon.org/admin/roles/.
But what do I do now?
I think you're in a "mastodon is the problem" zone and not a "coop cloud is the problem" zone now 🙃
@jeppebundsgaard any help? https://github.com/mastodon/mastodon/issues/18813
I think you're in a "mastodon is the problem" zone and not a "coop cloud is the problem" zone now 🙃
I think you're in a "mastodon is the problem" zone and not a "coop cloud is the problem" zone now 🙃
I looked into the issue, but it seems to be solved years ago. The command in abra.sh uses Owner with a capital O, as it should.
I managed to use the suggestion in the issue to create a user.
RAILS_ENV=production bundle exec bin/tootctl accounts create myusername --email name@email
and then RAILS_ENV=production bin/tootctl account approve myusername
So now I have an approved user, but it is not Owner or Admin, because those roles don't exist.
I guess you are right - this is Mastodon somehow. I'll see what I can find.
> @jeppebundsgaard any help? https://github.com/mastodon/mastodon/issues/18813
>
> I think you're in a "mastodon is the problem" zone and not a "coop cloud is the problem" zone now 🙃
I looked into the issue, but it seems to be solved years ago. The command in abra.sh uses Owner with a capital O, as it should.
I managed to use the suggestion in the issue to create a user.
`RAILS_ENV=production bundle exec bin/tootctl accounts create myusername --email name@email`
and then
`RAILS_ENV=production bin/tootctl account approve myusername`
So now I have an approved user, but it is not Owner or Admin, because those roles don't exist.
I guess you are right - this is Mastodon somehow. I'll see what I can find.
I believe @jeppebundsgaard fixed this with the db:seed command. That should probably be in the setup docs. I think this is relevant: #55
I believe @jeppebundsgaard fixed this with the `db:seed` command. That should probably be in the setup docs. I think this is relevant: https://git.coopcloud.tech/coop-cloud/mastodon/pulls/55
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I think I have done everything correct. But when running:
abra app cmd domain.dk app admin -- username user@email.tldI get this:
I have tried to run user generation this way:
abra app cmd domain.dk app bashRAILS_ENV=production bin/tootctl accounts create user --email user@email.tld --confirmed --role Owner(from https://docs.joinmastodon.org/admin/setup/)But I get:
I don't know how to set these variables.
Any suggestions?
@jeppebundsgaard
Hmmmmm, I assume you're getting
No such accountbecause you don't have a user created with the emailuser@email.tld? However, perhaps, I'm missing something.The reason you're seeing those env vars errors is because when you run
abra app cmd ...this gets injected into the environment:I haven't run this recipe in ages but I'd probably just cat this file once I
abra app bashin.And then copy/pasta the
file_envmachinery so I can expose all those env vars manually in my shell session. Annnnd finally run the command. Which will perhaps give you the same error 😛Good luck!
I learned a lot from your answer, thanks!
abracalls the exact command I tried from bash, and the results are the same.But it still doesn't work. It seems from "Cannot find user role with that name" that the user roles normally shipped with Mastodon are not enabled: https://docs.joinmastodon.org/admin/roles/.
But what do I do now?
@jeppebundsgaard any help? https://github.com/mastodon/mastodon/issues/18813
I think you're in a "mastodon is the problem" zone and not a "coop cloud is the problem" zone now 🙃
I looked into the issue, but it seems to be solved years ago. The command in abra.sh uses Owner with a capital O, as it should.
I managed to use the suggestion in the issue to create a user.
RAILS_ENV=production bundle exec bin/tootctl accounts create myusername --email name@emailand then
RAILS_ENV=production bin/tootctl account approve myusernameSo now I have an approved user, but it is not Owner or Admin, because those roles don't exist.
I guess you are right - this is Mastodon somehow. I'll see what I can find.
I believe @jeppebundsgaard fixed this with the
db:seedcommand. That should probably be in the setup docs. I think this is relevant: #55@nicksellen @Numerica any preferences whether to go with the approach in #55, or document the need to run
db:seed?