Updating to RC.6
Update an existing PhantomWP project to the RC.6 runtime.
Updating to RC.6
This guide is for people who already have a PhantomWP project and want to keep using it with the RC.6 runtime.
You do not need to update PhantomWP itself. Once RC.6 is live, the update work happens inside your project workspace or local Docker container.
Which Update Do You Need?
Use the option that matches where your project runs:
| Your project runs in... | What to update |
|---|---|
| GitHub Codespaces | Update the project infrastructure from the PhantomWP editor |
| Docker on your computer | Replace the local Docker container with the latest PhantomWP container |
| An older, unstable setup | Create a new RC.6 project and copy your site files across |
Your site content is not removed by the normal update flows. Still, commit or back up important work before updating.
Update a Codespace Project
Codespace projects include PhantomWP helper files that power the editor, preview, file sync, terminal, and visual tools. RC.6 can update those helper files from the editor.
- Open your project in PhantomWP.
- Wait for the Codespace to connect.
- In the editor toolbar, open More -> Infrastructure.
- If an update is available, click Update.
- Wait for the update log to finish.
- Reload the editor tab if the preview or terminal still looks stale.
This updates PhantomWP system files in the workspace. It does not rewrite your pages, components, images, or content.
Update a Local Docker Project
Local Docker projects run inside a PhantomWP container on your computer. To update, replace the container while keeping the same project storage.
- Open the project in PhantomWP.
- Open the local run/start dialog for the project.
- Copy the generated update command.
- Run that command in your terminal.
- Wait for Docker to pull the latest PhantomWP container and start it.
- Reopen the project editor.
The update command removes the old container, but it keeps the Docker volume or local folder that stores your project files. Your code stays in the project storage, not in the disposable container.
If Docker reports that the container name is already in use, stop and remove the old container, then run the update command again.
docker stop phantomwp-my-site
docker rm phantomwp-my-siteAfter the new container starts, you can watch its logs:
docker logs -f phantomwp-my-siteIf PhantomWP still shows an old project marker after the Docker container is current, open More -> Infrastructure and sync the marker. For local Docker projects, that marker only tells PhantomWP what project runtime it last saw; the actual runtime comes from the Docker container.
Create a New RC.6 Project from Old Files
If an older project has broken helper files, missing editor tools, or repeated connection problems, it may be cleaner to start a new RC.6 project and move your site files into it.
- Create a new project in PhantomWP.
- Choose Codespaces or Docker.
- Open the new project once so PhantomWP creates a fresh RC.6 workspace.
- Copy your site files from the old project into the new project.
- Reinstall dependencies if PhantomWP prompts you to do so.
- Preview the site and fix any missing assets or imports.
- Commit the migrated files.
Copy files that belong to your site, such as:
- pages and layouts
- components
- styles
- public images and assets
- content collections or data files
- custom configuration you intentionally changed
Do not copy old PhantomWP runtime or workspace setup folders from the old project. Let the new RC.6 project keep the fresh files PhantomWP created.
What Changes After Updating?
After updating, your project should use the RC.6 editor runtime. Depending on how old the project was, this may improve:
- editor connection reliability
- file creation behavior
- preview tools
- visual editing helpers
- screenshot and inspection tools
- local Docker startup behavior
Your published website does not change until you commit and deploy changes from the project.
Troubleshooting
The editor still asks me to update
Reconnect the project and open More -> Infrastructure again. If you are using Docker, confirm that you ran the generated Docker update command first, then sync the project marker.
Docker updated, but the preview will not load
Check the container logs:
docker logs -f phantomwp-my-siteIf dependency installation failed, open a terminal in the project and reinstall dependencies from the project root.
I accidentally removed the Docker container
That is normally okay. Recreate it from the PhantomWP dashboard using the generated command. As long as you keep the same Docker volume or local folder, your project files remain available.
The upgraded project is still unreliable
Create a new RC.6 project and copy only your site files across. This avoids carrying old workspace setup files into the new project.