Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup django project #53

Merged
merged 3 commits into from
Sep 14, 2023
Merged

Setup django project #53

merged 3 commits into from
Sep 14, 2023

Conversation

WillNilges
Copy link
Collaborator

No description provided.

@WillNilges WillNilges changed the title Setup django project [DRAFT] Setup django project Sep 8, 2023
Copy link
Collaborator

@andybaumgar andybaumgar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I love how organized this is. Added a few comments.

meshdb/meshapi/serializers.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
meshdb/meshapi/permissions.py Outdated Show resolved Hide resolved
meshdb/meshdb/settings.py Outdated Show resolved Hide resolved
meshdb/meshapi/views.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
@WillNilges
Copy link
Collaborator Author

hmmm do we want to prevent people from signing up with duplicate emails and phone numbers?

@WillNilges WillNilges changed the title [DRAFT] Setup django project Setup django project Sep 10, 2023
@andybaumgar
Copy link
Collaborator

hmmm do we want to prevent people from signing up with duplicate emails and phone numbers?

Good idea, that makes sense. Should we do it in another PR? I think what we have now will be fine for development testing purposes.

Copy link
Member

@Andrew-Dickinson Andrew-Dickinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work Willard. I left a lot of comments inline, but as a general note I'll say we don't have to resolve all of them right now. I'm happy to create separate GitHub issues to track this stuff, (especially the high-level comments) so that we can merge this PR quickly and unblock other dev work. Just wanted to leave them here so we don't loose track of them

.github/workflows/no_debug_allowed.yaml Show resolved Hide resolved
entrypoint.sh Outdated Show resolved Hide resolved
meshdb/meshdb/settings.py Outdated Show resolved Hide resolved
Dockerfile Outdated Show resolved Hide resolved
docker-compose.yaml Show resolved Hide resolved
meshdb/meshapi/views.py Outdated Show resolved Hide resolved
meshdb/meshapi/views.py Outdated Show resolved Hide resolved
meshdb/meshapi/views.py Outdated Show resolved Hide resolved
meshdb/meshapi/models.py Outdated Show resolved Hide resolved
meshdb/meshapi/permissions.py Outdated Show resolved Hide resolved
@Andrew-Dickinson
Copy link
Member

hmmm do we want to prevent people from signing up with duplicate emails and phone numbers?

Good idea, that makes sense. Should we do it in another PR? I think what we have now will be fine for development testing purposes.

We need to be careful however, we are inheriting a dataset that does not have a uniqueness constraint on those fields, so we can never assume it, even if we bar it going forward

@andybaumgar
Copy link
Collaborator

andybaumgar commented Sep 11, 2023

hmmm do we want to prevent people from signing up with duplicate emails and phone numbers?

Good idea, that makes sense. Should we do it in another PR? I think what we have now will be fine for development testing purposes.

We need to be careful however, we are inheriting a dataset that does not have a uniqueness constraint on those fields, so we can never assume it, even if we bar it going forward

I was imagining this would happen as a function when a request comes in vs an actual database constraint. We could check if someone already has an active node. I imagine Brian, Daniel etc. will brake this rule though.

@quoncc
Copy link
Collaborator

quoncc commented Sep 12, 2023

This looks very good, seems to be organized far better than what we had before.

@WillNilges
Copy link
Collaborator Author

Closes #51

Models and some serializers

It functions

Need to write the rest of the serializers and endpoints, figure out how to talk
to postgres, and confirm that validation works the way I want it to.

The rest of the serializers and endpoints™

This should be the basics. No guarantee of correctness. Need to check on
validation and what have you, yada yada.

Generics are cool

Basic admin or naw authentication

Fine tune permissions a lil bit?

IDK if this is correct, but I think I'm starting to understand how auth
works.

I need to go to bed.

Ops scaffolding

More ops scaffolding

A lot of this is going to have to change because I am going to bring in
nginx

Ops scaffolding 3: The epic conclusion

I added an Nginx server so that we could serve static files and gave a
best guess at configuring CSRF trusted origins.

Update README.md

Fun badges

Remove boilerplate

Andy Comments

black?

Make sure debug mode is OFF!!!

Whoops missed a 'lint'

Remove more boilerplate

Andrew Comments Part 1
Andrew Comments 2/2

outer meshdb -> src

Update Dockerfile

Andrew was right

Update .env.sample

Update debug instructions

Fix dockerfile and the user serializer
@WillNilges
Copy link
Collaborator Author

beeg squash

@WillNilges WillNilges merged commit f989c01 into main Sep 14, 2023
2 checks passed
@WillNilges WillNilges deleted the willnilges/django branch February 19, 2024 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants