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

Structuring our app data #6

Open
adoublef opened this issue Jul 31, 2022 · 2 comments
Open

Structuring our app data #6

adoublef opened this issue Jul 31, 2022 · 2 comments
Labels
question Further information is requested

Comments

@adoublef
Copy link
Contributor

I see that we have some migration files, have we documented how our data will be structures, what data is essential, and where it will be stored (server, client, cloud, hybrid)?

@pmoieni
Copy link
Contributor

pmoieni commented Jul 31, 2022

IMO it's better to keep application data on the server and avoid anything more complicated like s3 or cloud storage. A database like MySQL on the server would suffice.
That's why I used ent to generate migrations. We can add other fields to the User struct later. Like some info about the jam user is currently in or some other related stuff.

@adoublef
Copy link
Contributor Author

Do we have an ERD drawn up for the whole application? If not can we get something sorted so that we've a clear idea (especially for new starters).

@adoublef adoublef added the question Further information is requested label Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants