I did what I could man. I’m just one guy, a front-end guy even. I even made an announcement at the top of my GitHub readme looking for dev-ops or backend dev to help me make the self-hosting process better, but even with a project as popular as this, nobody came to help. So naturally I picked up as much I could myself and did it.

I honestly don’t know how it can be made easier though. It’s just a single service now, which needs to speak to other services. But if you still feel it’s convoluted, fork the repo and help me make it better, teach me what good self-hosted apps are supposed to look like.

I’m current taking a short break cause I’ve been working on this for more than a few months. Will be back soon with product guides, video tutorials and everything soon.

Is there a big difference from the old layout to the new one? I didn’t have a side by side comparison, but I tried to make the new templates a bit more flexible for custom CSS (hoping to introduce that feature soon).

Is there anything specific you’d like me to fix soon?

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.

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.

You can switch themes in the settings page, under “Profile”.

As reported by users who’ve sent me messages, but the whole section was meant to be taken sarcastically. Of course just the resume alone doesn’t do anything, it’s their skills. And personally, I’ve always wanted to have a logo cloud on my website, they have always looked cool to me.

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.

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.