# Retool

> Complete product documentation for Retool.

## Pages

- [Retool Documentation](retool-documentation.md): Complete product documentation for Retool.
- [Switch to root to add Kerberos configuration](switch-to-root-to-add-kerberos-configuration.md): USER root
- [Copy Kerberos configuration into the container](copy-kerberos-configuration-into-the-container.md): COPY krb5.conf /etc/krb5.conf # Ensure the destination path is correct
- [Switch back to the application user](switch-back-to-the-application-user.md): USER retool_user
- [Start the Retool API](start-the-retool-api.md): CMD ./docker_scripts/start_api.sh
- [Switch to root to add Kerberos configuration](switch-to-root-to-add-kerberos-configuration-2.md): USER root
- [Copy Kerberos configuration into the container](copy-kerberos-configuration-into-the-container-2.md): COPY krb5.conf /etc/krb5.conf # Ensure the destination path is correct
- [Switch back to the application user](switch-back-to-the-application-user-2.md): USER retool_user
- [section:end - copy krb5.conf](sectionend-copy-krb5conf.md): Once complete, restart your deployment for the changes to take effect.
- [MSSQLSvc/sqlserver.example.com:1433](mssqlsvcsqlserverexamplecom1433.md): Kerberos uses a cache to store tickets for authentication. This cache is relied upon by other tools, such as`kinit`...
- [Do not create a password for the retool user](do-not-create-a-password-for-the-retool-user.md): ec2-user@bastion:~$ sudo adduser retool --password NP
- [Create the authorized_keys file if it does not exist yet](create-the-authorized-keys-file-if-it-does-not-exist-yet.md): mkdir -p /home/retool/.ssh
- [Use your favorite editor to add Retool's public key to the file](use-your-favorite-editor-to-add-retools-public-key-to-the-file.md): vim /home/retool/.ssh/authorized_keys
- [Set permissions on the authorized_keys file](set-permissions-on-the-authorized-keys-file.md): chmod 644 /home/retool/.ssh/authorized_keys
- [Change owner of authorized_keys file to Retool](change-owner-of-authorized-keys-file-to-retool.md): chown retool:retool /home/retool/.ssh/authorized_keys
- [Run shell scripts on remote hosts](run-shell-scripts-on-remote-hosts.md): :::note Beta
- [Example Usage](example-usage.md): Any command supplied to a Shell Script query will be executed on the remote host. A simple application might allow a ...
- [Set up](set-up.md): Your instance of Retool generates a public and private key pair. For Retool to connect with your remote host, you mus...
- [Example Usage](example-usage-2.md): Any command supplied to a Shell Script query will be executed on the remote host. A simple application might allow a ...
- [Log into your Retool organization](log-into-your-retool-organization.md): npx retool-cli login
- [Follow the step by step instructions to create a resource and register a server](follow-the-step-by-step-instructions-to-create-a-resource-and-register-a-server.md): npx retool-cli rpc
- [If no password is setup, run:](if-no-password-is-setup-run.md): redis-cli -h -c -p
- [Otherwise...](otherwise.md): redis-cli -h --tls -a -p
- [Multiplayer-specific environment variables](multiplayer-specific-environment-variables.md): SERVICE_TYPE=MULTIPLAYER
- [Standard required environment variables. Their values should match the values used for the existing Retool backend service.](standard-required-environment-variables-their-values-should-match-the-values-use.md): COOKIE_INSECURE
- [nginx/nginx.conf](nginxnginxconf.md): http {
- [Support both npm and internal registries based on scope](support-both-npm-and-internal-registries-based-on-scope.md): NPM_REGISTRIES=@mycompany:
- [Only use internal registry](only-use-internal-registry.md): NPM_REGISTRIES=
- [Authentication for the Github Package repository](authentication-for-the-github-package-repository.md): NPM_REGISTRY_AUTH_LINES=//npm.pkg.github.com/:_authToken=