Skip to main content

Phoenix Starter

Deploy The Starter​

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.

Create an Elixir web prototype with Phoenix. This is a development workspace; use a Git-backed application for your finished production release.

  1. Open Services and select Phoenix Starter.
  2. Set a name and environment, then review capacity. The functional test used 150 mCPU / 512 MiB; this is not a production sizing recommendation.
  3. Choose Preview deploy, review the allowance and Confirm deploy.
  4. Follow Live Logs until the real application is ready, then open its URL.

Phoenix Starter deployment and capacity preview

Open The Application​

The generated URL should show the actual framework page, not an offline placeholder. A temporary 503 can mean startup has not finished.

Real Phoenix Starter application

Use The Terminal​

Open Terminal and wait for Connected:

cd /workspace/app
elixir --version
mix --version

Edit lib/moltern_starter_web/controllers/page_html/home.html.heex to change the homepage. Then use Stop service followed by Start service. Wait for the public page to respond before checking the change. Hex dependencies and compiled code can take time to restore.

A source edit in the real Moltern terminal

Work With Git And A Coding Agent​

Attach the Phoenix service under one coding agent's Resources settings and grant only the scope needed for the task. Use a private feature branch and a repository-scoped credential; repository access is not embedded in the image.

Pull and review the exact agent commit in /workspace/app, then run:

mix test

Confirm the generated page before and after restart. Remove temporary Git access and the agent attachment when the task is complete.

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

Codex completing the Phoenix application change in the Moltern terminal

Storage And Private Connections​

Project files live in this service's workspace under /workspace/app. Keep source in Git too; persistent storage is not a versioned backup. Connect only the private services this project needs through the connection controls.

Delete Service with Delete stored data requests runtime and workspace cleanup. Wait for cleanup to finish before assuming the allowance is released.

Troubleshooting​

The first startup generates the project without interactive prompts. An existing nonempty project directory is never silently erased. If startup fails, check Live Logs and repair the project before retrying.

The tested image reports a missing file-watcher warning. Do not rely on live reload: restart and refresh explicitly. This warning alone does not prove that the web application is unavailable.

Supported Workflow​

Use the workspace terminal or an attached coding agent to edit the Phoenix project, manage Mix dependencies, run mix test, preview the site, and synchronize changes with a private Git repository. Project files remain available after stopping and starting the workspace.

Before production, connect the intended database, review endpoint and secret configuration, and test channels, background work, and expected traffic.