-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"TypeError: objs.map is not a function" when trying to install PeerTube #1709
Comments
Please paste the redundancy section of your config file |
redundancy:
videos:
check_interval: '1 hour' # How often you want to check new videos to cache
strategies: # Just uncomment strategies you want
# -
# size: '1GB'
# # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances)
# min_lifetime: '48 hours'
# strategy: 'most-views' # Cache videos that have the most views
# -
size: '1GB'
# # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances)
min_lifetime: '48 hours'
strategy: 'trending' # Cache trending videos
# -
# size: '10GB'
# # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances)
# min_lifetime: '48 hours'
# strategy: 'recently-added' # Cache recently added videos
# min_views: 10 # Having at least x views |
It should be
|
Oh. Okay. I thought it was just cosmetic. Ah ah. I'll try now and tell you if something is wrong. Thanks! My issue is fixed. Thanks! |
I made the same mistake, thanks for the answer 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I followed steps to install PeerTube but once I had to run the command
sudo systemctl start peertube
I got an error from NPM:Steps to reproduce:
Additional information
PeerTube version or URL: 1.2.1
Server name/version: Debian 9
NodeJS version: 11.10.1
Link to server log if useful (journalctl or /var/www/peertube/storage/logs/):
npm logs:
The text was updated successfully, but these errors were encountered: