Getting started with Developer Tools

This guide helps you deploy and configure a Developer Tools server on ServerPrism. You will learn how to order your server, understand the first boot process, and begin configuring your chosen tool.

Ordering on ServerPrism

1. Select a plan: Choose a plan with at least 2 GB RAM. For larger projects or more users, consider 4 GB or more, up to 16 GB. You can upgrade your plan later from your ServerPrism customer dashboard.
2. Pick a region: Select the data center location closest to you or your primary users for the best performance.
3. Choose your runtime: During the order process, select the specific developer tool you want to install (e.g., Code-Server, Forgejo, Gitea). This will be installed automatically.
4. Deploy: Complete your order, and your server will begin provisioning.

First boot

After deployment, your server will start automatically. The initial boot process installs all necessary components for your chosen developer tool. You can monitor the progress in the ServerPrism panel's Console tab.

Your server is ready when you see output indicating the service has started successfully, often showing a listening port or a success message specific to the tool (e.g., "Server started," "Listening on port XXXX").

Connecting / inviting players

Connection methods vary depending on the tool you chose:

• Code-Server, Forgejo, Gitea, Haste-Server, LanguageTool, Reposilite: These tools are typically accessed via a web browser. Your server's IP address and port will be displayed in the ServerPrism panel under the Network tab. For easier access, you can attach a free subdomain from your ServerPrism customer dashboard.
  • Example URL: http://your_server_ip:port or http://your-subdomain.serverprism.me:port
• Code-Server: Ensure you note down any generated password from the console output during first boot, as this is required to access your VS Code instance in the browser.

Configuration basics

Most initial configurations can be done through the web interface of your chosen tool once it's running. For server-level settings or environment variables, use the ServerPrism panel.

General Configuration Steps:

1. Access the Web Interface: Navigate to your server's IP and port in a web browser.
2. Initial Setup: Follow any on-screen prompts for first-time setup, such as creating an admin user, setting a site title, or configuring storage.

Specific Tool Configuration Notes:

• Code-Server: The initial password might be printed to the console on first boot. You can often change this or configure authentication via environment variables in the Startup tab of the ServerPrism panel (e.g., PASSWORD=yournewsecurepassword).
• Forgejo / Gitea: During the initial web setup, you will configure the database, admin user, and repository root path. Ensure the database settings match the default (usually SQLite for simplicity, or external if you configure it).
• Haste-Server: Configuration files are typically located in the server directory (e.g., config.js). You can edit these using the ServerPrism panel's File Manager or via SFTP. Common settings include storage backend (filesystem or Redis) and port.
• LanguageTool: Configuration is often done via server.cfg or startup parameters. Check the Startup tab in the ServerPrism panel for available variables to customize memory, language models, or port.
• Reposilite: Configuration is primarily handled by reposilite.yml in the server's working directory. Use the File Manager to set up users, repositories, and security settings.

Many tools allow you to adjust settings via Startup Variables in the ServerPrism panel. Check the Startup tab for available options specific to your selected runtime.

Common issues

• "Site can't be reached" or connection refused:
  • Check server status: Ensure your server is running in the ServerPrism panel.
  • Firewall: ServerPrism automatically handles basic firewall rules for your service. If you've modified anything manually or are using a non-standard port, ensure it's open.
  • Port mismatch: Verify you are using the correct port listed in the ServerPrism panel's Network tab.
• Code-Server password lost: If you forget the Code-Server password, you can often reset it by setting a new PASSWORD environment variable in the Startup tab of your ServerPrism panel and restarting the server.
• Disk space warnings (Forgejo/Gitea): If you host many repositories, you might eventually run low on disk space. You can upgrade your server plan from your ServerPrism customer dashboard to get more storage.
• Slow performance:
  • RAM: If your tool is running slowly, especially under load, you might need more RAM. You can upgrade your server plan from your ServerPrism customer dashboard.
  • Configuration: Review your tool's specific documentation for performance tuning (e.g., database optimization for Forgejo/Gitea, JVM settings for LanguageTool/Reposilite).

If you encounter persistent issues, gather your server ID and relevant logs from the Console tab and open a support ticket at https://serverprism.com/tickets.

Next steps

Once your developer tool is running, you can explore further customization:

• Integrations: Most tools offer integrations with other services (e.g., Git hooks for Forgejo/Gitea, extensions for Code-Server).
• Runtime Switching: If you decide a different developer tool would better suit your needs, you can switch runtimes directly from the Startup tab in your ServerPrism panel. This allows you to install a different tool without reordering your server.
• Backup: Regularly back up any critical data, especially for code hosting solutions like Forgejo and Gitea. You can download files via SFTP or the ServerPrism File Manager.