[Bug] Disable new signups still not possible

[ektorasdj]

Is there an existing issue for this?

• [X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant

Self-Hosted

Current Behavior

Hello and thank you for this great tool! Can you please check it again? Another user confirmed it in the closed issue here : https://github.com/AmruthPillai/Reactive-Resume/issues/1592 and provided a thorough feedback of why this is happening. Thank you

Expected Behavior

No response

Steps To Reproduce

No response

What browsers are you seeing the problem on?

No response

What template are you using?

None

Anything else?

No response

[jasonmhite]

Can confirm, setting NODE_ENV=development and sign ups are disabled, but I can't log in with an existing account anymore, either. NODE_ENV=production and I can sign in again, but VITE_DISABLE_SIGNUPS is ignored and signups are re-enabled.

[aazam476]

Can we get an update on this issue?

[kgotso]

@AmruthPillai is there any fix for this? finding that I can not disable sign up which is weird

[ValorVie]

For me, I just need to git clone this project, and then add the VITE_DISABLE_SIGNUPS="true" environment variable during the build stage in the Dockerfile. After using this modified Dockerfile to build the image, I can disable signup when NODE_ENV=production.

Dockerfile example

...
# --- Build Image ---
FROM base AS build

ENV NX_CLOUD_ACCESS_TOKEN=$NX_CLOUD_ACCESS_TOKEN
ENV VITE_DISABLE_SIGNUPS="true"

COPY .npmrc package.json pnpm-lock.yaml ./
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile

COPY . .

RUN pnpm run build
...

[aazam476]

@AmruthPillai This issue has been unresolved for almost two months now. I cannot start my instance, and therefore am without a resume, without this fix. Can we please get a fix for this, or at least an update?

[guhanmathi]

I found a workaround

1. I created a resume and copied the shareable link for me to access it later

2. Then i recreated the stack with the below

   -- Email (Optional) --

   DISABLE_EMAIL_AUTH: true VITE_DISABLE_SIGNUPS: true

   SKIP_STORAGE_BUCKET_CHECK: false

3. Post this no login sections is visible in the login page, however the resume with the sharable link generated earlier is accessible via the link generated earlier.

4. To edit the resumes, I recreated the stack updating my docker compose with the below values.

   -- Email (Optional) --

   #DISABLE_EMAIL_AUTH: true #VITE_DISABLE_SIGNUPS: true

   SKIP_STORAGE_BUCKET_CHECK: false