Can you please assign this task to me?

Removing the Set up Documentation Alternative to Docker
Why that change

@jflory7 we should remove that option since we will likely use Docker to deploy the application
later too. The purpose of using Docker is it ensures everyone has the same environment.
It is easier for others to provide support and simulates what running it for real will be like
Using virtualenenv work, but I would consider it a more advanced option and much harder for
mentors to give support especially to upcoming applicants who opts to use virtual environment

Outcome

Remove the Alternative part and add further details to the docker part to include about redis and celery being installed automatically by docker and no need to install it manually

@feisal As far as I have knowledge, Docker is a suitable environment for development . Yes, it is great to use Docker in local setup as well, but many people will be interested in setting up environment in alternative way. Even minute changes in the files leads to building the docker , which is bit cumbersome process in itself, most people would got for alternative setup. So, there is no point of removing that part of Documentation. I hope this sounds reasonable! :)

@alishapapun yes i am getting you but then we need to broaden our scope and think of the future. yes you can run the app using the alternative but have we asked ourself about how far we can go on with this. when deploying the project live you will realize that docker is used for deployment and not pip environment. so what will happen to applicant using python environment?
so @jflory7 suggested to me as i was facing numerous issues trying to skip the docker part and setting up the project using environment with pip, that i should use docker to avoid app crushes during later days of deployment.

@alishapapun yes i am getting you but then we need to broaden our scope and think of the future. yes you can run the app using the alternative but have we asked ourself about how far we can go on with this. when deploying the project live you will realize that docker is used for deployment and not pip environment. so what will happen to applicant using python environment?
so @jflory7 suggested to me as i was facing numerous issues trying to skip the docker part and setting up the project using environment with pip, that i should use docker to avoid app crushes during layer days of deployment.

@feisal Let the decision be made by @jflory7 :)!

@alishapapun okey

I don't thing this a good idea , setting up a different development environment maybe a good option for someone. If we want extend the actual docker documentation fine but not removing one part just because it don't works for averyone. -1

@bt0dotninja It is not about not working for everyone but the fact the projects we will likely use Docker to deploy the application later too @jflory7 will explain more

I agree with @bt0dotninja, we will keep both options for now