Drum Roulette is a web application built using Next.js and TypeScript on the frontend. Its purpose is to facilitate the random assignment of US Military band percussionists to instruments for specific jobs.
- Randomly assign percussionists to instruments for jobs and ceremonies.
- Efficiently distribute workload among percussionists.
- User-friendly interface for managing percussion assignments.
- Next.js
- TypeScript
- PostgreSQL
To get a local copy of the project up and running, follow these steps:
- Clone the repository:
git clone [https://github.com/RubySpeeders/Drum-Roulette]
- Navigate to the project directory:
cd Drum-Roulette
- Install the dependencies:
yarn install
- Navigate to the FE directory:
cd client
- Install the dependencies:
yarn install
- Start the development server:
yarn dev
- Open your browser and access the application at
http://localhost:3000
To ensure a consistent code style across the project, we use Prettier as our code formatter. Please make sure to have the Prettier extension installed in your editor and configure it to match the project's Prettier settings.
If you prefer to manually format your code, you can run the following command before committing your changes:
npx prettier --write .
This command will format all files in the current directory and its subdirectories according to the Prettier configuration.
Please avoid committing code with formatting inconsistencies, as it helps maintain a clean and readable codebase.
Imports in .tsx
files should follow the following order:
- React/Next.js Imports
- Library Imports
- Type/Interface Imports
- Other Component Imports
- Styles or CSS Imports
- Constants or Config Imports
Contributions are welcome! If you'd like to contribute to this project, please make sure to follow the code formatting guidelines defined by Prettier. This ensures consistent code style and makes it easier to review and merge your contributions. If you'd like to contribute to Drum Roulette, please follow these guidelines:
- Clone the repository
- Create a new branch for your feature:
git checkout -b DR-[issue-number]-feature-name
- Make your changes and commit them:
git commit -m 'Add some feature'
- Push the changes to your forked repository:
git push origin DR-[issue-number]-feature-name
- Submit a pull request detailing your changes
Our front-end application is automatically deployed through the following process:
Version Control System:
- The source code for the front-end is version-controlled using Git.
Continuous Integration:
- We utilize continuous integration (CI) to automate the testing and building processes. The CI system monitors changes in the repository and triggers the build process.
Build Process:
- The build process is handled by Next.js and Vercel. On each merge to the
main
branch, Next.js compiles the application code, assets, and dependencies into a deployable format.
Deployment Trigger:
- Deployment is triggered when changes are merged into the
main
branch. This is achieved through the integration between Next.js and Vercel.
Deployment to Vercel:
- Vercel, our hosting provider, automatically deploys the application based on the changes in the
main
branch. The deployment includes updating the live version of the application.
While our current deployment process is triggered on each push to the main
branch, we are considering the implementation of a deployment schedule for more controlled releases. The schedule might involve deploying updates at specific times or on particular days to align with project milestones or user expectations.
This project is licensed under the MIT License.
If you have any questions or suggestions regarding the Musician Personnel Assignment Project, please feel free to reach out: