Coders Headquarters (CodersHQ) is a social platform for developers to grow, network, challenge themselves, and gain points by contributing and helping others in this community. This platform was built by the community and for the community. The essence of CodersHq is to inspire everyone to learn to code, share knowledge and learn together.
Currently the platform is at the alpha stage with a lot of the foundations being set. It is built using django and deployed using docker.
Have a look at the docs, we document everything over there. We plan to migrate from the docs to something more established, like readthedocs, once we have enough material to work with.
We also document the tasks in notion and you can have a look at the issues section to find out what we are working on.
Make sure you have Docker version 2+ and then do the following to build the stack and update the databse :
$ docker-compose -f local.yml build
$ docker-compose -f local.yml run --rm django python manage.py makemigrations
$ docker-compose -f local.yml run --rm django python manage.py migrate
$ docker-compose -f local.yml run --rm django python manage.py createsuperuser
Follow the rest of the README for more information and use /admin
to edit and create challenges.
The steps below will get you up and running with a local development environment. All of these commands assume you are in the root of your generated project.
If you're new to Docker, please be aware that some resources are cached system-wide and might reappear if you generate a project multiple times with the same name.
- Docker; if you don't have it yet, follow the installation instructions;
- Docker Compose; refer to the official documentation for the installation guide.
- (Windows) This repository can run on windows and was tested on WSL2. Once you have WSL2, and a linux kernel, installed and running you need to install docker and you should be good to go. (Tested on Docker version 20.10.7, build f0df350 and Windows OS Build: 19042.1052)
This can take a while, especially the first time you run this particular command on your development system::
$ docker-compose -f local.yml build
Generally, if you want to emulate production environment use production.yml
instead. And this is true for any other actions you might need to perform: whenever a switch is required, just do it!
This brings up both Django and PostgreSQL. The first time it is run it might take a while to get started, but subsequent runs will occur quickly.
Open a terminal at the project root and run the following for local development::
$ docker-compose -f local.yml up
You can also set the environment variable COMPOSE_FILE
pointing to local.yml
like this::
$ export COMPOSE_FILE=local.yml
And then run::
$ docker-compose up
To run in a detached (background) mode, just::
$ docker-compose up -d
As with any shell command that we wish to run in our container, this is done using the docker-compose -f local.yml run --rm
command: ::
$ docker-compose -f local.yml run --rm django python manage.py migrate
$ docker-compose -f local.yml run --rm django python manage.py createsuperuser
Here, django
is the target service we are executing the commands against.
When DEBUG
is set to True
, the host is validated against ['localhost', '127.0.0.1', '[::1]']
. This is adequate when running a virtualenv
. For Docker, in the config.settings.local
, add your host development server IP to INTERNAL_IPS
or ALLOWED_HOSTS
if the variable exists.
-
To create a normal user account, just go to Sign Up and fill out the form. Once you submit it, you'll see a "Verify Your E-mail Address" page. Go to your console to see a simulated email verification message. Copy the link into your browser. Now the user's email should be verified and ready to go.
-
To create an superuser account, use this command:
$ python manage.py createsuperuser
For convenience, you can keep your normal user logged in on Chrome and your superuser logged in on Firefox (or similar), so that you can see how the site behaves for both kinds of users.
Running type checks with mypy:
$ mypy codershq
To run the tests, check your test coverage, and generate an HTML coverage report:
$ coverage run -m pytest
$ coverage html
$ open htmlcov/index.html
Running tests with py.test
$ pytest
This app comes with Celery.
To run a celery worker:
cd codershq
celery -A config.celery_app worker -l info
Please note: For Celery's import magic to work, it is important where the celery commands are run. If you are in the same folder with manage.py, you should be right.
In development, it is often nice to be able to see emails that are being sent from your application. For that reason local SMTP server MailHog with a web interface is available as docker container.
Container mailhog will start automatically when you will run all docker containers.
Please check cookiecutter-django Docker documentation
for more details how to start all containers.
With MailHog running, to view messages that are sent by your application, open your browser and go to http://127.0.0.1:8025
We would like to thank and appreciate our extraordinary contributors 👏
Rashed Suwaidi 💻 🎨 📆 🚇 🚧 |
Abdulrahman Alblooshi 💻 🎨 |
Abdulkarim Suleiman 🖋 |
Musab 💻 |
arsxl 💻 🔌 |
DerpySmurf 💻 🎨 |
haralali 📆 |
Kajal Doshi 💻 🚇 |
Khushboo Gehi 📆 |
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!