feat(add): nodejs, goland and python

Author: CodeMeAPixel

.editorconfig

@@ -0,0 +1,19 @@
+# editorconfig.org
+root = true
+
+[*]
+indent_style = tab
+indent_size = 4
+tab_width = 4
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.yml]
+indent_style = space
+indent_size = 2
+tab_width = 2

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,27 @@
+# Code of Conduct
+
+## Our Commitment
+
+We are committed to providing a welcoming and inclusive environment for all contributors, regardless of background or experience level.
+
+## Expected Behavior
+
+- **Be respectful** - Treat all contributors with courtesy
+- **Be constructive** - Offer helpful feedback and solutions
+- **Be collaborative** - Work together to improve the project
+- **Be honest** - Acknowledge mistakes and learn from them
+
+## Unacceptable Behavior
+
+- Harassment, discrimination, or unwelcoming comments
+- Deliberate disruption of discussions
+- Sharing others' private information without consent
+- Any form of abuse or violence
+
+## Reporting Issues
+
+If you witness or experience a violation, please report it privately to the project maintainers by opening a confidential issue or reaching out directly.
+
+## Scope
+
+This Code of Conduct applies to all project spaces and interactions related to this repository.

.github/CONTRIBUTING.md

@@ -0,0 +1,80 @@
+# Contributing Guide
+
+## Adding a New Game Recipe
+
+### Structure
+Each game recipe lives in `games/{publisher}/{game}/`:
+
+```
+games/
+  rockstar/
+    fivem/
+      Dockerfile
+      start.sh
+      recipe.json
+      README.md
+      .dockerignore
+```
+
+### Required Files
+
+1. **Dockerfile** - Alpine-based container image (keep it minimal)
+2. **start.sh** - Server startup script with configuration handling
+3. **recipe.json** - Pterodactyl egg definition (PTDL_v2 format)
+4. **README.md** - Quick start and usage guide
+5. **.dockerignore** - Exclude unnecessary files from build context
+
+### Checklist
+
+- [ ] Create directory structure `games/{publisher}/{game}/`
+- [ ] Add Dockerfile using Alpine base
+- [ ] Create start.sh with environment variable handling
+- [ ] Define recipe.json with proper Pterodactyl format
+- [ ] Write clear README with examples
+- [ ] Add game to matrix in `games.yml`:
+  ```yaml
+  matrix:
+    game:
+      - minecraft
+      - rockstar/fivem
+      - rockstar/redm  # your new game here
+  ```
+- [ ] Push to develop branch (triggers workflow test)
+- [ ] Verify build succeeds in Actions
+
+### Code Standards
+
+- **Dockerfile**: Use Alpine 3.20, create non-root user, include health checks
+- **start.sh**: Validate inputs, map Pterodactyl variables, use bash `set -e`
+- **Environment Variables**: Support both new and legacy variable names for backward compatibility
+- **Logging**: Output errors with clear prefixes (ERROR, WARN)
+
+### Testing
+
+1. Build locally: `docker build -f games/{publisher}/{game}/Dockerfile -t test .`
+2. Run container with env vars: `docker run -e KEY=value test`
+3. Verify server starts and responds to health checks
+
+## Updating Go Recipe Versions
+
+Add versions to the matrix in `go.yml`:
+
+```yaml
+matrix:
+  version:
+    - "1.14"
+    - "1.15"    # add here
+```
+
+Then create `golang/{version}/Dockerfile`.
+
+## Pull Requests
+
+- Keep commits focused and descriptive
+- Reference issues when applicable
+- Test changes locally before pushing
+- Expect workflows to run on develop branch automatically
+
+## Questions?
+
+Open an issue with the `question` label.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug Report
+about: Report a bug in a recipe or workflow
+title: "[BUG] "
+labels: bug
+assignees: ''
+
+---
+
+## Describe the Bug
+
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+
+1. Run `...`
+2. Use environment variable `...`
+3. See error
+
+## Expected Behavior
+
+What should happen instead?
+
+## Actual Behavior
+
+What actually happens?
+
+## Environment
+
+- **Recipe**: (e.g., FiveM, Go v1.14, Minecraft)
+- **OS**: (e.g., Windows, Linux)
+- **Docker version**: (if applicable)
+- **Pterodactyl version**: (if applicable)
+
+## Logs
+
+```
+Paste relevant error logs or output here
+```
+
+## Additional Context
+
+Any other context that might help?

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,28 @@
+---
+name: Feature Request
+about: Suggest a new recipe, feature, or improvement
+title: "[FEATURE] "
+labels: enhancement
+assignees: ''
+
+---
+
+## Description
+
+What would you like to add or improve?
+
+## Use Case
+
+Why is this useful? What problem does it solve?
+
+## Implementation Ideas
+
+How do you think this could be implemented? (optional)
+
+## Examples
+
+Any examples or references? (links, code samples, etc.)
+
+## Additional Context
+
+Any other information?

.github/SECURITY.md

@@ -0,0 +1,38 @@
+# Security Policy
+
+## Supported Versions
+
+- **Current**: Latest version on `main` branch is fully supported
+- **Development**: `develop` branch is tested but may have unstable changes
+- **Past releases**: Fix security issues on request
+
+## Reporting Security Issues
+
+**Do not** open a public issue for security vulnerabilities.
+
+Instead, email security concerns to the project maintainers privately. Include:
+- Description of the vulnerability
+- Steps to reproduce (if applicable)
+- Potential impact
+- Suggested fix (if you have one)
+
+We will acknowledge receipt within 48 hours and work on a fix.
+
+## Security Best Practices
+
+When using game-recipes in production:
+
+1. **Keep images updated** - Rebuild regularly to get base image updates
+2. **Use trusted sources** - Only pull from `ghcr.io/nodebytehosting/` on GitHub Container Registry
+3. **Rotate credentials** - Change server licenses and API keys regularly
+4. **Monitor logs** - Set up monitoring for container health checks
+5. **Use secrets** - Never commit credentials; use Pterodactyl environment variables
+
+## Dependencies
+
+All recipes are based on Alpine Linux. Security patches are applied automatically when rebuilding.
+
+To check for known vulnerabilities:
+```bash
+docker run --rm -v /var/run/docker.sock:/var/run/docker.sock aquasec/trivy image ghcr.io/nodebytehosting/games:fivem
+```

.github/pull_request_template.md

@@ -0,0 +1,32 @@
+## Description
+
+Briefly describe what this PR does.
+
+## Type of Change
+
+- [ ] Bug fix (non-breaking change fixing an issue)
+- [ ] New recipe or feature (non-breaking change adding functionality)
+- [ ] Breaking change (fix or feature causing existing functionality to change)
+- [ ] Documentation update
+
+## Related Issues
+
+Fixes #(issue number) or relates to #(issue number)
+
+## Testing
+
+- [ ] Tested locally with `docker build`
+- [ ] Verified with environment variables
+- [ ] Checked workflow triggers
+- [ ] (If applicable) Updated recipe.json
+
+## Checklist
+
+- [ ] Code follows project standards
+- [ ] Documentation is updated
+- [ ] No unnecessary files added
+- [ ] Workflow files (if modified) are valid YAML
+
+## Notes
+
+Add any additional context or notes here.