In the standard use of the Bol Processor, all data is stored in the "bolprocessor" folder located in the "htdocs" folder created by MAMP or XAMPP. Read the installation instructions for more details. This is acceptable in most cases because Bol Processor data is basically made of text files that do not take up much space.
However, there are a number of reasons why a user might want to store data in locations other than the "bolprocessor" folder:
- Need for additional space
- Avoid storing data on the startup disk
- Sharing data with other applications and other users
- Sharing data via a cloud device (e.g. DropBox).
A procedure for moving the entire "bolprocessor" folder is described in the installation instructions: for example, in the MacOS environment. Unfortunately, as of today, the relocated installation does not work on MacOS with XAMPP after a reboot, unless the "BolProcessorInstaller.pkg" installer is run again. The same problem might exist in both Windows and Linux environments where MAMP or XAMPP is used.
In fact, there is not much interest in relocating the entire "bolprocessor" folder. Moving data folders outside this folder will suffice. This tutorial will tell you how to do this.
The first time you install the Bol Processor, the "bolprocessor" folder will contain a unique folder called "ctests" for storing data. This folder contains examples that are updated when a new version is installed. However, you can use it to store new projects, new subfolders, etc., which will not be affected by new versions.
You can also create your own folders (and subfolders) at the same level as "ctests". The interface is designed for the creation, moving and deletion of folders and files within the "bolprocessor" folder. Always use the interface. Creating a folder (or a file) via the Finder or File Manager may not work, especially with XAMPP, because the owner may be different from the Apache server's identity. For geeks: XAMPP runs as "daemon" while the Finder runs as your personal identity.
Creating folders and files without using the Bol Processor interface may result in "permission errors" when a file is saved. Indeed, there are workarounds, for those familiar with shell scripts, for example the "change_permissions.sh" script designed for Linux and MacOS. But this is not a pleasant way to use the Bol Processor…
In short, always create folders using the CREATE FOLDERS function in the interface. Once created, they can be moved (even with the Finder or File Manager) within the "bolprocessor" folder, and even renamed. The Bol Processor will always recognise them as its own.
Below is an example of two folders called "data" and "my_data" created at the same level as "ctests":

Now, how can we move a folder outside the "bolprocessor" folder? Once we've moved it, the interface no longer shows it. For example, let us do this with "my_data". (The folder may be empty or contain other folders and files.)
Using the Finder in MacOS, or copy/paste in Windows and Linux, we move "my_data" to the desired location, for example a "MUSIC" folder at the root of an external drive called "EXT". Make sure that this location accepts read/write operations.
At this point, there is no more "my_data" in "bolprocessor", or we delete it using the DELETE FOLDERS button. You can't delete "ctests" with this delete function.
To make "my_data" visible again from its remote location, we need to create a symbolic link. Unfortunately, the Bol Processor's interface cannot do this due to security restrictions. I've spent hours with a chatbot trying to find a workaround!
In MacOS and Linux, the symbolic link is created from a (Unix) Terminal. In Windows, you will use the Windows PowerShell (admin).
This procedure doesn't work with aliases created by the Finder in MacOS. You really need to use symbolic links.
MacOS or Linux
Open the Terminal (in the Applications folder) and point it to the "htdocs" directory. For those unfamiliar with Unix commands, you will need to type "cd " (followed by a space) and drag "htdocs" to the end of this command, then press "return". You can type the instruction "ls -al" to see the contents of "htdocs", which contains "bolprocessor", "ctests", and more.
Suppose that your "MUSIC" folder is on disk "EXT" and you want to link to the relocated "my_data" folder. Type this command:
ln -s /Volumes/EXT/MUSIC/my_data my_data
This will create the "my_data" symbolic link pointing to the remote "my_data" folder. Check that the link has been created by typing "ls -al".
Depending on the disk or disk area used to store relocated data, you might encounter problems due to MacOS access restrictions, especially if the System Integrity Protection (SIP) is enabled.
If you are using a recent installer (as of 3 Feb 2025) and a XAMPP Apache server, the 'daemon' identity used by XAMPP is automatically added to the 'admin', 'wheel' and 'staff' groups which are commonly used by the Finder.
There are probably fewer restrictions with MAMP because this server runs under your personal identity, and file owners are set to that identity.
Windows
Right-click the start icon at the bottom left of the screen, and select Windows PowerShell (admin). Then type the following command to create a symbolic link — in fact a junction (/J instead of /D):
cmd /c mklink /J "C:\MAMP\htdocs\bolprocessor\my_data" "D:\MUSIC\my_data"
If you are using XAMPP, replace "\MAMP\" with "\xampp\".
Depending on the disk or disk area used to store relocated data, you may encounter issues due to Windows 10 access restrictions.
For example, moving your data to the OneDrive directory won't work by default. If you must keep the target folder inside OneDrive, you must disable the synchronisation of your files:
- Open OneDrive Settings
- Go to "Choose folders"
- Uncheck your data folder(s).
Return to the Bol Processor
Now, the BolProcessor interface will show "my_data" as if the folder was in "bolprocessor". If it doesn't, make sure that the paths used to create the link were correct.
Make sure that you can create and save data in the relocated folder. Welcome to shared projects!