Closed RaunoT closed 2 months ago
You might also want to consider using the Github Container Registry
I think we'll also need to create some sort of config screen to allow the admin to set the values that are currently set in the .env
file. Wondering regarding the best implementation. The easiest would probably be creating some sort of database and storing them there?
Unsure how to handle SSR, generateStaticParams and other build optimizations when using a published (built) Docker image. We need to have the relevant API keys etc. at build time for this. If anyone has any ideas regarding this, I'm open to suggestions. Wonder how overseerr and similar tools using Next.js solve this?
Could you add a "latest" tagged Docker image? Most applications dealing with Docker containers assume "latest" if a specific tag isn't provided.
Could you add a "latest" tagged Docker image? Most applications dealing with Docker containers assume "latest" if a specific tag isn't provided.
Good point, re-opening this.
Could it be possible to make it available for arm64 too? I've tried it on a raspberry pi before so I know it's compatible, having an image built for arm64 would be great! Thank you!
:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:
v2.0.0
Your semantic-release bot :package::rocket:
We should consider publishing an already built Docker image instead of having the user build it.