You can host PeerTube at:
- a subdomain, like
peertube.YOUR_DOMAIN(e.g.peertube.example.com) orvideos.YOUR_DOMAIN - or, at a top-level domain (e.g.
my-videos-service.com)
Now that you've decided what your hostname would be, you can substitute it below (in place of <your-peertube-hostname>) and in other configuration which will come later.
Follow these steps inside the playbook directory:
-
create a directory to hold your configuration (
mkdir inventory/host_vars/<your-peertube-hostname>) -
copy the sample configuration file (
cp examples/host-vars.yml inventory/host_vars/<your-peertube-hostname>/vars.yml) -
edit the configuration file (
inventory/host_vars/<your-peertube-hostname>/vars.yml) to your liking. See more in Configuring Services. -
copy the sample inventory hosts file (
cp examples/hosts inventory/hosts) -
edit the inventory hosts file (
inventory/hosts) to your liking
Doing the above preparation step, you're all set to proceed to Installing with our default recommended configuration.
However, you may wish to tweak a few other things before installing (or any time later):
-
configuring the database - if you'd like to use an external Postgres server - by default, we install Postgres in a container alongside PeerTube
-
configuring object storage - if you'd like to use an Object Storage service (like AWS S3) for storing your media files
-
configuring the reverse-proxy - if you'd like to expose your PeerTube service to the internet using another HTTP webserver - by default, we set up Traefik which will handle ports
80(http) and443(https)
You may also take a look at the various defaults/main.yml files in roles/ and see if there's anything you'd like to copy over and override in your vars.yml configuration file.
Once you've configured everything, you can proceed to Installing.
After installation, you can continue changing settings in vars.yml and re-running the installation step to make your server consistent with the configuration.