Welcome to the Nebulatask project! This web application is built using Laravel, Inertia.js, and Vue.js to provide a modern and efficient platform for tracking and managing issues.
This project aims to provide a robust and user-friendly issue tracking system for better project management. It utilizes Laravel on the backend to handle server-side operations, Inertia.js for seamless single-page application development, and Vue.js for dynamic and reactive user interfaces.
- User Authentication: Secure user authentication system to ensure only authorized users can access and manage issues.
- Create and Manage Issues: Create, update, and delete issues with ease.
Before you begin, ensure you have the following software installed on your machine:
- Docker
- Docker Compose
- Node.js (>= 12)
- NPM
-
Start Devilbox:
cd /path/to/devilbox docker-compose up
-
Open the Devilbox shell with PHP running:
./shell.sh
-
Change to the project directory:
cd /path/to/nebulatask
-
Install PHP dependencies:
composer install
-
Install Node.js dependencies:
npm install
-
Generate an application key:
php artisan key:generate
-
Migrate the database:
php artisan migrate
Now, you should be able to access the application at https://nebulatask.dvlsite.
When using Vite for asset development, follow these steps to configure a proxy in Devilbox:
-
Create a new folder inside the Devilbox web root, for example,
hmr.nebulatask.dvlsite
. -
Inside the newly created folder, add a subfolder named
.devilbox
. -
Create a file named
backend.cfg
inside the.devilbox
folder. -
Add the following content to
backend.cfg
:conf:rproxy:ws:php:8081
Note: You may need to adjust the port (in this example,
8081
) based on its availability. -
Now, in the
vite.config.js
file of the Nebulatask project, modify the following properties under theserver
configuration.export default defineConfig({ server: { https: false, host: "0.0.0.0", port: 8088, // Set the same port as in the backend.cfg file hmr: { host: "hmr.nebulatask.dvlsite", clientPort: 443, protocol: "wss", https: true, }, }, // ... other configurations });
Ensure that the
port
property matches the port specified in thebackend.cfg
file.
Now, when you run Vite for asset development, it should use the Devilbox proxy configuration to access assets properly.