Skip to content

πŸ’¬πŸ³ Rin Minase's AniDB API Service utilizing the latest version of Laravel and deployed to Heroku

License

Notifications You must be signed in to change notification settings

RinMinase/anidb-be

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Rin Minase's Anime Database
(Back-end API Service)

Laravel PHP

Introduction

Add info here

Table Of Contents

Getting Started

Environment variables setup

Return to the table of contents

  1. Database

    Definition of terms:

    • DB_HOST - docker container name of the database
    • DB_PORT - port used by the database
    • DB_DATABASE - database username
    • DB_PASSWORD - database password

    Notes : DB_HOST should use docker container name of db, by default this is 'anidb-pgsql', but yours could be different. You can check this by running docker ps then check the container name of the postgres container.

  2. Cloudinary

    • Fire up your browser and login your Cloudinary Account. If you have no account yet, you can create one for free.
    • After logging in, navigate to the Cloudinary Console to retrieve your Cloudinary URL
    • Copy the value of API Environment variable to CLOUDINARY_URL of your ENV file

Running the project

Return to the table of contents

  1. Download and install Docker.

  2. Clone the project, then install the dependencies

    git clone https://github.com/RinMinase/anidb-be.git
    cd anidb-be
  3. Run the necessary docker containers

    docker compose up -d
    docker compose exec php sh

    This runs only the necessary containers. As for running the optional containers, please see the section below.

  4. Inside the docker image, copy the env file, install the necessary dependencies and generate the necessary key for laravel

    cp .env.example .env
    composer install
    php artisan key:generate
  5. Generate the necessary API key and take note of this is as this is REQUIRED to access the API

    php artisan app:api-key

    or you can generate your own from any application, and add it under API_KEY in your .env file. Example:

    openssl rand -hex 36
  6. Generate the necessary root password key and take note of this is as this is REQUIRED to create admin accounts

    php artisan app:generate-root-password

    or generate your own, and add it under APP_REGISTRATION_ROOT_PASSWORD in your .env file.

  7. Cache the config file, then run the database migrations

    php artisan config:cache
    php artisan migrate:fresh --seed
  8. Fire up your browser and go to localhost.

Note: If you need to access the container run, docker compose exec php sh

Running the optional containers

Return to the table of contents

List of optional containers:

Name Description
dbui GUI for postgres using sosedoff/pgweb

You can run them individually by:

docker compose up -d <name>

Or run all of them by:

docker compose up -d --profile optional

Re-running the project

Return to the table of contents

  1. Navigate inside the php docker container

    docker compose exec php sh
  2. Run the migrations when necessary, then install the dependencies also when necessary

    php artisan migrate
    composer install
  3. Fire up your browser and go to localhost.

Running scheduled tasks

Return to the table of contents

  1. Navigate inside the php docker container [how]

  2. Run the command to run the scheduled tasks manually

    php artisan schedule:run

There are a few commands specific to running tasks:

Name Description
schedule:run Runs the scheduled tasks manually with respect to cron
schedule:work Runs the scheduler daemon / worker
schedule:list Lists the upcoming tasks to be run

Running the Swagger Generator / API Documentation Generator

Return to the table of contents

  1. Navigate inside the php docker container [how]

  2. Run the command to generate the documentations inside the container

    docs
  3. Fire up your browser and go to localhost/docs to open Swagger UI.

Running the Unit Tests

Return to the table of contents

  1. Navigate inside the php docker container [how]

  2. Run the command below:

    php artisan test

    or if you want to run a specific test module

    php artisan test --filter <Class name of Test File | function name>
    

    or if you want to run a specific single test

    php artisan test --filter test_function_name tests/Location/of/TestCase.php

Project shorthands / aliases inside the PHP Docker container

Return to the table of contents

This shortcuts were created to reduce the need to keep typing the same long commands over and over again.

Shortcut Long version
pa or artisan php artisan
docs composer docs
dump or da composer dumpautoload

Project Structure

Return to the table of contents

.
β”œβ”€β”€ app/                     # Application source code
β”‚   β”œβ”€β”€ docs.blade.php       # Swagger page template
β”‚   β”œβ”€β”€ index.blade.php      # Landing page template
β”‚   └── ...                  # Other application-related files
β”œβ”€β”€ bootstrap/               # Project initializers
β”‚   β”œβ”€β”€ app.php              # Framework bootstrapper
β”‚   β”œβ”€β”€ helpers.php          # Helper functions
β”‚   └── routes.php           # Route definitions
β”œβ”€β”€ config/                  # Laravel configuration files
β”œβ”€β”€ database/                # Database migrations and seeders
β”œβ”€β”€ docker/                  # Docker functions
β”‚   β”œβ”€β”€ php-config/          # PHP settings for docker
β”‚   β”œβ”€β”€ sites/               # Nginx sites for docker
β”‚   β”œβ”€β”€ nginx.dockerfile     # Nginx container docker file
β”‚   β”œβ”€β”€ php.dockerfile       # PHP container docker file
β”‚   └── ...                  # Other docker files
β”œβ”€β”€ public/                  # Project entry point
β”œβ”€β”€ tests/                   # Project test files
β”œβ”€β”€ .czrc                    # Commitizen configuration file
β”œβ”€β”€ docker-compose.yml       # Main docker file
β”œβ”€β”€ phpunit.xml              # Unit test configuration file
β”œβ”€β”€ Procfile                 # Heroku process file
└── ...                      # Other project files

Built with

Deployed to