search

jazzbassjohnson / team_manager

A basic platform for managing a team member
0 stars 0 forks source link

Project feedback #1

Open adamstep opened 2 months ago

adamstep commented 2 months ago

Hi @jazzbassjohnson , I ran into this issue while following the instructions to build/run the docker containers using Docker compose. Seems like something is wrong with the frontend image build steps. Please advise.

 > [team_manager-frontend 4/5] RUN yarn install:
#0 0.319 yarn install v1.22.19
#0 0.331 info No lockfile found.
#0 0.335 [1/4] Resolving packages...
#0 6.485 warning eslint > @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
#0 6.654 warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
#0 6.671 warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
#0 6.714 warning eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
#0 6.755 warning eslint > file-entry-cache > flat-cache > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
#0 8.682 [2/4] Fetching packages...
#0 23.20 error @typescript-eslint/eslint-plugin@7.18.0: The engine "node" is incompatible with this module. Expected version "^18.18.0 || >=20.0.0". Got "18.17.1"
#0 23.21 error Found incompatible module.
#0 23.21 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
failed to solve: executor failed running [/bin/sh -c yarn install]: exit code: 1
jazzbassjohnson commented 2 months ago

Hi @adamstep ! Based on these logs it looks like we need to update the node version in the docker container. I've updated the frontend/Dockerfile and pushed up the change.

I'm not sure if this info was passed along but this project is incomplete. I was able to build most of the backend to support the project but the UI was never completed.

adamstep commented 2 months ago

Thanks, it worked properly now. I didn't see documentation for login, can you share the creds with me?

jazzbassjohnson commented 2 months ago

You can paste this in a .env file at the root:

VITE_API_URL=http://localhost:8000/ POSTGRES_DB=team_manager_db POSTGRES_USER=root POSTGRES_PASSWORD=password SECRET_KEY=django-insecure DJANGO_SETTINGS_MODULE=backend.settings DEBUG=True

On Mon, Jul 29, 2024 at 2:45 PM Adam Stepinski @.***> wrote:

Thanks, it worked properly now. I didn't see documentation for login, can you share the creds with me?

— Reply to this email directly, view it on GitHub https://github.com/jazzbassjohnson/team_manager/issues/1#issuecomment-2257064589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASMHKS4HIAB6DA72BALPALZO2ZZLAVCNFSM6AAAAABLU3UVESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGA3DINJYHE . You are receiving this because you were mentioned.Message ID: @.***>

-- Gary Johnson (510) 827-8318

adamstep commented 2 months ago

Hi @jazzbassjohnson , I do see that file in the root. The problem is, when I get the app up and running, I'm not sure how to test the API or the frontend. I created a superuser using manage.py to log in, but I still can't authenticate or find the frontend. The README doesn't have any hints as to how to proceed. See attached video.

https://github.com/user-attachments/assets/4f9130f1-9ef9-4158-b1dc-3f6099912194

jazzbassjohnson commented 1 month ago

My apologies for missing this messages. I think the notification email was filtered out of my primary inbox.

I'm going to pick this up tomorrow morning.