needed to switch this 2 steps, to get the 3rd secret
docker-compose build <== this may take a while, go make yourself a cup of tea ️
Now that the image is built, we’re going to generate 3 secret keys that are required for the configuration. Run this command 3 times and note down each of the keys generated, we’ll need them in a minute:
docker-compose run --rm web rake secret
–
but than there was in the “build” a fault about some ca.certificates …? do not solfed the problem and , sorry me, still have no idea how to.?
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
—> 0076c3f76149
Removing intermediate container 8be1094e3809
and 2nd-> fault message
yarn install v0.24.5
[1/4] Resolving packages…
[2/4] Fetching packages…
warning fsevents@1.1.2: The platform “linux” is incompatible with this module.
info “fsevents@1.1.2” is an optional dependency and failed compatibility check. Excluding it from installation.
warning store@1.3.20: The engine “browser” appears to be invalid.
[3/4] Linking dependencies…
warning “chai-enzyme@0.7.1” has incorrect peer dependency “chai@3.x”.
later the behavior of the instance is faulty.
there are no images uploadable . profiles are not customizable . all user profiles are at default image and also on other instances they are just in default image.
what do you want exactly to know? I see no errors. There are this faults , that there is no realy working instance like i
told.
what do you mean “client side” ?
may be there are some rights not set for some path? but this was not documented in the guide.
some the files are not able to store? just a guess.
as i understand this file i use is not needed to config. but i had a look inside to doublecheck. looks good as far.
i still think there is a conflict in my install user .
so we tried to run chown -R 991:991 public/system again with no effect.
still trying. some ideas !
But a question into the field : how many admin running mastodon virtual on a virtual machine?
I got an answer back from my VPS provider . Tell could be a problem … so tell me your opinion
I run mine on docker on digital ocean VPS with no issues. That chown command likely needs to be run within the docker container tho, not from the host. as thats where user/group 991 exists I think.
I accomplished similar on mine by, from the host, running sudo chmod -R 755 system/ from within the public directory
Also, may I ask if your preferred language is something other than English, so maybe we can find someone in our community who is fluent in that and can help you in that instead?