localhost { root * /root encode gzip file_server { browse ./file-browser-template-for-caddy.html hide .* } } </code></pre>

Nodejs Monorepo

2022-03-26T00:00:00+00:00

Use changesets as monorepo mananger.

Tools 🔗</a></h2>
GitHub - atlassian/changesets: 🦋 A way to manage your versioning and changelogs with a focus on monorepos</a>

Use Changesets as monorepo manager 🔗</a></h2>

Init a monorepo 🔗</a></h3>

mkdir</span> monorepo && </span>cd</span> monorepo
</span>git</span> init
</span># Add .gitignore file for nodejs <https://github.com/github/gitignore/blob/master/Node.gitignore>
</span>npm</span> init</span> --yes
</span></code></pre>
Add "private":"true"</code> to the root package.json</code></p>
npm</span> init</span> -w</span> packages/a
</span>npm</span> init</span> -w</span> packages/b
</span>npm</span> init</span> -w</span> packages/c
</span></code></pre>
Let c</code> depends a</code> and b</code>,</p>
Add</p>
"</span>dependencies</span>": {
</span>  "</span>a</span>":"</span>^1.0.0</span>",
</span>  "</span>b</span>":"</span>^1.0.0</span>"
</span>}
</span></code></pre>
to packages/c/package.json</code></p>
Install changesets🔗</a></h3>
Also see here</a></p>
npm</span> install</span> -D</span> @changesets/cli && </span>npx</span> changeset init
</span></code></pre>
This action will add a .changeset</code> folder, and a couple of files to help you out:</p>
You should change the .changeset/config.json</code> -> baseBranch</code> to yourself main branch, also change access</code> to public</code></p>
Commit current files.</p>
git</span> add .
</span>git</span> commit</span> -m </span>"</span>feat: init</span>"
</span></code></pre>
That’s done.</p>
Usage🔗</a></h3>
First publish🔗</a></h4>
First publish you should just use the follow command to publish your module</p>
npx</span> changeset publish
</span></code></pre>
Future changes🔗</a></h4>
You should see changesets philosophy</a></p>
You should first create an intent to change</code>, that said, before what ever changes you want to make, you should create a intent change</code></p>
npx</span> changeset
</span></code></pre>
…Make some changes</p>
Now, generate new version, changeset will take care your dependences,</p>

Note, by default, if a</code> upgrade from 1.0.1</code> to 1.0.2</code>, c</code> depends on a@^1.0.1</code>, then c</code> package.json</code> will not change, cause npm will auto update a@^1.0.1</code> to the last version 1.0.2</code>
if you want change to the exact version every time, you can set the config to</p>
 "</span>___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH</span>"</span>: </span>{
</span>    "</span>updateInternalDependents</span>": "</span>always</span>"
</span> }
</span></code></pre>
</blockquote>
npx</span> changeset version
</span></code></pre>
Then, you can publish it.</p>
npx</span> changeset publish
</span></code></pre>
git</span> add .
</span>git</span> commit</span> -m </span>"</span>chore: version</span>"
</span>git</span> push</span> --follow-tags
</span></code></pre>
With CI🔗</a></h2>
I’ll use Github Actions as example.</p>
The CI workflow assume that you use 开发技巧收藏</a> as your git workflow.</p>

Note, you can use @changesets/changelog-github</code></a> as your changelog format log. with this, you can generate a log like this</a> , without this, then the log will only include commit link</a> > npm i -D @changesets/changelog-github</code></p>
{
</span>  "</span>changelog</span>": [
</span>    "</span>@changesets/changelog-github</span>",
</span>    { "</span>repo</span>": "</span>theowenyoung/monorepo-example</span>" }
</span>  ]
</span>}
</span></code></pre>
</blockquote>

Create a script in root package.json</code></li>
</ol>
{
</span>  "</span>scripts</span>": {
</span>    "</span>version-packages</span>": "</span>changeset version</span>",
</span>    "</span>release</span>": "</span>changeset publish</span>"
</span>  }
</span>}
</span></code></pre>

Create github actions workflows</li>
</ol>
mkdir -p</span> .github/workflows
</span></code></pre>
touch</span> .github/workflows/release.yml
</span></code></pre>
With the following content:</p>
name</span>: </span>Release
</span>
</span>on</span>:
</span>  </span>workflow_dispatch</span>:
</span>  </span>push</span>:
</span>    </span>branches</span>:
</span>      - </span>main
</span>
</span>jobs</span>:
</span>  </span>release</span>:
</span>    </span>name</span>: </span>Release
</span>    </span>runs-on</span>: </span>ubuntu-latest
</span>    </span>steps</span>:
</span>      - </span>name</span>: </span>Checkout Repo
</span>        </span>uses</span>: </span>actions/checkout@master
</span>        </span>with</span>:
</span>          </span># This makes Actions fetch all Git history so that Changesets can generate changelogs with the correct commits
</span>          </span>fetch-depth</span>: </span>0
</span>
</span>      - </span>name</span>: </span>Setup Node.js 12.x
</span>        </span>uses</span>: </span>actions/setup-node@master
</span>        </span>with</span>:
</span>          </span>node-version</span>: </span>12.x
</span>      - </span>name</span>: </span>Setup NPM Latest
</span>        </span>run</span>: </span>npm i -g npm
</span>      - </span>name</span>: </span>Install Dependencies
</span>        </span>run</span>: </span>npm i
</span>
</span>      - </span>name</span>: </span>Create Release Pull Request or Publish to npm
</span>        </span>uses</span>: </span>changesets/action@master
</span>        </span>with</span>:
</span>          </span># this expects you to have a script called release which does a build for your packages and calls changeset publish
</span>          </span>publish</span>: </span>npm run release
</span>          </span>version</span>: </span>npm run version-packages
</span>        </span>env</span>:
</span>          </span>GITHUB_TOKEN</span>: </span>${{ secrets.GITHUB_TOKEN }}
</span>          </span>NPM_TOKEN</span>: </span>${{ secrets.NPM_TOKEN }}
</span></code></pre>

Add NPM_TOKEN</code> to your github repo secret settings</li>
</ol>
By 开发技巧收藏</a></p>
npm</span> token create
</span></code></pre>
Done.</p>
Every time you use npx changeset</code> to generate a new changeset intent, and the change is pulled to the main</code> branch, then CI will create a pull request to generate a new version, and after the pull request was merged, CI will publish npm packages, and create a new release.</p>

Install PHP 8.0 On CentOS 7 / RHEL 7

2020-03-26T00:00:00+00:00

yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm yum install -y https://rpms.remirepo.net/enterprise/remi-release-7.rpm yum install -y --enablerepo=remi-php80 php php-cli php -v </code></pre>

Peertube Setup with Caddy Server

2020-03-26T00:00:00+00:00

Peertube is an activityPub-federated video streaming platform using P2P directly in your web browser.

Also see here</a>

Pre Requirement 🔗</a></h2>

Debian Server Setup</a></li>
Caddy2 Setup for Debian</a></li>
Nodejs Setup for Debian</a></li>

Install yarn, and be sure to have a recent version</a>: https://yarnpkg.com/en/docs/install#linux-tab</a></li> </ol>

sudo</span> npm i</span> -g</span> yarn
</span></code></pre>

Install Python:</li>
</ol>
On Ubuntu <= bionic (18.04 LTS) or Debian <= Buster:</p>
sudo apt update
</span>sudo apt install python-dev
</span>python --version # Should be >= 2.x or >= 3.x
</span></code></pre>
On Ubuntu >= focal (20.04 LTS) or Debian >= Bullseye:</p>
sudo apt update
</span>sudo apt install python3-dev python-is-python3 # python-is-python2 should also work
</span>python --version # Should be >= 2.x or >= 3.x
</span></code></pre>
Install🔗</a></h2>

Install common dependencies:</li>
</ol>
sudo apt update
</span>sudo apt install certbot nginx ffmpeg postgresql postgresql-contrib openssl g++ make redis-server git cron wget
</span>ffmpeg -version # Should be >= 4.1
</span>g++ -v # Should be >= 5.x
</span></code></pre>
Now that dependencies are installed, before running PeerTube you should start PostgreSQL and Redis:</p>
sudo systemctl start redis postgresql
</span></code></pre>
PeerTube user🔗</a></h3>
Create a peertube</code> user with /var/www/peertube</code> home:</p>
$ sudo useradd -m -d /var/www/peertube -s /bin/bash -p peertube peertube
</span></code></pre>
Set its password:</p>
$ sudo passwd peertube
</span></code></pre>
Database🔗</a></h3>
Create the production database and a peertube user inside PostgreSQL:</p>
$ cd /var/www/peertube
</span>$ sudo -u postgres createuser -P peertube
</span></code></pre>
For password you can use peertube</code> from the default config yaml.</p>
Here you should enter a password for PostgreSQL peertube</code> user, that should be copied in production.yaml</code> file.
Don’t just hit enter else it will be empty.</p>
$ sudo -u postgres createdb -O peertube -E UTF8 -T template0 peertube_prod
</span></code></pre>
Then enable extensions PeerTube needs:</p>
$ sudo -u postgres psql -c "CREATE EXTENSION pg_trgm;" peertube_prod
</span>$ sudo -u postgres psql -c "CREATE EXTENSION unaccent;" peertube_prod
</span></code></pre>
Prepare PeerTube directory🔗</a></h3>
Fetch the latest tagged version of Peertube</p>
$ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/latest | grep tag_name | cut -d '"' -f 4) && echo "Latest Peertube version is $VERSION"
</span></code></pre>
Open the peertube directory, create a few required directories</p>
$ cd /var/www/peertube
</span>$ sudo -u peertube mkdir config storage versions
</span>$ sudo -u peertube chmod 750 config/
</span></code></pre>
Download the latest version of the Peertube client, unzip it and remove the zip</p>
$ cd /var/www/peertube/versions
</span>$ sudo -u peertube wget -q "https://github.com/Chocobozzz/PeerTube/releases/download/${VERSION}/peertube-${VERSION}.zip"
</span>$ sudo -u peertube unzip -q peertube-${VERSION}.zip && sudo -u peertube rm peertube-${VERSION}.zip
</span></code></pre>
Install Peertube:</p>
cd /var/www/peertube
</span>sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest
</span>cd ./peertube-latest
</span>sudo -H -u peertube yarn install --production --pure-lockfile
</span></code></pre>
PeerTube configuration🔗</a></h3>
Copy the default configuration file that contains the default configuration provided by PeerTube.
You must not</strong> update this file.</p>
$ cd /var/www/peertube
</span>$ sudo -u peertube cp peertube-latest/config/default.yaml config/default.yaml
</span></code></pre>
Now copy the production example configuration:</p>
$ cd /var/www/peertube
</span>$ sudo -u peertube cp peertube-latest/config/production.yaml.example config/production.yaml
</span></code></pre>
Then edit the config/production.yaml</code> file according to your webserver
and database configuration (webserver</code>, database</code>, redis</code>, smtp</code> and admin.email</code> sections in particular).
Keys defined in config/production.yaml</code> will override keys defined in config/default.yaml</code>.</p>
PeerTube does not support webserver host change</strong>. Even though PeerTube CLI can help you to switch hostname</a> there’s no official support for that since it is a risky operation that might result in unforeseen errors.</p>
Webserver🔗</a></h3>
We only provide official configuration files for Nginx.</p>
Copy the nginx configuration template:</p>
$ sudo /etc/nginx/sites-available/peertube
</span></code></pre>
with the following config:</p>
# Minimum Nginx version required:  1.13.0 (released Apr 25, 2017)
</span># Please check your Nginx installation features the following modules via 'nginx -V':
</span># STANDARD HTTP MODULES: Core, Proxy, Rewrite, Access, Gzip, Headers, HTTP/2, Log, Real IP, SSL, Thread Pool, Upstream, AIO Multithreading.
</span># THIRD PARTY MODULES:   None.
</span>
</span>upstream </span>backend {
</span>  </span>server </span>127.0.0.1:9000</span>;
</span>}
</span>
</span>server </span>{
</span>  </span>listen </span>8880</span>;
</span>  </span>listen </span>[::]:</span>8880</span>;
</span>  </span>access_log </span>/var/log/nginx/peertube.access.log; </span># reduce I/0 with buffer=10m flush=5m
</span>  </span>error_log  </span>/var/log/nginx/peertube.error.log;
</span>
</span>  </span>##
</span>  </span># Certificates
</span>  </span># you need a certificate to run in production. see https://letsencrypt.org/
</span>  </span>##
</span>
</span>  location @api</span> {
</span>    </span>proxy_set_header </span>X-Forwarded-For </span>$proxy_add_x_forwarded_for</span>;
</span>    </span>proxy_set_header </span>Host  </span>$host</span>;
</span>    </span>proxy_set_header </span>X-Real-IP       </span>$remote_addr</span>;
</span>
</span>    </span>client_max_body_size  </span>100k</span>; </span># default is 1M
</span>
</span>    </span>proxy_connect_timeout </span>10m</span>;
</span>    </span>proxy_send_timeout    </span>10m</span>;
</span>    </span>proxy_read_timeout    </span>10m</span>;
</span>    </span>send_timeout          </span>10m</span>;
</span>
</span>    </span>proxy_pass </span>http://backend</span>;
</span>  }
</span>
</span>  location </span>/ {
</span>    </span>try_files </span>/dev/</span>null </span>@api</span>;
</span>  }
</span>
</span>  location </span>= /api/v1/videos/upload-resumable {
</span>    </span>client_max_body_size    </span>0</span>;
</span>    </span>proxy_request_buffering </span>off</span>;
</span>
</span>    </span>try_files </span>/dev/</span>null </span>@api</span>;
</span>  }
</span>
</span>  location </span>= /api/v1/videos/upload {
</span>    </span>limit_except </span>POST HEAD { deny all; }
</span>
</span>    </span># This is the maximum upload size, which roughly matches the maximum size of a video file.
</span>    </span># Note that temporary space is needed equal to the total size of all concurrent uploads.
</span>    </span># This data gets stored in /var/lib/nginx by default, so you may want to put this directory
</span>    </span># on a dedicated filesystem.
</span>    </span>client_max_body_size                      </span>12G</span>; </span># default is 1M
</span>    </span>add_header            </span>X-File-Maximum-Size </span>8G</span> always; </span># inform backend of the set value in bytes before mime-encoding (x * 1.4 >= client_max_body_size)
</span>
</span>    </span>try_files </span>/dev/</span>null </span>@api</span>;
</span>  }
</span>
</span>  location </span>~ ^/api/v1/(videos|video-playlists|video-channels|users/me) {
</span>    </span>client_max_body_size                      </span>6M</span>; </span># default is 1M
</span>    </span>add_header            </span>X-File-Maximum-Size </span>4M</span> always; </span># inform backend of the set value in bytes before mime-encoding (x * 1.4 >= client_max_body_size)
</span>
</span>    </span>try_files </span>/dev/</span>null </span>@api</span>;
</span>  }
</span>
</span>  </span>##
</span>  </span># Websocket
</span>  </span>##
</span>
</span>  location @api_websocket</span> {
</span>    </span>proxy_http_version </span>1</span>.</span>1</span>;
</span>    </span>proxy_set_header   </span>X-Forwarded-For </span>$proxy_add_x_forwarded_for</span>;
</span>    </span>proxy_set_header   </span>Host            </span>$host</span>;
</span>    </span>proxy_set_header   </span>X-Real-IP       </span>$remote_addr</span>;
</span>    </span>proxy_set_header   </span>Upgrade         </span>$http_upgrade</span>;
</span>    </span>proxy_set_header   </span>Connection      </span>"upgrade"</span>;
</span>
</span>    </span>proxy_pass </span>http://backend</span>;
</span>  }
</span>
</span>  location </span>/socket.io {
</span>    </span>try_files </span>/dev/</span>null </span>@api_websocket</span>;
</span>  }
</span>
</span>  location </span>/tracker/socket {
</span>    </span># Peers send a message to the tracker every 15 minutes
</span>    </span># Don't close the websocket before then
</span>    </span>proxy_read_timeout </span>15m</span>; </span># default is 60s
</span>
</span>    </span>try_files </span>/dev/</span>null </span>@api_websocket</span>;
</span>  }
</span>
</span>  </span>##
</span>  </span># Performance optimizations
</span>  </span># For extra performance please refer to https://github.com/denji/nginx-tuning
</span>  </span>##
</span>
</span>  </span>root </span>/var/www/peertube/storage;
</span>
</span>  </span># Enable compression for JS/CSS/HTML, for improved client load times.
</span>  </span># It might be nice to compress JSON/XML as returned by the API, but
</span>  </span># leaving that out to protect against potential BREACH attack.
</span>  </span>gzip              </span>on</span>;
</span>  </span>gzip_vary         </span>on</span>;
</span>  </span>gzip_types        </span># text/html is always compressed by HttpGzipModule
</span>                    </span>text</span>/css
</span>                    </span>application</span>/javascript
</span>                    </span>font</span>/truetype
</span>                    </span>font</span>/opentype
</span>                    </span>application</span>/vnd.ms-fontobject
</span>                    </span>image</span>/svg+xml;
</span>  </span>gzip_min_length   </span>1000</span>; </span># default is 20 bytes
</span>  </span>gzip_buffers      </span>16 8k</span>;
</span>  </span>gzip_comp_level   </span>2</span>; </span># default is 1
</span>
</span>  </span>client_body_timeout       </span>30s</span>; </span># default is 60
</span>  </span>client_header_timeout     </span>10s</span>; </span># default is 60
</span>  </span>send_timeout              </span>10s</span>; </span># default is 60
</span>  </span>keepalive_timeout         </span>10s</span>; </span># default is 75
</span>  </span>resolver_timeout          </span>10s</span>; </span># default is 30
</span>  </span>reset_timedout_connection </span>on</span>;
</span>  </span>proxy_ignore_client_abort </span>on</span>;
</span>
</span>  </span>tcp_nopush                </span>on</span>; </span># send headers in one piece
</span>  </span>tcp_nodelay               </span>on</span>; </span># don't buffer data sent, good for small data bursts in real time
</span>
</span>  </span># If you have a small /var/lib partition, it could be interesting to store temp nginx uploads in a different place
</span>  </span># See https://nginx.org/en/docs/http/ngx_http_core_module.html#client_body_temp_path
</span>  </span>#client_body_temp_path /var/www/peertube/storage/nginx/;
</span>
</span>  </span># Bypass PeerTube for performance reasons. Optional.
</span>  </span># Should be consistent with client-overrides assets list in /server/controllers/client.ts
</span>  location </span>~ </span>^/client/(assets/images/(icons/icon-36x36\.png|icons/icon-48x48\.png|icons/icon-72x72\.png|icons/icon-96x96\.png|icons/icon-144x144\.png|icons/icon-192x192\.png|icons/icon-512x512\.png|logo\.svg|favicon\.png))$</span> {
</span>    </span>add_header </span>Cache-Control </span>"public, max-age=31536000, immutable"</span>; </span># Cache 1 year
</span>
</span>    </span>root </span>/var/www/peertube;
</span>
</span>    </span>try_files </span>/storage/client-overrides/</span>$1 </span>/peertube-latest/client/dist/</span>$1 @api</span>;
</span>  }
</span>
</span>  </span># Bypass PeerTube for performance reasons. Optional.
</span>  location </span>~ </span>^/client/(.*\.(js|css|png|svg|woff2|otf|ttf|woff|eot))$</span> {
</span>    </span>add_header </span>Cache-Control </span>"public, max-age=31536000, immutable"</span>; </span># Cache 1 year
</span>
</span>    alias </span>/var/www/peertube/peertube-latest/client/dist/</span>$1</span>;
</span>  }
</span>
</span>  </span># Bypass PeerTube for performance reasons. Optional.
</span>  location </span>~ ^/static/(thumbnails|avatars)/ {
</span>    if</span> (</span>$request_method </span>= </span>'OPTIONS'</span>) {
</span>      </span>add_header </span>Access-Control-Allow-Origin  </span>'*'</span>;
</span>      </span>add_header </span>Access-Control-Allow-Methods </span>'GET, OPTIONS'</span>;
</span>      </span>add_header </span>Access-Control-Allow-Headers </span>'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'</span>;
</span>      </span>add_header </span>Access-Control-Max-Age       </span>1728000</span>; </span># Preflight request can be cached 20 days
</span>      </span>add_header </span>Content-Type                 </span>'text/plain charset=UTF-8'</span>;
</span>      </span>add_header </span>Content-Length               </span>0</span>;
</span>      </span>return </span>204</span>;
</span>    }
</span>
</span>    </span>add_header </span>Access-Control-Allow-Origin    </span>'*'</span>;
</span>    </span>add_header </span>Access-Control-Allow-Methods   </span>'GET, OPTIONS'</span>;
</span>    </span>add_header </span>Access-Control-Allow-Headers   </span>'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'</span>;
</span>    </span>add_header </span>Cache-Control                  </span>"public, max-age=7200"</span>; </span># Cache response 2 hours
</span>
</span>    rewrite </span>^/static/(.*)$ /$</span>1</span> break;
</span>
</span>    </span>try_files </span>$uri @api</span>;
</span>  }
</span>
</span>  </span># Bypass PeerTube for performance reasons. Optional.
</span>  location </span>~ ^/static/(webseed|redundancy|streaming-playlists)/ {
</span>    </span>limit_rate_after            </span>5M</span>;
</span>
</span>    </span># Clients usually have 4 simultaneous webseed connections, so the real limit is 3MB/s per client
</span>    </span>set </span>$peertube_limit_rate    </span>800k</span>;
</span>
</span>    </span># Increase rate limit in HLS mode, because we don't have multiple simultaneous connections
</span>    if</span> (</span>$request_uri </span>~ -fragmented.mp4$) {
</span>      </span>set </span>$peertube_limit_rate  </span>5M</span>;
</span>    }
</span>
</span>    </span># Use this line with nginx >= 1.17.0
</span>    </span>#limit_rate $peertube_limit_rate;
</span>    </span># Or this line if your nginx < 1.17.0
</span>    </span>set </span>$limit_rate $peertube_limit_rate</span>;
</span>
</span>    if</span> (</span>$request_method </span>= </span>'OPTIONS'</span>) {
</span>      </span>add_header </span>Access-Control-Allow-Origin  </span>'*'</span>;
</span>      </span>add_header </span>Access-Control-Allow-Methods </span>'GET, OPTIONS'</span>;
</span>      </span>add_header </span>Access-Control-Allow-Headers </span>'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'</span>;
</span>      </span>add_header </span>Access-Control-Max-Age       </span>1728000</span>; </span># Preflight request can be cached 20 days
</span>      </span>add_header </span>Content-Type                 </span>'text/plain charset=UTF-8'</span>;
</span>      </span>add_header </span>Content-Length               </span>0</span>;
</span>      </span>return </span>204</span>;
</span>    }
</span>
</span>    if</span> (</span>$request_method </span>= </span>'GET'</span>) {
</span>      </span>add_header </span>Access-Control-Allow-Origin  </span>'*'</span>;
</span>      </span>add_header </span>Access-Control-Allow-Methods </span>'GET, OPTIONS'</span>;
</span>      </span>add_header </span>Access-Control-Allow-Headers </span>'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'</span>;
</span>
</span>      </span># Don't spam access log file with byte range requests
</span>      </span>access_log </span>off</span>;
</span>    }
</span>
</span>    </span># Enabling the sendfile directive eliminates the step of copying the data into the buffer
</span>    </span># and enables direct copying data from one file descriptor to another.
</span>    </span>sendfile </span>on</span>;
</span>    </span>sendfile_max_chunk </span>1M</span>; </span># prevent one fast connection from entirely occupying the worker process. should be > 800k.
</span>    </span>aio </span>threads;
</span>
</span>    rewrite </span>^/static/webseed/(.*)$ /videos/$</span>1</span> break;
</span>    rewrite </span>^/static/(.*)$         /$</span>1</span>        break;
</span>
</span>    </span>try_files </span>$uri @api</span>;
</span>  }
</span>}
</span></code></pre>
Add caddy config:</p>
example</span>.com {
</span>	</span>reverse_proxy </span>127.0.0.1:8880
</span>}
</span></code></pre>
Then modify the webserver configuration file. Please pay attention to the alias</code> keys of the static locations.
It should correspond to the paths of your storage directories (set in the configuration file inside the storage</code> key).</p>
$ sudo vim /etc/nginx/sites-available/peertube
</span></code></pre>
Activate the configuration file:</p>
$ sudo ln -s /etc/nginx/sites-available/peertube /etc/nginx/sites-enabled/peertube
</span></code></pre>
To generate the certificate for your domain as required to make https work you can use Let’s Encrypt</a>:</p>
$ sudo systemctl stop nginx
</span>$ sudo certbot certonly --standalone --post-hook "systemctl restart nginx"
</span>$ sudo systemctl reload nginx
</span></code></pre>
Now you have the certificates you can reload nginx:</p>
$ sudo systemctl reload nginx
</span></code></pre>
Certbot should have installed a cron to automatically renew your certificate.
Since our nginx template supports webroot renewal, we suggest you to update the renewal config file to use the webroot</code> authenticator:</p>
$ # Replace authenticator = standalone by authenticator = webroot
</span>$ # Add webroot_path = /var/www/certbot
</span>$ sudo vim /etc/letsencrypt/renewal/your-domain.com.conf
</span></code></pre>
TCP/IP Tuning🔗</a></h3>
On Linux</strong></p>
$ sudo cp /var/www/peertube/peertube-latest/support/sysctl.d/30-peertube-tcp.conf /etc/sysctl.d/
</span>$ sudo sysctl -p /etc/sysctl.d/30-peertube-tcp.conf
</span></code></pre>
Your distro may enable this by default, but at least Debian 9 does not, and the default FIFO
scheduler is quite prone to “Buffer Bloat” and extreme latency when dealing with slower client
links as we often encounter in a video server.</p>
systemd🔗</a></h3>
If your OS uses systemd, copy the configuration template:</p>
$ sudo cp /var/www/peertube/peertube-latest/support/systemd/peertube.service /etc/systemd/system/
</span></code></pre>
Check the service file (PeerTube paths and security directives):</p>
$ sudo vim /etc/systemd/system/peertube.service
</span></code></pre>
Tell systemd to reload its config:</p>
$ sudo systemctl daemon-reload
</span></code></pre>
If you want to start PeerTube on boot:</p>
$ sudo systemctl enable peertube
</span></code></pre>
Run:</p>
$ sudo systemctl start peertube
</span>$ sudo journalctl -feu peertube
</span></code></pre>
Run:</p>
$ sudo service peertube start
</span></code></pre>
Administrator🔗</a></h3>
The administrator password is automatically generated and can be found in the PeerTube
logs (path defined in production.yaml</code>). You can also set another password with:</p>
$ cd /var/www/peertube/peertube-latest && NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run reset-password -- -u root
</span></code></pre>
Alternatively you can set the environment variable PT_INITIAL_ROOT_PASSWORD</code>,
to your own administrator password, although it must be 6 characters or more.</p>
What now?🔗</a></h3>
Now your instance is up you can:</p>

Add your instance to the public PeerTube instances index if you want to: https://instances.joinpeertube.org/</li>
Check available CLI tools</a></li>
</ul>
Upgrade🔗</a></h2>
PeerTube instance🔗</a></h3>
Check the changelog (in particular BREAKING CHANGES!):</strong> https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md</p>
Auto🔗</a></h4>
The password it asks is PeerTube’s database user password.</p>
$ cd /var/www/peertube/peertube-latest/scripts && sudo -H -u peertube ./upgrade.sh
</span>$ sudo systemctl restart peertube # Or use your OS command to restart PeerTube if you don't use systemd
</span></code></pre>
Manually🔗</a></h4>
Make a SQL backup</p>
$ SQL_BACKUP_PATH="backup/sql-peertube_prod-$(date -Im).bak" && \
</span>    cd /var/www/peertube && sudo -u peertube mkdir -p backup && \
</span>    sudo -u postgres pg_dump -F c peertube_prod | sudo -u peertube tee "$SQL_BACKUP_PATH" >/dev/null
</span></code></pre>
Fetch the latest tagged version of Peertube:</p>
$ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/latest | grep tag_name | cut -d '"' -f 4) && echo "Latest Peertube version is $VERSION"
</span></code></pre>
Download the new version and unzip it:</p>
$ cd /var/www/peertube/versions && \
</span>    sudo -u peertube wget -q "https://github.com/Chocobozzz/PeerTube/releases/download/${VERSION}/peertube-${VERSION}.zip" && \
</span>    sudo -u peertube unzip -o peertube-${VERSION}.zip && \
</span>    sudo -u peertube rm peertube-${VERSION}.zip
</span></code></pre>
Install node dependencies:</p>
$ cd /var/www/peertube/versions/peertube-${VERSION} && \
</span>    sudo -H -u peertube yarn install --production --pure-lockfile
</span></code></pre>
Copy new configuration defaults values and update your configuration file:</p>
$ sudo -u peertube cp /var/www/peertube/versions/peertube-${VERSION}/config/default.yaml /var/www/peertube/config/default.yaml
</span>$ diff /var/www/peertube/versions/peertube-${VERSION}/config/production.yaml.example /var/www/peertube/config/production.yaml
</span></code></pre>
Change the link to point to the latest version:</p>
$ cd /var/www/peertube && \
</span>    sudo unlink ./peertube-latest && \
</span>    sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest
</span></code></pre>
nginx🔗</a></h3>
Check changes in nginx configuration:</p>
$ cd /var/www/peertube/versions
</span>$ diff "$(ls --sort=t | head -2 | tail -1)/support/nginx/peertube" "$(ls --sort=t | head -1)/support/nginx/peertube"
</span></code></pre>
systemd🔗</a></h3>
Check changes in systemd configuration:</p>
$ cd /var/www/peertube/versions
</span>$ diff "$(ls --sort=t | head -2 | tail -1)/support/systemd/peertube.service" "$(ls --sort=t | head -1)/support/systemd/peertube.service"
</span></code></pre>
Restart PeerTube🔗</a></h3>
If you changed your nginx configuration:</p>
$ sudo systemctl reload nginx
</span></code></pre>
If you changed your systemd configuration:</p>
$ sudo systemctl daemon-reload
</span></code></pre>
Restart PeerTube and check the logs:</p>
$ sudo systemctl restart peertube && sudo journalctl -fu peertube
</span></code></pre>
Things went wrong?🔗</a></h3>
Change peertube-latest</code> destination to the previous version and restore your SQL backup:</p>
$ OLD_VERSION="v0.42.42" && SQL_BACKUP_PATH="backup/sql-peertube_prod-2018-01-19T10:18+01:00.bak" && \
</span>    cd /var/www/peertube && sudo -u peertube unlink ./peertube-latest && \
</span>    sudo -u peertube ln -s "versions/peertube-$OLD_VERSION" peertube-latest && \
</span>    sudo -u postgres pg_restore -c -C -d postgres "$SQL_BACKUP_PATH" && \
</span>    sudo systemctl restart peertube
</span></code></pre>

Owen Young's Blog - Dev

Caddy File Server Browser with URL Scheme

Makefile Template

Mastdon Development Setup

Mini Reset CSS

Nodejs Monorepo

Rclone Setup

FileBrowser Setup

Bazarr Setup

Caddy2 Setup for Debian

Debian Server Setup

How to check if there are uncommited changes in Github Actions?

qBittorrent setup for Debian

Config🔗</a></h2> Download directory, /data/Downloads</code></li>

Shadowsocks Rust Setup for Debian

Add as a system service🔗</a></h2> sudo</span> vim /etc/systemd/system/ss.service </span></code></pre> Note: Change username</code> to your own username</p> </blockquote>

Open BBR for Debian

Install PHP 8.0 On CentOS 7 / RHEL 7

Metube Setup

Nginx Setup for Debian

Optional Install certbot🔗</a></h2> Install snap🔗</a></h3> https://snapcraft.io/docs/installing-snapd</p> </blockquote>

Install snap🔗</a></h3> https://snapcraft.io/docs/installing-snapd</p> </blockquote>

Nodejs Setup for Debian

Peertube Setup with Caddy Server

What now?🔗</a></h3> Now your instance is up you can:</p> Add your instance to the public PeerTube instances index if you want to: https://instances.joinpeertube.org/</li>

Radarr Setup

Sonarr Setup