Developer Tools

What this screen is for

Tools collects the utilities that support development without belonging to any one environment: setting up your machine, generating Dockerfiles from templates, scanning images, load testing, and running test suites.

Unlike Deploy, nothing here changes what is running. These are things you use before something ships, or about something that already has.

Before you start

Opening it

Tools in the sidebar. Each entry is gated separately, so a partly-populated submenu is normal.

📸 Screenshot Placeholder: The Tools submenu expanded in the sidebar. Mark: (1) Local Setup, (2) Templates Library, (3) Security Scanner, (4) Stress Testing, (5) Test Runner.

What is it for?

Developer Tools bring together practical utilities to make your daily work on the Fenwave platform easier.

Who is it for?

All developers using Fenwave

Accessing the Tools

1. Click on “Tools” or “Developer Tools” in the menu
2. OR go to /developer-tools

Available Features

1. Secret Generator

What it does: Create secure secrets (tokens, API keys, passwords)

How to use it:

1. Go to Tools → “Secret Generator”
2. Choose the type:
   • API Key: Random API key
   • Password: Secure password
   • Token: Unique token
3. Configure length and characters
4. Click on “Generate”
5. Copy the generated secret

Example usage:

• Create an API key for your service
• Generate a strong password
• Create a token for integration

2. Base64 Encoder/Decoder

What it does: Encode or decode data in Base64

How to use it:

1. Go to Tools → “Base64”
2. Encode:
   • Paste your text
   • Click “Encode”
   • Copy the result
3. Decode:
   • Paste the Base64
   • Click “Decode”
   • Read the original text

Example usage:

• Encode credentials for configuration
• Decode a Base64 secret

3. UUID Generator

What it does: Create unique identifiers (UUID/GUID)

How to use it:

1. Go to Tools → “UUID Generator”
2. Click on “Generate”
3. Copy the created UUID

Example usage:

• Unique ID for database
• Correlation ID for logs
• Session identifier

4. JSON Validator

What it does: Check and format JSON

How to use it:

1. Go to Tools → “JSON Validator”
2. Paste your JSON
3. Click on “Validate”
4. Results:
   • ✅ Valid: Correct JSON, nicely formatted
   • ❌ Invalid: Shows error and line number

Example usage:

• Check a JSON config file
• Format badly indented JSON
• Debug JSON syntax errors

5. Password Generator

What it does: Create secure passwords

How to use it:

1. Go to Tools → “Password Generator”
2. Configure:
   • Length (8-128 characters)
   • Include uppercase
   • Include numbers
   • Include symbols
3. Click on “Generate”
4. Copy the password

Example usage:

• Create a password for an account
• Generate a secret for authentication
• Password for database

6. Timestamp Converter

What it does: Convert between Unix timestamp and readable date

How to use it:

1. Go to Tools → “Timestamp Converter”
2. Timestamp → Date:
   • Enter the timestamp (e.g., 1704067200)
   • See the date: 2024-01-01 00:00:00 UTC
3. Date → Timestamp:
   • Select a date
   • Get the corresponding timestamp

Example usage:

• Debug logs with timestamps
• Convert API dates
• Calculate durations

7. Hash Generator

What it does: Create hashes (MD5, SHA-1, SHA-256)

How to use it:

1. Go to Tools → “Hash Generator”
2. Enter your text
3. Choose the algorithm:
   • MD5 (fast, less secure)
   • SHA-1
   • SHA-256 (recommended)
   • SHA-512 (very secure)
4. Click on “Generate”
5. Copy the hash

Example usage:

• Verify file integrity
• Create checksums
• Hash passwords (with salt!)

8. Diff Calculator

What it does: Compare two texts and see the differences

How to use it:

1. Go to Tools → “Text Diff”
2. Paste text 1
3. Paste text 2
4. Click on “Compare”
5. See differences in color:
   • Green: Additions
   • Red: Deletions
   • White: Unchanged

Example usage:

• Compare two config versions
• See changes in a file
• Debug data

Best Practices

✅ DO:

• Use strong passwords (16+ characters)
• Store secrets in Kubernetes Secrets (not in code)
• Use SHA-256 or SHA-512 for hashing
• Always validate JSON before using it

❌ DON’T:

• Store secrets in plain text in GitHub
• Use MD5 for security (obsolete)
• Reuse the same passwords
• Commit generated secrets

Keyboard Shortcuts

Use Cases

Case 1: Create a secret for Kubernetes

1. Generate a password:
   • Length: 32 characters
   • All character types
2. Encode in Base64:
   • Copy the password
   • Use the Base64 encoder
3. Create Kubernetes Secret:
   • Use the Base64 value
   • Via Kubernetes Admin

Case 2: Debug a timestamp in logs

1. Copy the timestamp from logs: 1704067200
2. Use Timestamp Converter
3. See the date: 2024-01-01
4. Understand when the event occurred

Case 3: Validate a JSON configuration

1. Copy JSON from file
2. Use JSON Validator
3. If error: see the problematic line
4. Fix and revalidate
5. Copy the formatted JSON

Security

⚠️ Important:

• Tools run in your browser (no data sent to server)
• Generated secrets are NOT saved
• Copy them immediately to a password manager
• Never share your secrets

Next Steps

• Create environments with Branch Environments
• Manage Kubernetes secrets with Kubernetes Admin
• Automate with Pipeline Builder

Need Help?

• 📚 Complete documentation
• 💬 Contact the platform team
• 🐛 Report issues

Scenario

Setting up a new machine and taking a service through to a load test.

1. Local Setup — install the agent and connect it. Nothing else here depends on it, but everything local does.
2. Templates Library — if the service has no Dockerfile, start from a template rather than a blank file.
3. Security Scanner — scan the built image before it reaches an environment, not after.
4. Deploy it to dev.
5. Test Runner — run the suite against it. Runs execute on Argo Workflows, so a run that never starts is a CI/CD problem rather than a test problem.
6. Stress Testing — only once it is correct. Load testing something that does not work yet measures nothing.

Step 6’s ordering is the point: correctness first, then behaviour under load.

When it doesn’t work

Next

• Local Setup — start here on a new machine