Virtual hosts

Three states that look identical from outside

A port that does not answer can mean two very different things, and the difference matters when something is broken. The app reads the virtual host configuration and tells them apart.

  • Listening, the port answers right now
  • Apache is down, configured, but nothing is serving it
  • Disabled, the block is commented out in the configuration

The last one is the case that wastes an afternoon: a port you expected is simply absent, and nothing tells you why until you open the file.

Below the projects with a port come the folders in projects/ that have none, in alphabetical order, each with three buttons: Open, which opens it at virtualhost/projects/<name>/, Folder, and Assign a port.

projects
PROJECTS 6 listening · 1 disabled 4000 example1 example1/website 4002 example2 example2/frontend 4003 example3 disabled in configuration 4004 example4 example4/shop 4005 example5 example5/landing
Repositories

Which repo is this project, again?

Each project shows the repository it belongs to and the branch currently checked out. Click the name and it opens on GitHub. It works with GitLab and Bitbucket too, and with both HTTPS and SSH remotes.

  • Finds the repository even when the host points at a subfolder
  • Reads the git files directly, without running git on every redraw
  • Shows the branch, so a forgotten refactor branch is visible
repository
4000 example1 example1/website BRANCH refactor/acf-local-json opens on GitHub
New project

Start a new project without editing a single file

Adding a project used to mean four steps in three places: make the folder, write the virtual host block, find a free port, add a matching Listen line, restart Apache. Miss one and the site answers nothing, with no error to tell you why.

Start a new project in the app asks for three things: a name, the address of a GitHub repository, and a port. It creates the folder or clones the repository, writes the virtual host, opens the port and restarts Apache.

Assign a port does the same for a folder that is already there: the name stays the folder's, and nothing inside it is touched. A folder whose name contains a double quote, a backslash, a dollar sign or a control character cannot get a port, because Apache would misread it. Spaces and accents are fine.

The port is proposed, not imposed: the first free one after those already configured, commented out lines included, because a port switched off by hand still belongs to a project.

If the repository has a public/ folder, as Laravel and Symfony do, that becomes the document root. Serving the project from its own root would put the .env on the web.

Give it a repository. It is optional, and VXOST works without one, but the whole flow is built around having it: the project list shows which repository each project belongs to and on which branch, the name links straight to GitHub, and the time tracking report tells you where the hours went per repository. Set it at the start and everything else follows on its own.

new project
New project NAME my-project GITHUB REPOSITORY git@github.com:you/my-project.git PORT 4006 Create project my-project is on http://virtualhost:4006
New project and Assign a port write to the Apache configuration, and they are treated as such. Both files are copied, with the date in the name, before anything is written. The result is validated with httpd -t, and if the check fails the copies go back and Apache is never restarted. A malformed configuration would not take down the new project, it would take down every project on the machine.

Stop guessing which port is which

Everything above is read from your own configuration.

v9.26.17Updated November 2026Free · app and dashboard GPL