🌟 A social media made with Django and Python and Bulma. 🎉

  • By Visualway
  • Last update: Aug 30, 2022
  • Comments: 7

Vitary

A simple social media made with Django

Django CI CodeQL

Installation 🛠️

Get the source code 💻 

git clone https://github.com/foxy4096/Vitary.git

Go the the dir 📁 

cd Vitary

Add the enviroment variables ⚙️

In Powershell or terminal 💻 

touch .env

In .env add the following variables ➕ 

DEBUG=True or False
EMAIL_ADDRESS
EMAIL_PASSWORD
SITE_ID

Make a virtualenv 📡 

pip install virtualenv

and

virtuatenv venv

Install the dependencies 🔨 

pip install -r req.txt

Make Migrations 💿

On Windows:

python manage.py makemigrations

On *nix systemm:

python3 manage.py makemigrations

Migrate the database 🏃‍♂️

On Windows:

python manage.py migrate

On *nix systemm:

python3 manage.py migrate

Create the superuser 🤵

On Windows :

python manage.py createsuperuser

On *nix systemm:

python3 manage.py createsuperuser

Run the server 🚀

On Windows:

python manage.py runserver

On *nix systemm:

python3 manage.py runserver

Tools 🔧

Python the programming language

Git Version Control System

Visual Studio Code Free source code editor

Screenshot 📷

Homepage

signup

login

feed_home

profile

Github

https://github.com/Visualway/Vitary

Comments(7)

  • 1

    Website Crashes on Google Chrome Andriod

    Describe the bug When the website is accessed from Google Chrome Android The Site Crashes

    To Reproduce Steps to reproduce the behavior:

    1. Go to https://bit.ly/vitary on Google Chrome Android
    2. The website will cause the browser to crash

    Expected behavior The website should open as normally as it work on desktop Screenshots If applicable, add screenshots to help explain your problem.

    Desktop (please complete the following information):

    • OS: Windows 10
    • Browser: Microsoft Edge
    • Version: 96.0.1054.34 (Official build) (64-bit)
    • It works on Desktop and on other mobile browser like Mozilla Firefox

    Smartphone (please complete the following information):

    • Device: OPPO F11
    • OS: Android 11
    • Browser: Google Chrome
    • Version: 96.0.4664.104

    Additional context Works on any other browser like Mozilla Firefox etc

  • 2

    Refactored the code

    Pull Request Template

    Description

    Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

    Fixes # (issue)

    Type of change

    Please delete options that are not relevant.

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

    • [ ] Test A
    • [ ] Test B

    Test Configuration:

    • Firmware version:
    • Hardware:
    • Toolchain:
    • SDK:

    Checklist:

    • [ ] My code follows the style guidelines of this project
    • [ ] I have performed a self-review of my own code
    • [ ] I have commented my code, particularly in hard-to-understand areas
    • [ ] I have made corresponding changes to the documentation
    • [ ] My changes generate no new warnings
    • [ ] I have added tests that prove my fix is effective or that my feature works
    • [ ] New and existing unit tests pass locally with my changes
    • [ ] Any dependent changes have been merged and published in downstream modules
    • [ ] I have checked my code and corrected any misspellings
  • 3

    Bump minimatch from 3.0.4 to 3.0.8 in /apps/core/static/css

    Bumps minimatch from 3.0.4 to 3.0.8.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 4

    Fixed the edited bug this time for real :watch:

    Pull Request Template

    Description

    Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

    Fixes # (issue)

    Type of change

    Please delete options that are not relevant.

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

    • [ ] Test A
    • [ ] Test B

    Test Configuration:

    • Firmware version:
    • Hardware:
    • Toolchain:
    • SDK:

    Checklist:

    • [ ] My code follows the style guidelines of this project
    • [ ] I have performed a self-review of my own code
    • [ ] I have commented my code, particularly in hard-to-understand areas
    • [ ] I have made corresponding changes to the documentation
    • [ ] My changes generate no new warnings
    • [ ] I have added tests that prove my fix is effective or that my feature works
    • [ ] New and existing unit tests pass locally with my changes
    • [ ] Any dependent changes have been merged and published in downstream modules
    • [ ] I have checked my code and corrected any misspellings
  • 5

    Fixed update_date issue :watch:

    Pull Request Template

    Description

    Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

    Fixes # (issue)

    Type of change

    Please delete options that are not relevant.

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

    • [ ] Test A
    • [ ] Test B

    Test Configuration:

    • Firmware version:
    • Hardware:
    • Toolchain:
    • SDK:

    Checklist:

    • [ ] My code follows the style guidelines of this project
    • [ ] I have performed a self-review of my own code
    • [ ] I have commented my code, particularly in hard-to-understand areas
    • [ ] I have made corresponding changes to the documentation
    • [ ] My changes generate no new warnings
    • [ ] I have added tests that prove my fix is effective or that my feature works
    • [ ] New and existing unit tests pass locally with my changes
    • [ ] Any dependent changes have been merged and published in downstream modules
    • [ ] I have checked my code and corrected any misspellings
  • 6

    Create label.yml

    Pull Request Template

    Description

    Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

    Fixes # (issue)

    Type of change

    Please delete options that are not relevant.

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

    • [ ] Test A
    • [ ] Test B

    Test Configuration:

    • Firmware version:
    • Hardware:
    • Toolchain:
    • SDK:

    Checklist:

    • [ ] My code follows the style guidelines of this project
    • [ ] I have performed a self-review of my own code
    • [ ] I have commented my code, particularly in hard-to-understand areas
    • [ ] I have made corresponding changes to the documentation
    • [ ] My changes generate no new warnings
    • [ ] I have added tests that prove my fix is effective or that my feature works
    • [ ] New and existing unit tests pass locally with my changes
    • [ ] Any dependent changes have been merged and published in downstream modules
    • [ ] I have checked my code and corrected any misspellings
  • 7

    Create greetings.yml

    Pull Request Template

    Description

    This action will greet to new user who are new to contributing on this repository. 🚀 🦊

    Fixes # (issue)

    Type of change

    Created the action

    Checklist:

    • [x] My code follows the style guidelines of this project
    • [x] I have performed a self-review of my own code
    • [x] I have commented my code, particularly in hard-to-understand areas
    • [x] I have made corresponding changes to the documentation
    • [x] My changes generate no new warnings
    • [x] I have added tests that prove my fix is effective or that my feature works
    • [x] New and existing unit tests pass locally with my changes
    • [x] Any dependent changes have been merged and published in downstream modules
    • [x] I have checked my code and corrected any misspellings

Popular Tag

Related