Merge pull request #106 from PFConnect/main

preview update with open-source

Author: dev-banane

.env.vite.preview

@@ -1 +1 @@
-VITE_SERVER_URL=http://localhost:9902
+VITE_SERVER_URL=https://canary.pfconnect.online

.gitattributes

@@ -0,0 +1,34 @@
+* text=auto eol=lf
+
+*.js     text eol=lf
+*.jsx    text eol=lf
+*.ts     text eol=lf
+*.tsx    text eol=lf
+*.json   text eol=lf
+*.css    text eol=lf
+*.md     text eol=lf
+*.yml    text eol=lf
+*.yaml   text eol=lf
+*.html   text eol=lf
+*.scss   text eol=lf
+*.less   text eol=lf
+*.sh     text eol=lf
+*.env*   text eol=lf
+
+* text=auto eol=lf
+
+*.png    binary
+*.jpg    binary
+*.jpeg   binary
+*.gif    binary
+*.ico    binary
+*.svg    text eol=lf
+*.woff   binary
+*.woff2  binary
+*.ttf    binary
+*.eot    binary
+*.pdf    binary
+*.zip    binary
+
+.editorconfig text eol=lf
+.prettierrc   text eol=lf

.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: PFConnect
+open_collective: # Replace with a single Open Collective username
+ko_fi: pfconnect
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/workflows/CI.yml

@@ -1,39 +1,39 @@
 name: lint
 
 on:
-    push:
-        branches:
-            - main
-        paths-ignore:
-            - 'README.md'
-    pull_request:
-        branches:
-            - main
-        paths-ignore:
-            - 'README.md'
+  push:
+    branches:
+      - main
+    paths-ignore:
+      - 'README.md'
+  pull_request:
+    branches:
+      - main
+    paths-ignore:
+      - 'README.md'
 
 jobs:
-    build:
-        runs-on: ubuntu-latest
+  build:
+    runs-on: ubuntu-latest
 
-        steps:
-            - name: Checkout repository
-              uses: actions/checkout@v4
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
 
-            - name: Setup Node.js
-              uses: actions/setup-node@v4
-              with:
-                  node-version: 20
-                  cache: 'npm'
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: 'npm'
 
-            - name: Install dependencies
-              run: npm ci --legacy-peer-deps
+      - name: Install dependencies
+        run: npm ci
 
-            - name: Run lint
-              run: npm run lint
+      - name: Run lint
+        run: npm run lint
 
-            - name: Run type check
-              run: npm run type-check
+      - name: Run type check
+        run: npm run type-check
 
-            - name: Build project
-              run: npm run build-only
+      - name: Build project
+        run: npm run build-only

.prettierrc

@@ -2,4 +2,4 @@
   "singleQuote": true,
   "tabWidth": 2,
   "trailingComma": "es5"
-}
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [support@pfconnect.online](mailto:support@pfconnect.online). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,63 @@
+# Contributing to PFControl
+
+Contributions are welcome!
+
+## How to Contribute
+
+- **Fork the repo** and open a pull request (to the `preview` branch so it can be tested on [canary.pfconnect.online](https://canary.pfconnect.online)).
+- **Follow the existing code style** and conventions.
+- **Run checks before submitting:**
+  - `npm run lint` to check for lint errors.
+  - `npm run format` to auto-format your code.
+  - `npm run type-check` to ensure type safety.
+- **For larger changes**, open an issue first to discuss your proposal.
+- **Keep pull requests focused**: One feature or fix per PR is preferred.
+
+## Commit Messages
+
+- Use clear, descriptive commit messages.
+- Follow [Conventional Commits](https://www.conventionalcommits.org/) if possible (e.g., `fix: correct typo in login page`).
+
+## Code Style
+
+- Use Prettier for formatting (`npm run format`).
+- Use ESLint for linting (`npm run lint`).
+- Prefer TypeScript for all new code.
+- Keep functions and files small and focused.
+
+## Testing
+
+- Add or update tests for new features or bug fixes.
+- Ensure all tests pass before submitting a PR.
+- If possible, add unit tests for backend and frontend changes.
+
+## Environment Variables
+
+- If you're adding features that require environment variables, update `.env.example` and document them in this README.
+- Never commit secrets or real credentials.
+
+## Documentation
+
+- Update documentation and comments as needed.
+- If you add a new feature, update the relevant docs or README sections.
+
+## Pull Request Checklist
+
+Before submitting a PR, please ensure:
+
+- [ ] Code compiles and builds (`npm run build`).
+- [ ] Lint and format checks pass.
+- [ ] Type checks pass.
+- [ ] PR description explains the change and references any related issues.
+
+## Reporting Issues
+
+- Search existing issues before opening a new one.
+- Provide clear steps to reproduce, expected vs. actual behavior, and screenshots/logs if possible.
+
+## Code of Conduct
+
+- Be respectful and inclusive.
+- No harassment, discrimination, or inappropriate behavior.
+
+Thank you for helping to make PFControl better!

Dockerfile

@@ -8,7 +8,7 @@ WORKDIR /app
 COPY package*.json ./
 
 # Install ALL dependencies (including dev dependencies for build)
-RUN npm ci --legacy-peer-deps && npm cache clean --force
+RUN npm ci && npm cache clean --force
 
 # Copy source code
 COPY . .
@@ -39,7 +39,7 @@ WORKDIR /app
 COPY package*.json ./
 
 # Install only production dependencies
-RUN npm ci --omit=dev --legacy-peer-deps && npm cache clean --force
+RUN npm ci --omit=dev && npm cache clean --force
 
 # Set NODE_ENV explicitly
 ENV NODE_ENV=production

Dockerfile.preview

@@ -8,7 +8,7 @@ WORKDIR /app
 COPY package*.json ./
 
 # Install ALL dependencies (including dev dependencies for build)
-RUN npm ci --legacy-peer-deps && npm cache clean --force
+RUN npm ci && npm cache clean --force
 
 # Copy source code
 COPY . .
@@ -39,7 +39,7 @@ WORKDIR /app
 COPY package*.json ./
 
 # Install only production dependencies
-RUN npm ci --omit=dev --legacy-peer-deps && npm cache clean --force
+RUN npm ci --omit=dev && npm cache clean --force
 
 # Set NODE_ENV explicitly
 ENV NODE_ENV=production