Fork of official Bluesky PDS (Personal Data Server).

feedback cleanups

+3 -3
+3 -3
README.md
··· 106 106 * 80/tcp (Used only for TLS certification verification) 107 107 * 443/tcp (Used for all application requests) 108 108 109 - **Note:** there is no need to set up TLS or redirect requests from port 80 to 443 because the Caddy web server, included in the Dockerfile install method, will handle this for you. 109 + **Note:** there is no need to set up TLS or redirect requests from port 80 to 443 because the Caddy web server, included in the Docker compose file, will handle this for you. 110 110 111 111 ### Configure DNS for your domain 112 112 ··· 145 145 curl https://raw.githubusercontent.com/bluesky-social/pds/main/installer.sh > installer.sh 146 146 ``` 147 147 148 - And then run the installer using bash: 148 + And then run the installer using `bash`. You will need `sudo` permissions to continue: 149 149 150 150 ```bash 151 151 sudo bash installer.sh 152 152 ``` 153 153 154 - You will need `sudo` permissions to continue. The install script is interactive and will prompt for input during the install process. You will need to provide your public DNS address, an admin email address (which does not need to be from the same domain), and be prompted to create a PDS user account with its own email address and handle. If you plan to reuse an existing AT handle, you can skip user account creation, though if it is your first time deploying a PDS you may want to create an account using your domain like `account.your-domain.net` for testing purposes. 154 + The install script is interactive and will prompt for input during the install process. You will need to provide your public DNS address, an admin email address (which does not need to be from the same domain), and be prompted to create a PDS user account with its own email address and handle. If you plan to reuse an existing AT handle, you can skip user account creation, though if it is your first time deploying a PDS you may want to create an account using your domain like `account.your-domain.net` for testing purposes. 155 155 156 156 Upon completion of a successful installation, you'll receive output similar to the following: 157 157