init

.env.example

@@ -0,0 +1,40 @@
+APP_NAME=Cookie
+APP_DESCRIPTION=Code, Run and Share
+APP_KEY=)lj2@3@y&5ofgoekbt2c-4$$w2bedn@-(hr&i^!#%wype&wp6d
+APP_DEBUG_MODE=true
+APP_URL=https://cookie.sh
+APP_EMAIL=[email protected]
+
+CURRENT_THEME=default
+
+DB_CONNECTION=sqlite
+DB_HOST=127.0.0.1
+DB_PORT=3306
+DB_DATABASE=cookie
+DB_USERNAME=root
+DB_PASSWORD=root
+
+EMAIL_BACKEND=filebased
+MAIL_DRIVER=smtp
+MAIL_HOST=smtp.mailtrap.io
+MAIL_PORT=2525
+MAIL_USERNAME=null
+MAIL_PASSWORD=null
+MAIL_ENCRYPTION=null
+
+ALLOWED_HOSTS=*
+APP_TIMEZONE=UTC
+APP_LANGUAGE=en-us
+
+DJANGO_LOGGING_HANDLERS=
+DJANGO_LOGGING_LEVEL=warning
+DJANGO_LOGGING_PROPAGATE=false
+
+APP_LOGGING_HANDLERS=file
+APP_LOGGING_LEVEL=info
+APP_LOGGING_PROPAGATE=true
+
+REDIS_HOST=localhost
+REDIS_PORT=6379
+REDIS_DB=0
+REDIS_PASSWORD=

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Docs: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
+*       @clivern

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: clivern

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,18 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Development or production environment**
+ - OS: [e.g. Ubuntu 18.04]
+ - Python 3
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/boring-cyborg.yml

@@ -0,0 +1,92 @@
+---
+firstIssueWelcomeComment: "Thanks for opening your first issue here! Be sure to follow the issue template!"
+firstPRMergeComment: "Awesome work, congrats on your first merged pull request!"
+firstPRWelcomeComment: "Thanks for opening this pull request! Please check out our contributing guidelines."
+
+labelPRBasedOnFilePath:
+    "🚧 CI":
+        - .github/workflows/*
+
+    "🚧 CSS":
+        - "**/*.css"
+
+    "🚧 Configuration":
+        - .github/*
+
+    "🚧 Dependencies":
+        - Dockerfile*
+        - composer.*
+        - package.json
+        - package-lock.json
+        - yarn.lock
+        - go.mod
+        - go.sum
+        - build.gradle
+        - Cargo.toml
+        - Cargo.lock
+        - Gemfile.lock
+        - Gemfile
+
+    "🚧 Docker":
+        - Dockerfile*
+        - .docker/**/*
+
+    "🚧 Documentation":
+        - README.md
+        - CONTRIBUTING.md
+
+    "🚧 Go":
+        - "**/*.go"
+
+    "🚧 Rust":
+        - "**/*.rs"
+
+    "🚧 Java":
+        - "**/*.java"
+
+    "🚧 Ruby":
+        - "**/*.rb"
+
+    "🚧 HTML":
+        - "**/*.htm"
+        - "**/*.html"
+
+    "🚧 Image":
+        - "**/*.gif"
+        - "**/*.jpg"
+        - "**/*.jpeg"
+        - "**/*.png"
+        - "**/*.webp"
+
+    "🚧 JSON":
+        - "**/*.json"
+
+    "🚧 JavaScript":
+        - "**/*.js"
+        - package.json
+        - package-lock.json
+        - yarn.lock
+
+    "🚧 MarkDown":
+        - "**/*.md"
+
+    "🚧 PHP":
+        - "**/*.php"
+        - composer.*
+
+    "🚧 Source":
+        - src/**/*
+
+    "🚧 TOML":
+        - "**/*.toml"
+
+    "🚧 Templates":
+        - "**/*.twig"
+        - "**/*.tpl"
+
+    "🚧 Tests":
+        - tests/**/*
+
+    "🚧 YAML":
+        - "**/*.yml"
+        - "**/*.yaml"

.github/workflows/ci.yml

@@ -0,0 +1,24 @@
+name: CI Build
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      max-parallel: 4
+      matrix:
+        python-version: [3.7, 3.8, 3.9]
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Run make ci
+      run: |
+        pip install --upgrade pip
+        make config
+        make ci

.gitignore

@@ -0,0 +1,113 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+env/
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# 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/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# dotenv
+.env
+
+# virtualenv
+.venv
+venv/
+ENV/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+#  Local .terraform directories
+**/.terraform/*
+
+# .tfstate files
+*.tfstate
+*.tfstate.*
+
+# .tfvars files
+*.tfvars
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+
+db.sqlite3

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+## Contributing
+
+- With issues:
+  - Use the search tool before opening a new issue.
+  - Please provide source code and commit sha if you found a bug.
+  - Review existing issues and provide feedback or react to them.
+
+- With pull requests:
+  - We follow [Google Python Style Guide](http://google.github.io/styleguide/pyguide.html).
+  - Open your pull request against `main`.
+  - Your pull request should have no more than two commits, if not you should squash them.
+  - It should pass all tests in the available continuous integrations systems such as Github Actions.
+  - You should add/modify tests to cover your proposed code changes.
+  - If your pull request contains a new feature, please document it on the README.