Skip to main content

Go Starter

When To Use It​

Public development URL

The starter page is publicly accessible. Workspace permissions do not add application login protection. Add your own authentication before using sensitive data, and use a production deployment for a finished application.

Use this starter for Go HTTP services and small APIs. Project files live in the service workspace. It is a development server, not a production deployment of your finished application.

Deploy In Moltern​

  1. Open Services, select Go Starter, and choose a name and environment.
  2. Select capacity. The September 30 customer journey used 50 mCPU / 128 MiB with one instance. This is a tested starting size, not a load-tested minimum.
  3. Choose Preview deploy, review the impact, then Confirm deploy.
  4. Wait for deployment and open the application. First startup can take several minutes.

Go Starter capacity and deployment preview in Moltern

Use The Application​

Open the service URL to see the Go starter. Open /health to receive {"status":"ok"}. An ingress error or a connection failure is not a successful startup.

Real Go Starter application after deployment and a persistence test

Edit From The Terminal​

Open the service's Terminal tab. After it connects:

cd /workspace/app
go version

Edit main.go and keep dependencies in go.mod. The starter runs go run . on startup. Stop and start the service after changing the server; do not launch a second process on its existing port.

Keep useful code in Git as well. A service workspace is not a substitute for a versioned backup. Never paste credentials into screenshots or commit them into the project.

Restart And Storage​

Use Stop service, then Start service. Wait until the public application responds again; the status label can update before startup has finished.

Files under /workspace persist across runtime replacement. Changes elsewhere in the container may not. To remove the service and its stored files, select Delete Service, keep Delete stored data selected, and complete account confirmation. Retained files continue to count toward storage.

Work With Git And A Coding Agent​

The runtime includes Git and SSH tooling, but it does not contain a repository credential. Use a repository-scoped credential and a private feature branch.

  1. Add the Go service under the coding agent's Resources settings.
  2. Grant only the access required for the task, then apply the policy update.
  3. Let the agent commit its change to the private feature branch.
  4. Pull the exact commit into /workspace/app and review the diff.
  5. Run go test ./... and check /health before restarting.
  6. Remove temporary Git credentials and unnecessary agent access afterward.

Go workspace selected as a scoped resource for a Moltern coding agent

Codex completing the Go application change in the Moltern terminal

Private databases or APIs must also be attached explicitly. Configure the Go client and credentials in the application after making the connection.

Troubleshooting​

  • Still starting: inspect Live Logs for package downloads or compilation.
  • Package download failed: review the recorded error, then retry after connectivity is restored. An offline placeholder page is not a working framework.
  • 503 just after restart: startup is not complete. If it persists, check logs rather than repeatedly restarting.
  • No terminal connection: wait for the runtime to start, then reconnect.

Supported Workflow​

Use the workspace terminal or an attached coding agent to edit the Go project, run go test ./..., preview the service, and synchronize changes with a private Git repository. Project files remain available after stopping and starting the workspace.

Before production, connect required services, review timeouts and graceful shutdown behavior, and test the application with representative traffic.

Next Steps​

Commit the application to Git and deploy it through Moltern Applications when it is ready to run beyond the development workspace.