- Home
- Changelog
What changed in 9.26.17
Every version from 9.26.9 to 9.26.17: protected VXOST files, projects that follow the Finder, PHP versions of VXOST's own, Close port and a cleaner list of project folders.
On 9.26.8, the app installs every version from 9.26.9 to 9.26.17 as one update: choose Check for updates from the VXOST icon in the menu bar, then Install. The disk image for 9.26.17 contains all of them.
Version 9.26.17
Built on 16 November 2026.
What it changes
- PHP versions window: the description of each version uses the full width of its row, is no longer cut off, and is in your language. The title of a row stays on one line when there is room. Installed versions keep their description when the list cannot be reached
- The subtitle of the main window now lists the PHP versions you have, for example PHP 8.2, 8.4, 8.5, instead of the version of the base package
- The setting for who can reach your projects now also reads the
Listenlines inhttpd-vhosts.conf, and changes them together with the others - When VXOST cannot read the configuration, the setting and the setup assistant say so and name the file
- A new project gets a port the local network can reach only when all your ports are open to it. With ports set by hand in different ways, or a configuration VXOST cannot read, it gets a port only this Mac can reach
- The setup assistant no longer rewrites ports you set by hand unless you choose an option in its network step, and it says so. It says that macOS will ask for your password only when it will
Good to know
- VXOST reads
httpd.conf,httpd-ssl.confandhttpd-vhosts.conf. AListenline in another file that you included by hand is not seen
Version 9.26.16
Built on 16 November 2026.
What it changes
- Close port: Esc now cancels the confirmation, like Return. No key confirms it
- If the database of a new project cannot be created, the reason now appears in an alert. The project itself is still created
- When a line of the Apache configuration continues on the next one with a backslash, VXOST now reads it the way Apache does, in the project list, in Close port and in the setting for who can reach your projects. Close port refuses when removing a block would change what a continued line swallows
- When a configuration file contains a control character VXOST cannot read, the setting for who can reach your projects changes nothing and says which file, and a new project gets a port that only this Mac can reach
- After closing a port VXOST also tries it on the IPv6 loopback address
- A project description that ends with a backslash no longer breaks the creation of the project
- The port proposed for a new project also takes into account
Listenlines written by hand for IPv6 or split over two lines
Version 9.26.15
Built on 16 November 2026.
What it changes
- On the port of a project, a folder without an index page now shows its listing in the VXOST look, dark or light like your system, instead of the bare Apache listing. The style travels inside the page: nothing is fetched from anywhere. Port 80 is unchanged
- A project created by the wizard starts with a page in the same look, with its port and the name of the file to replace. Projects that already exist are not touched
- In Urdu, the language menu of the dashboard opened outside the screen and the page scrolled sideways. Both are fixed
- The setting for who can reach your projects, and the port proposed for a new project, now also recognise a
Listenline written by hand in lowercase
Good to know
- The update replaces
www/projects/.htaccess, which is a VXOST file. If you had changed it by hand it is replaced all the same, and the update says so
Version 9.26.14
Built on 15 November 2026.
What it changes
- A project row has a new Close port button, also in the right-click menu. After you confirm and type your password, VXOST removes the virtual host and the
Listenline of that port, keeps a copy of both files, checks the configuration and restarts Apache. The folder, the files and the databases are not touched. The project goes back to the folders without a port, where Assign a port gives it one again - VXOST closes a port only when it understands every
Listenline and every virtual host in the configuration. If something was written by hand in a form it does not know, it changes nothing and tells you to close the port by hand. After the restart it tries the port: if it still answers, it tells you instead of saying it is closed - When an operation you asked for fails, the reason now appears in an alert, not only in the status line
- The PHP version of a project is now a button with a menu arrow, and PHP versions is also in the VXOST menu at the top of the screen
Version 9.26.13
Built on 15 November 2026.
What it changes
- A new window, PHP versions, in the menu bar lists the extra PHP versions VXOST offers for Macs with Apple Silicon. Install downloads a signed package from vxost.com, checks it, and asks for your password once. Update and Remove are in the same window. Nothing is downloaded until you click, and a version that an active project uses cannot be removed
- With the app open, VXOST starts again the PHP versions your active projects use when Apache comes up, so a project on an extra PHP version no longer answers 503 after the Mac restarts
- A project that runs on a PHP from Homebrew keeps it while that PHP is running, also when the same version arrives from VXOST, and the app says so. The project moves to the one from VXOST when you choose the version again, or the next time VXOST starts PHP for it
- Changing the PHP version of a project, the exposure to the network and the certificate renewal failed every time in 9.26.12 and put everything back as it was. They work again
Version 9.26.12
Built on 14 November 2026.
What it changes
- The commands VXOST runs with your Mac administrator password now start from a clean environment that the app writes itself, instead of the one the app was started with
- The app refuses code loaded into it from outside, and the files it prepares for a change (project ports, network exposure, the certificate) are checked again before they are installed. If one was changed in between, nothing is installed and the app says so
- The scripts of the stack that run as administrator check what they are about to change before they start
Good to know
- Security check and Backup may ask once whether VXOST may control Terminal
Version 9.26.11
Built on 14 November 2026.
What it changes
- The app recognises PHP versions installed inside VXOST (for Macs with Apple Silicon), next to the PHP 8.2 that Apache loads, and lists them for a project like a Homebrew version. When the same version is installed both ways, the list shows the VXOST one
- New project now starts the PHP version you chose before it creates the project, so the first page no longer answers 503
- The update engine can install and remove a PHP version from a signed package
Version 9.26.10
Built on 14 November 2026.
What it changes
- A folder you create, rename or delete in your projects folder now shows up in the Projects section right away, without reopening VXOST. A project made with New project or Assign a port appears as soon as it is created
Version 9.26.9
Built on 13 November 2026. On 9.26.8 it arrives as part of the single update to 9.26.17.
What it changes
- The VXOST files in
/Applicationsare protected: they are owned by the system (root) and are no longer writable by the admin group. Your projects inwww/projectsstay yours, and you work in them as before - Editing
httpd.conf,php.ini,my.cnforhttpd-vhosts.confby hand now needs your Mac administrator password, for example withsudo nano /Applications/VXOST/vxostfiles/etc/php.ini(Ctrl+O then Return to save, Ctrl+X to leave). VXOST has no password of its own. Everything the app does (a new project, the PHP version of a project, exposure to the network, the certificate, the services, updates) already asked for the password, and works as before - The Projects section of the app also lists the folders in
www/projectsthat have no port of their own, below the projects that have one, with three buttons: Open, which openshttp://virtualhost/projects/<name>/, Folder, and Assign a port - Assign a port gives an existing folder a port of its own, without touching what is inside it. Spaces and accents in the name are fine. 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
- A commented-out project block whose folder no longer exists is no longer listed as disabled; one whose folder still exists still is. So the commented example project,
my-siteon port 4000, is no longer shown in the app, and new installations no longer have it - The notes shown at the end of a build update are in the app's language
- The dashboard FAQ and guides say that editing a configuration file needs your Mac administrator password, and the guides that had you create files directly in
www/now usewww/projects - The app and the dashboard show version 9.26.9
Good to know
- Services stop for a few seconds while it installs, and macOS asks for your password
- Sites kept directly in
www/, outsideprojects, are protected like the rest of the VXOST files: move the folder intowww/projects - If you replaced a folder inside the VXOST installation with a symbolic link (for example
etc/extraorlogs, linked to another disk or to your dotfiles), or put a link directly invxostfiles, the update stops and is undone, and the message reads bin/fix_rights failed. This lists the links to folders, and lines saying Permission denied can be ignored:find /Applications/VXOST/vxostfiles -type l -not -path '*/www/projects/*' -exec test -d {} \; -print. Three of them belong to VXOST and stay:lib/terminfo,lib/instantclientandlib/icu/current. Replace any other one with a real folder, then update again. Links to single files deeper in the installation, and anything insidewww/projects, are not affected - That command lists links to folders. A link placed directly in
vxostfilesstops the update even when it points to a file, and this lists those:find /Applications/VXOST/vxostfiles -maxdepth 1 -type l. When the update stops, the top folder is already protected, so removing a link placed directly invxostfilesneedssudo, for examplesudo rm /Applications/VXOST/vxostfiles/logs(this removes the link, not what it points to) - If an update is undone, the files may already be protected even though the version did not change. Nothing is lost, and the app works the same
- After the update
VXOST.appis owned by root, as since 9.26.8
Version 9.26.8
A build update for 9.26.7: choose Check for updates from the VXOST icon in the menu bar, then Install. On an earlier version, get to 9.26.7 first.
What it changes
- The setup assistant said the daily check was the only network request VXOST makes. Since 9.26.7 the app also asks for the signed list of build updates, and downloads one when you click Install: the note now says so, in fifteen languages
- The app and the dashboard show version 9.26.8
Good to know
- Services stop for a few seconds while it installs, and macOS asks for your password
- If anything fails, the update is undone. If it cannot be undone completely, or the Mac loses power halfway, the app offers Restore interrupted update at the next start
- After this update
VXOST.appis owned by root, because the installer that replaces it runs with administrator rights: moving it to the Trash then asks for your password
Version 9.26.7
This version still installs from the disk image. Updating from an earlier version? It is one command.
Build updates, from the app
- Check for updates in the menu bar menu now also looks for build updates: changes to the app, the dashboard and the control scripts, installed without downloading the disk image again
- Nothing installs by itself. The window shows the version and what changes, and waits for Install; the download has a progress bar and can be cancelled
- Every update is signed. The app checks size, fingerprint and signature before asking for your password, and the installer verifies the signature again, and the fingerprint of every file inside
- Only the files that changed are replaced, each after a safety copy. If a step fails, that update is undone and everything is put back as it was, and after a power cut the app offers Restore interrupted update
- A build update never touches the projects themselves or your databases. In the projects folder it can only replace the two files VXOST keeps there,
index.phpand.htaccess, after a safety copy - The servers themselves (Apache, PHP, MariaDB, OpenSSL) are not updated this way yet: Core update is in the menu, marked as coming
The dashboard on a new installation
- On a fresh install of 9.26.5 or 9.26.6,
http://virtualhost/redirected to itself and the dashboard could not be reached. The package now ships withvirtualhostas the default site on port 80 - The update script adds that block to an installation that lacks it, after a safety copy, and leaves your virtual hosts file alone if it is already there
Smaller fixes
- The app checked the database port by opening a connection and dropping it, which filled the MariaDB log with
Aborted connection
lines. It now reads the list of listening ports instead - Starting MariaDB no longer writes an
Access denied
line to its log - The update script no longer sets aside the
index.phpand.htaccessof your projects folder when they are identical to the new ones, and its instructions for going back say exactly what to type - The package no longer carries Finder leftovers (
.DS_Store)
Version 9.26.6
A full review of the three repositories, line by line. Updating from an earlier version? It is one command.
FTP is no longer part of VXOST
- ProFTPD is gone from the package, the app and the control script. To move files, use SFTP (Remote Login in System Settings) or git
- If FTP was on in your previous installation, the update script tells you at the end
Apache stops when asked
- The servers started from the app ignored the stop signal, so stopping Apache waited 20 seconds and then forced it. They now start with normal signals
- An Apache started by an earlier version keeps the old behaviour until it is restarted once with the new app
One operation at a time
- At power-on the automatic start and the app could start Apache at the same moment. The control script now waits for an operation in progress
The HTTPS certificate
- Updating keeps your certificate and key
- With mkcert installed, the app offers to make the certificate trusted, warns you 30 days before it expires and renews it with one click; your password is asked only when you choose to
Security fixes
- Reading a project log with your password could run a command chosen by the name of the log file
- The logs folder was writable by the projects' PHP code; PHP now logs to
logs/php/ - Folders whose name starts with a dot are no longer served when Apache is opened to the local network
- None of these could be reached from the internet: the package listens on this Mac only
Smaller fixes
- A root password with
#or a trailing space no longer locks the app out of the database - The setup assistant shows every step that failed before closing; a client report never falls back to all projects
vxost reloadno longer fails every time, and a full disk no longer leaves an empty configuration file behind- The dashboard FAQ is rewritten in fifteen languages, and the log viewer shows PHP errors
Version 9.26.5
Two fixes found by updating a real Mac with 69 projects. Updating from an earlier version? It is one command.
MariaDB no longer stops by itself
- Started from the app, MariaDB was shut down 15 to 25 minutes later, usually while you were away from the Mac: macOS stopped it together with the privileged command that had started it. It now runs on its own, like Apache
Your projects keep their owner
- The permission repair on the first start after an update gave every project file to root: git refused the repositories and Apache could not write uploads and caches. The repair now leaves the projects folder alone
Smaller fixes
- The About window shows the real release month
- The disk image explains what to do if macOS stops the update script because it is not notarised
Version 9.26.4
A change to the update script, found while updating a Mac with 46 GB of projects. Updating from an earlier version? It is one command.
Updating needs no extra space for your projects
- The update script moves your projects folder into the new installation instead of copying it: no time, no disk space, and the same path as before
- If anything fails halfway, the projects go back into the old installation; databases are still copied, and the old ones stay untouched
Safer when interrupted
- After a power loss during an update, running the script again tells you where your projects and databases are, with the commands to put them back
- If your projects folder lives on another disk, the script stops before changing anything
Version 9.26.3
Fixes found in a second review, and a safe way to update. Updating from an earlier version? It is one command.
Updating is one command
- The disk image carries a script that stops the servers, keeps your current installation untouched as VXOST-old-<date>, installs the new one and brings your projects, databases, virtual hosts and ports into it
- It checks everything before it changes anything, never deletes anything, and puts the old installation back if something fails halfway
Stopping really stops
- MariaDB is stopped even when its supervisor keeps restarting it, always with the orderly shutdown and never a forced kill
- Apache that ignores the stop signal is stopped after 20 seconds, and the app says it had to force it
Time tracking
- A damaged timesheet no longer crashes the app: it is moved aside, never overwritten, and the app tells you where it is
- If hours cannot be saved, the app says so, keeps trying, and asks before quitting
Safer on a shared network
- If you open Apache to your local network, archives in your projects folder and the list of your projects are still reachable from this Mac only
Smaller fixes
- A project created but not verified is shown as a warning, not as a success
- The build checks more reliably that the package is signed and contains no private key
Version 9.26.2
No new features: things that were broken, unverified, or more open than they should be, found in a long independent review. Updating from an earlier version? Read this first: do not drag the new folder over the old one, and do not replace only the app.
Apache starts on a Mac that never had it
- The HTTPS certificate is created before the configuration check, not after it: on a fresh install the check no longer fails for a certificate nothing had created yet
- Stopping Apache no longer waits for the certificate
Stop and restart say what really happened
- No more "ok" while a service keeps running: stop and restart check the process and the log
- When the outcome cannot be verified, the app says so instead of reporting success
Closed by default
- Apache, MariaDB and ProFTPD listen on this Mac only; opening Apache to the local network is a choice in the app
- The dashboard's diagnostic pages (phpinfo, ports, file browser, database) answer this Mac only
- Compressed database dumps, SQLite files and Markdown notes are never served
- The server no longer announces its Apache, OpenSSL and PHP versions
Time tracking
- "Start" always records on the project you chose, even if a project folder appears or disappears while the menu is open
- If the timesheet cannot be read, new hours are refused with an explanation instead of being lost when the app quits
Smaller fixes
- pecl and pear work again, and phar.phar opens
- The app runs on macOS 13 Ventura and 14 Sonoma, as promised
- Styled error pages in the dashboard
Version 9.26.1
The first release of the native app, alongside the redesigned dashboard.
A native app for the menu bar and the Dock
- Native arm64 and x86_64 binary of about 2 MB, with no Rosetta and no dependency
- Lives in the menu bar and in the Dock, both offering the same functions
- Start, stop, restart and reload Apache, MySQL and ProFTPD
- Service state from
pgrepand a real TCP probe, so MySQL no longer looks stopped when it is not - Privileges through the native macOS prompt: no helper installed,
sudoersuntouched
Projects and ports
- Reads the virtual hosts and shows which project answers on which port
- Tells listening, stopped and commented-out virtual hosts apart
- Shows the Git repository and branch of each project, and opens it in the browser
- Opens a project in the browser or reveals it in the Finder
Time tracking
- Timers per project, several at once, each with its own pause
- Automatic pause after ten idle minutes and before the Mac sleeps, backdated to when the inactivity began
- History by day with totals per project
- Summaries copied for an email, or exported as CSV with decimal hours
- Data kept in a readable JSON file under Application Support
Interface
- Window built with Auto Layout: resizable and full screen from the green button
- Dark, light and automatic themes, remembered between launches
- Log viewer that reads only the tail of a file, so multi-gigabyte logs open instantly
- Right-to-left layout for Urdu
Dashboard
- Complete restyling of the web root around one design system built on the VXOST accent orange
- Contrast checked against WCAG for every colour pair, on the composited surfaces and not only on the page background, with every pair kept above 7:1
- Ports and addresses viewer, collapsible PHPInfo, phpMyAdmin themed to match
- Fifteen languages generated from one template and one string table
- Accessibility throughout: skip links, focus rings, 44px targets, reduced motion
Known limitations
- The app is ad-hoc signed and not notarised, so macOS blocks the first launch
- Creating a virtual host from the app is planned but not implemented yet
- The dashboard's PHP tools are being brought to all fifteen languages