A real-time chat application built with Laravel, Vue.js and Pusher Channels.

• Main Technologies
• Features
• Installation
  • Via Laravel Sail
  • Via Local Composer
• Environment Configuration
  • Database
  • Queue connection - Redis
  • Pusher Channels
  • File storage - AWS S3
  • Email service
  • OAuth 2.0 providers - Google & Facebook
  • Google Maps Platform
• Live Demo

• Laravel 8
• Vue.js 3
• Vuex
• MySQL 8
• Sass (SCSS)
• Pusher Channels
• Laravel Echo
• Redis
• Laravel Horizon

• One-to-one chat.
• Single-page application.
• Responsive design.
• User authentication:
  • Register and login.
  • Reset forgotten password.
  • Login with Google and Facebook accounts.
• User profile:
  • Edit user profile.
  • Profile pictures (avatars).
• Contacts:
  • User search.
  • Real-time users online/offline status.
• Chat:
  • Messages pagination with infinite scrolling.
  • User typing indicator.
  • Message read status.
  • Chat sounds.
  • Share user's current location.
  • Emoji picker.

Laravel Sail is a lightweight command-line interface for interacting with Laravel's default Docker development environment. Sail provides a great starting point for building a Laravel application using PHP, MySQL, and Redis.

Before you begin, you need to install Docker on your computer to use Laravel Sail. To do this, follow the instructions in the official Laravel documentation for your operating system. After installing Docker, set up your project by following these steps.

1. Clone the repository and open the project directory.

git clone [email protected]:lukaszwoznica/chatter.git && cd chatter

2. Install application dependencies using a small Docker container.

docker run --rm \
    -u "$(id -u):$(id -g)" \
    -v $(pwd):/var/www/html \
    -w /var/www/html \
    laravelsail/php80-composer:latest \
    composer install --ignore-platform-reqs

3. Run Laravel Sail containers.

vendor/bin/sail up -d

4. Create an environment configuration file and set required variables (see the Environment Configuration section for information on how to configure your environment variables).

cp .env.example .env

5. Generate Laravel application key.

vendor/bin/sail artisan key:generate

6. Install Node.js dependencies and compile frontend assets.

vendor/bin/sail npm install

7. Run database migrations and populate the database with some dummy data.

vendor/bin/sail artisan migrate:fresh --seed

8. Run Laravel Horizon to start processing queued jobs.

vendor/bin/sail artisan horizon

9. Additionally, you can run PHPUnit tests to check everything is working fine.

vendor/bin/sail test

10. At this point, the application should be ready to go at http:https://localhost/.

If you don't want to use Laravel Sail, you can install the application without using Docker containers. In this case, you must have PHP, Composer, Node.js and PhpRedis extension installed locally on your computer. You also need to take care of the database (it does not have to be MySQL, but it has to be supported by Laravel) and the Redis database for queues (optional - more information in the Environment Configuration section). If you meet the above requirements, you can proceed to the application installation process.

1. Clone the repository and open the project directory.

git clone [email protected]:lukaszwoznica/chatter.git && cd chatter

2. Install Composer dependencies.

composer install

3. The next steps are the same as steps 3-9 when installing the app with Laravel Sail. The only difference is that you don't need to use the vendor/bin/sail script in your commands.

cp .env.example .env # Set environment variables at this stage 
php artisan key:generate
npm install
php artisan migrate:fresh --seed
php artisan horizon
php artisan test

4. Start Laravel's local development server.

php artisan serve

5. At this point, the application should be ready to go at http:https://localhost:8000/.

This section describes how to configure environment variables in the .env file.

If you are using Laravel Sail, you don't need to change anything in the database configuration. Otherwise, you need to set up the database connection. The default database configuration is as follows.

DB_CONNECTION=mysql
DB_HOST=mysql 
DB_PORT=3306
DB_DATABASE=chatter
DB_USERNAME=root
DB_PASSWORD=null

By default, Redis is set as the queue driver. If you are using Laravel Sail, you don't have to configure anything. Otherwise, you need to set up your Redis database connection. Alternatively, you can set the queue driver to sync. When using this driver, queued jobs will be executed immediately (synchronously) within the current process.

QUEUE_CONNECTION=redis

REDIS_HOST=redis
REDIS_PASSWORD=null
REDIS_PORT=6379

Another service that needs to be configured is Pusher. It allows you to broadcast events through the WebSocket connection so that the application works in real time. Sign up on the Pusher website and create a new Channels application. Remember to turn on the client events in the app settings. Then fill in the following variables with the credentials of the newly created application (App Keys tab in Pusher dashboard).

PUSHER_APP_ID=
PUSHER_APP_KEY=
PUSHER_APP_SECRET=
PUSHER_APP_CLUSTER=

Chatter uses Pusher Channels webhooks to determine user activity status. Therefore, you need to enable them in the Channels' app dashboard. To do this, select the Webhook tab and add a new channel existence webhook. However, you will need the public URL for Chatter for this. To obtain it in a local development environment, you can use tunnel applications such as ngrok or Expose. Then set the webhook URL as follows.

https://your-public-url/webhooks/pusher

By default, this app uses Amazon S3 to store uploaded files. If you also want to use it, you need to register an AWS account and create a new bucket in the S3 service. Then set the appropriate environment variables in the .env file. To learn how to create an S3 bucket, see the official AWS S3 documentation.

MEDIA_DISK=s3 # Disk for storing uploaded files

AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_DEFAULT_REGION=
AWS_BUCKET=

If you don't want to use AWS S3, you can use the public disk and store files locally. To make uploaded files accessible from the web, you should create a symbolic link from public/storage to storage/app/public. You can do this with the command below.

vendor/bin/sail artisan storage:link
php artisan storage:link # if not using Laravel Sail

The application has a functionality related to sending emails containing a link to reset the user's password. Laravel Sail has a configured MailHog service. MailHog intercepts emails sent by the application during local development and provides a convenient web interface so that you can preview email messages in your browser. You may access the MailHog web interface at http:https://localhost:8025.

However, if you want to send real emails, you need to configure some email service. You can use API-based drivers such as Mailgun, Postmark, Amazon SES or any SMTP server. The connection with chosen email service should be configured using the following variables.

MAIL_MAILER=smtp
MAIL_HOST=mailhog
MAIL_PORT=1025
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
MAIL_FROM_ADDRESS=[email protected]
MAIL_FROM_NAME="${APP_NAME}"

Chatter allows you to authenticate with OAuth providers such as Google and Facebook. For this functionality to work fitly, you need to create Google and Facebook OAuth 2.0 credentials and put them as the values of the following variables.

GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET=

FACEBOOK_CLIENT_ID=
FACEBOOK_CLIENT_SECRET=

The last service that needs to be configured for the application to work correctly is Google Maps API. You will need to create an API key according to the instructions here and then set it as the value of the environment variable below.

MIX_GOOGLE_API_KEY=

A working live demo of Chatter is available here: https://chatter-laravel.herokuapp.com.

• The database is automatically refreshed and populated with dummy data every two hours in this demo.

• The first load of the website may take a while because the Heroku dyno may be asleep.

• You can create a new user account or log in using one of the following credentials: