Move core from solar to this project
-
clone the complete django-setup of core in solar to this project -
test if the frontend of solar can still work with this project (locally) -
prepare PyPi publication of this project -
Have a look at Poetry for publishing and maintaining the project -
add further infrastructure like docker, gitlab-ci ... -
Rename the setting folder and project folder "the_social_network" to something like "social_network" and rename the application and each occurance of "core" to "the_social_network" for match the the poetry.toml
-
test if solar can work with the PyPi package of this project -
Document the-social-network (REAME, SWAGGER/POSTMAN, Django-Adim-Doc) -
think of further improvements: better database, How-to-integrate this project to other projects ... -
remove core in solar -
Think of this: Is it better to provide a service in a docker-env to allow other services to communicate with the core over an API or is it better to provide a PyPi package wich can be added to another django project. For code-injection on code level a PyPi project would be good, to provide whole services a shipping with docker would be better, because then the client gets a standalone and ready-to-run service whould could be used and communicated with over the internal API. Therefore, also think about a good API flow (input, output)