init

Author: HassanBahati

.env.example

@@ -0,0 +1,5 @@
+DEBUG=True
+CLOUDINARY_CLOUD_NAME = 'your_cloud_name'
+CLOUDINARY_API_KEY = 'your_api_key'
+CLOUDINARY_API_SECRET = 'your_api_secret'
+SECRET_KEY="your_secret_key"

.gitignore

@@ -0,0 +1,131 @@
+*.pyc
+*.pyo
+*.db
+.DS_Store
+.coverage
+local_settings.py
+secrets.py
+#static/
+media/
+migrations/
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+#dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# Secrets configuration
+secrets.py
+**/secrets.py

CONTRIBUTING.md

@@ -0,0 +1,105 @@
+# Contributing to the PyCon Africa Website
+
+We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
+
+## Setting up locally with venv
+### 1. Create virtual environment
+```sh
+python -m venv .venv
+```
+### 2. Activate a virtual environment
+While in the root project directory, activate a virtual environment by executing the following command based on your operating system;
+- For Unix/macOS run:
+
+```sh
+source .venv/bin/activate
+```
+- For windows run:
+```sh
+.venv/Scripts/activate
+```
+Install Requirements
+```sh
+pip install -r dev.requirements.txt
+```
+
+### 3. Environment Variables
+Create a `secrets.py` inside the [pyconafrica](https://github.com/PyconUg/pycon-africa/tree/main/pyconafrica) Django app directory, in the same directory as `settings.py` file. The `secrets.py` file will hold all the environment variables. Below are the default environment variables. 
+
+```
+  SCRETE_KEY='your_secret_key'
+  CLOUDINARY_URL='your_cloudinary_url'
+  CLOUDINARY_STORAGE = {
+      'CLOUD_NAME': 'your_cloud_name',
+      'API_KEY': 'your_api',
+      'API_SECRET': 'your_api_secret'
+  }
+  SILENCED_SYSTEM_CHECKS = ['django_recaptcha.recaptcha_test_key_error']
+```
+
+> Please reference, the [.env.example](https://github.com/PyconUg/pycon-africa/tree/main/.env.example) file for the expected environment variables.
+
+### 4. Managing Database Migrations
+With an active virtual environment, run the command below while in the root project directory to apply the current migrations to your database. By default, the migrations will be applied to an SQLite Database that will be autocreated in your root project directory.
+
+```sh
+python manage.py migrate
+```
+Create a superuser account
+```sh
+python manage.py createsuperuser
+```
+
+### 4. Running the 
+Run the server by executing the command below
+```sh
+python manage.py runserver
+```
+Log into the superuser account [http://localhost/accounts/login]
+Access the admin dashboard [http://127.0.0.1:8000/organizers/]
+Add an event year [http://127.0.0.1:8000/organizers/home/eventyear/]
+
+## We Develop with Github
+We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
+
+## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `master`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
+
+## Any contributions you make will be under the MIT Software License
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](https://choosealicense.com/licenses/mit/) that covers the project.
+
+## Report bugs using Github's [issues](https://github.com/PyConAfrica/pyconafrica-website/issues)
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/PyConAfrica/pyconafrica-website/issues/new); it's that easy!
+
+## Write bug reports with detail, background, and sample code
+**Great Bug Reports** tend to have:
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+People *love* thorough bug reports.
+
+## License
+By contributing, you agree that your contributions will be licensed under its MIT License.
+
+## References
+This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md)
+
+
+python3 manage.py shell < seeder.py  

README.md

@@ -0,0 +1,69 @@
+# [PyCon Africa](https://pycon.africa/)
+
+This is the source code for the https://pycon.africa/ website.
+
+## Running the site locally 
+
+1. Before you can run the site, you will need to install these requirements:
+
+* [Python 3.11](https://python.org)
+* [Poetry](https://python-poetry.org/)
+
+Once those are installed, you can do the following:
+
+
+2. Clone or fork the repo 
+
+Follow the guide on [GitHub Help - Fork a Repo](https://help.github.com/articles/fork-a-repo) to understand how to clone or fork a repo.
+
+
+3. Use poetry to install all the prerequisite Python packages
+
+```
+poetry install 
+```
+
+4. Get your database set up 
+
+```
+# open a poetry shell. This activates the virtual environment associated with the project 
+
+poetry shell
+
+# look at the shell prompt, it will look a little different. This means that the virtual environment is active
+
+# Then run the migrations 
+
+python manage.py migrate 
+```
+
+5. Now everything is set up; you can run the application
+
+```
+# If your virtual environment is not active, then activate it
+
+poetry shell
+
+# Run the server 
+
+python manage.py runserver
+
+```
+
+You'll see a whole lot of output in the terminal, it will look something like this:
+
+```
+Watching for file changes with StatReloader
+Performing system checks...
+
+System check identified no issues (0 silenced).
+April 12, 2024 - 06:16:26
+Django version 5.0.4, using settings 'pyconafrica.settings'
+Starting development server at http://127.0.0.1:8000/
+Quit the server with CONTROL-C.
+
+```
+
+Now open up a web browser and visit the url that was mentioned. It should be http://127.0.0.1:8000/
+
+That's all. Now the site is running.