Best Practices

Application Design

Do:

• Use descriptive, unique component labels
• Group related components visually on canvas
• Document applications with descriptions
• Use meaningful environment variable names

Don’t:

• Use generic names like “app” or “service”
• Hardcode secrets in environment variables
• Skip validation before publishing

Version Management

Do:

• Use semantic versioning (v1.0.0, v1.1.0, v2.0.0)
• Write meaningful version descriptions
• Test thoroughly in draft before publishing

Don’t:

• Skip version numbers randomly
• Publish untested configurations
• Delete all versions without backup

Security

Do:

• Use environment variables for configuration
• Set appropriate restart policies
• Use specific image tags (not latest)

Don’t:

• Store passwords in plain environment variables (use secrets)
• Run containers as root unnecessarily
• Grant excessive permissions

Team Collaboration

Do:

• Write clear descriptions and version notes

Don’t:

• Skip descriptions when publishing
• Ignore notifications about applications you use