Skip to content
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

local-production.json not valid anymore after update to 6.x #6322

Closed
lonesomewalker opened this issue Apr 10, 2024 · 2 comments
Closed

local-production.json not valid anymore after update to 6.x #6322

lonesomewalker opened this issue Apr 10, 2024 · 2 comments
Labels
Status: Waiting for answer Waiting issue author answer

Comments

@lonesomewalker
Copy link

Describe the problem

After upgrading from 5.x to 6.x i was still missing the "studio" functionality, also the possibility to replace videos.
So i added these values to the local-production.json from another default installation.
Same intendation, all exact fine.

Now, studio is available, but the setting to replace videos is missing (not able to enable it in admin backend), also when i try to save the new values, i get a:

Incorrect request parameters: cache.storyboards.size, transcoding.webVideos.enabled, videoFile.update.enabled

Did i miss something?
The values are exact copied from a working instance, also i am wondering why the option to upload videos/overwrite them is not shown...

Thank you

Additional information

  • PeerTube version: 6.0.3
  • NodeJS version: docker latest
  • Ffmpeg version: docker latest
  • Redis version: docker latest
  • PostgreSQL version: docker latest
@Chocobozzz
Copy link
Owner

Hi,

local-production.json must not be updated manually.

When you upgrade, do you use docker compose down -v? (-v option is important)

@Chocobozzz Chocobozzz added the Status: Waiting for answer Waiting issue author answer label Apr 10, 2024
@lonesomewalker
Copy link
Author

Hi :-)

local-production.json must not be updated manually.

Yeah, i thought so, but this was the only file which contained these values.

I could SWEAR i did it with -v, but obviously... after doing it again, works like a charm.

Closed.

THANK YOU FOR YOUR SWIFT RESPONSE!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Waiting for answer Waiting issue author answer
Projects
None yet
Development

No branches or pull requests

2 participants