.env.example

@@ -1,5 +1,4 @@
 DATABASE_URL=postgres://postgres:mypassword@db-host:5432/databasename
-DATABASE_URL_LOCAL=postgres://postgres:mypassword@localhost:5432/databasename
 
 POSTGRES_USER=postgres
 POSTGRES_PASSWORD=postgres
@@ -11,8 +10,3 @@ GOOGLE_CLIENT_ID=
 GOOGLE_CLIENT_SECRET=
 GITHUB_CLIENT_ID=
 GITHUB_CLIENT_SECRET=
-
-VITE_WS_URL=
-
-UID=1000
-GID=1000

apps/api/src/lib/utils.ts

@@ -8,5 +8,3 @@ export const shuffleArray = <T>(array: T[]): T[] => {
   }
   return result;
 };
-
-// testing pre-commit hooks

documentation/notes.md

@@ -12,8 +12,7 @@ task description.
 4. if we go through a file, we'll do it slowly section by section, no matter how many sections
 5. how to name the current feature branch? also tell me when its time to git commit and provide a commit message
 6. if we have multiple options to do something, also always provide options that reflect current industry standards and best practices
-7. never assume anything! always ask for clarification!
+7. For every completed task, produce a ticket file in documentation/tickets/. Use ADR format (adr-) for decisions between options with long-term consequences. Use feat-/fix-/chore- for routine tasks. Always include a setup guide or summary of what was done. Suggest the filename.
-8. For every completed task, produce a ticket file in documentation/tickets/. Use ADR format (adr-) for decisions between options with long-term consequences. Use feat-/fix-/chore- for routine tasks. Always include a setup guide or summary of what was done. Suggest the filename.
 
 ## tasks