AmruthPillai

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.

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.

There's absolutely no extra setup necessary, if all of the services are running correctly. The error might just be related to networking. You can check out the hosted instance and take it for a spin to validate the product, and then when you have the time debug those errors with self-hosting it. I personally use the docker swarm compose template to deploy the production application and it works right out of the box.

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

Thank you :)

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 :)