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.
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.
I have always assumed that the two words mean the same but as specific to a region. There's no reason why you can't make your resume look like the way you want it to, especially because you can create custom sections that pertain to your industry.
The features you're asking for already exist in the app. You should be able to create a resume with all section items, and duplicate the resume for a specific job. Now, you have the option to hide certain items from each section or hide a section altogether.
There's also another interesting feature specific for this use case. You can create a base resume and then lock it, ensuring no further changes are made to it by mistake. Another feature is that you can add personal notes to each resume, for example a link to the job description you applied to.
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!
Thank you so much! :)
SMTP is optional, so is Sentry. If you don't include the env variable, the module isn't loaded in the app itself.
As for 2FA, it was just a few bits of code, so it adds almost zero weight to the instance. The project is very much catered to being self-hosted and meant for a single person to use. The rest are just nice features to have on a cloud instance, but they don't add any overhead to the server.
I will definitely look into the possibility of having this on, although I suspect my database would blow up if I were to implement this on the cloud.
Please do let me know how it goes, and if there's anything I can do to make the process more simpler :)
I've kept the Custom CSS section dormant for now because the templates themselves aren't too well adapted with custom classes/IDs etc to correctly work with custom CSS. I've kept it off for a later release until I can do it properly, but it'll definitely be a feature soon.
As for the issues you can't fix with CSS, I'm afraid the only way is to build the project locally and develop a template of your own, which isn't too difficult if you know TailwindCSS. I plan on writing a guide for this as well.