A Duty Roster planner for the SAF. It's tailored for unit uses, however the code is customizable. MIT License.
View Demo »
In SAF, soldiers are required to do duties, be it guard duty or 24hr ops duty. This project is tailored for unit, where they are required to do 24hr ops duty. The duty roster has these requirements:
- The duty roster should be spread out in a month of a calendar
- It is a 24-hour duty shift
- There must be a duty personnel for each day from the start to the end of the month
- There should not be any back-to-back duty for the same duty personnel.
- There should be an equal number of duties for everyone if possible.
- Personnel should be shuffled to avoid the first person always having the most number of duties
- Personnel can have block out dates where they should not have duties on the date they have blocked out.
- Duty roster generation with points algorithm
- Blockout dates management for personnel to avoid duties
- Duty swap request with another personnel
- Push notifications for reminders of duty and swap requests
To get a local copy up and running follow these simple example steps.
You'll first need a Supabase project which can be made via the Supabase dashboard.
-
Clone this project with Git
git clone https://github.com/ISnackable/saf-duty
-
Rename
.env.local.exampleto.env.localand update the following:NEXT_PUBLIC_SUPABASE_URL=[INSERT SUPABASE PROJECT URL] NEXT_PUBLIC_SUPABASE_ANON_KEY=[INSERT SUPABASE PROJECT API ANON KEY]Both
NEXT_PUBLIC_SUPABASE_URLandNEXT_PUBLIC_SUPABASE_ANON_KEYcan be found in your Supabase project's API settings -
You can now run the Next.js local development server:
pnpm dev
The server should now be running on localhost:3000.
As much as this project aims to set up as seamlessly as possible, due to some limitation to Supabase, there are some config that has to be done manually.
Navigate to Project Vault settings in your Supabase Dashboard.
- Create a new secret with the name
project_url. - The secret value should be your project's url, you can find the it through the Project API settings.
- Repeat for the secret
service_role_key.
To Enable Push Notification with Web Push. You will need to deploy the Supabase Edge Function and create the database webhook manually.
The database webhook handler to send push notifications is located in supabase/functions/push/index.ts. Deploy the function to your linked project and set the WEB_PUSH_PUBLIC_KEY, WEB_PUSH_PRIVATE_KEY & WEB_PUSH_EMAIL secret.
supabase functions deploy pushsupabase secrets set --env-file .env.local
Note: The Public and Private keys secrets must be generated using the alastaircoote/webpush-webcrypto package.
Navigate to the Database Webhooks settings in your Supabase Dashboard.
- Enable and create a new hook with the name
on_after_notifications_created. - Conditions to fire webhook: Select the
notificationstable and tick theInsertevent. - Webhook configuration: Supabase Edge Functions.
- Edge Function: Select the
pushedge function and leave the method asPOSTand timeout as1000. - HTTP Headers: Click "Add new header" > "Add auth header with service key" and leave Content-type:
application/json. - Click "Create webhook".
When a new row is added in your notifications table, a push notification will be sent to the user who has subscribed to push notification.
-
Note: There's also a cron job for daily duty reminder if a user is subscribed to push notification.
-- View all scheduled job. select * from cron.job; -- Or unschedule it if you want to disable it. select cron.unschedule('daily-roster-reminder');
Distributed under the MIT License. See LICENSE for more information.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent