user_creation.md (1874B)
1 # Creating users 2 3 Regardless of the installation method, you'll need to create some users. GoToSocial currently doesn't have a way for users to be created through the web UI, or for people to sign-up through the web UI. 4 5 Using the CLI, you can create a user: 6 7 ```sh 8 $ gotosocial --config-path /path/to/config.yaml \ 9 admin account create \ 10 --username some_username \ 11 --email some_email@whatever.org \ 12 --password 'SOME_PASSWORD' 13 ``` 14 15 In the above command, replace `some_username` with your desired username, `some_email@whatever.org` with the email address you want to associate with your account, and `SOME_PASSWORD` with a secure password. 16 17 If you want your user to have admin rights, you can promote them using a similar command: 18 19 ```sh 20 $ gotosocial --config-path /path/to/config.yaml \ 21 admin account promote --username some_username 22 ``` 23 24 Replace `some_username` with the username of the account you just created. 25 26 !!! info 27 When running these commands, you'll get a bit of output like the following: 28 29 ```text 30 time=XXXX level=info msg=connected to SQLITE database 31 time=XXXX level=info msg=there are no new migrations to run func=doMigration 32 time=XXXX level=info msg=closing db connection 33 ``` 34 35 This is normal and indicates that the commands ran as expected. 36 37 ## Containers 38 39 When running GoToSocial from a container, you'll need to execute the above command in the conatiner instead. How to do this varies based on your container runtime, but for Docker it should look like: 40 41 ```sh 42 $ docker exec -it CONTAINER_NAME_OR_ID \ 43 /gotosocial/gotosocial \ 44 admin account create \ 45 --username some_username \ 46 --email someone@example.org \ 47 --password 'some_very_good_password' 48 ``` 49 50 If you followed our Docker guide, the container name will be `gotosocial`. Both the name and the ID can be retrieved through `docker ps`.