Custom App Templates for Marketplace

Getting custom right from the start saves hours of debugging later. In this comprehensive guide, we'll cover everything from initial setup to production-ready configuration, including templates and apps considerations.

Prerequisites

• Root or sudo access to the server
• A registered domain name (for public-facing services)
• Basic familiarity with the Linux command line

Accessing the Marketplace

The default configuration works well for development environments, but production servers require additional tuning. Pay particular attention to connection limits, timeout values, and logging settings.

# Check marketplace app status
curl -s http://localhost:8080/health | jq .

# View application logs
docker logs -f custom-app --since 1h

# Restart the marketplace app
docker compose -f /opt/custom/docker-compose.yml restart

These commands should be run as root or with sudo privileges. If you're using a non-root user, prefix each command with sudo.

• Use SSH keys instead of password authentication
• Keep all software components up to date
• Use strong, unique passwords for all services
• Set up fail2ban for brute force protection
• Enable firewall and allow only necessary ports

Deployment Configuration

If you encounter issues during setup, check the system logs first. Most problems can be diagnosed by examining the output of journalctl or the application-specific log files in /var/log/.

# Check marketplace app status
curl -s http://localhost:8080/health | jq .

# View application logs
docker logs -f custom-app --since 1h

# Restart the marketplace app
docker compose -f /opt/custom/docker-compose.yml restart

Make sure to restart the service after applying these changes. Some settings require a full restart rather than a reload to take effect.

Common Issues and Solutions

• Service won't start: Check the logs with journalctl -xe -u custom. Common causes include port conflicts, missing configuration files, or insufficient permissions.
• Permission denied errors: Ensure files and directories have the correct ownership. Use chown -R to fix ownership and chmod for permissions.

Conclusion

This guide covered the essential steps for working with custom on a VPS environment. For more advanced configurations, refer to the official documentation. Don't hesitate to reach out to our support team if you need help with your specific setup.