I believe they have made some changes to the OpenAI API since I last did the integration, will look into this tomorrow. The model is set to use gpt-3.5-turbo, but I would soon implement a dropdown to allow the user to select a model from a list.
I believe they have made some changes to the OpenAI API since I last did the integration, will look into this tomorrow. The model is set to use gpt-3.5-turbo, but I would soon implement a dropdown to allow the user to select a model from a list.
Interesting. It should be possible to do this without having to break the app or modify any of the code. You just need to ensure STORAGE URL and CHROME URL and not public addresses, but URLs that are accessible within your network (without basic auth).
Then it’s just a matter of implementing basic auth on the proxy layer (using nginx/Traefik/caddy). Or instead of basic auth, another strategy would be to block all requests from External IPs and only allow your home IP and the IP of the server itself.
Entirely up to the user. All of the templates adapt depending on whether there’s a picture or not, so no one’s experience is hindered. But it’s true, it is discouraged in some regions, for good reason, but also expected in many other regions or industries.
Yes, unfortunately it’s not a straightforward upgrade as there are a lot of things changed since V3 to V4. What I’d suggest is to extract or export your resume json from your running V3 instance and store it locally. Once you have v4 running, simply import the JSON back into the app.
Also it should be pointed out that the name of the image tag has changed. There is no client and server anymore, but just latest.
You can find the examples here: https://github.com/AmruthPillai/Reactive-Resume/tree/main/tools/compose
No, thank you! And please do let me know how your self-hosting experience was. If there’s anything I can do to simplify the process, happy to!
Please do let me know how it goes, and if there’s anything I can do to make the process more simpler :)
There’s a new env (described in the compose file also) called DISABLE_EMAIL_AUTH which would disable all email flows (login/register). If you need to allow email login but disable registration, that’s not really a feature yet, but please raise an issue on GitHub so I can track it. Will implement it as soon as I can.