OpenSite/Installation
Start an authorized Windows development package without mixing its components.
Before you begin
Obtain the complete package and its instructions from the distributor. See OpenSite/Downloads for availability. Back up existing documents. This is a package-use guide, not a claim that a public installer exists.
Start the desktop
- Extract the entire archive to a writable folder if it is supplied as an archive. Keep all subfolders.
- Find the supplied
opensite-desktop.exe; a staged development layout can place it underbin. - Start it normally. Do not add development authorization flags to make a disabled production command run.
- Check the title/About information and confirm that the intended workbench and Python surfaces are present.
- Follow OpenSite/Guides/First desktop session using a new practice file.
Keep the package together
The executable can depend on OpenSite DLLs, Qt DLLs/platform plugins, extension packages and a matching embedded runtime. Keep the distributor’s layout. Do not copy random DLLs into Windows system folders, mix Debug and Release files, or replace the embedded interpreter with a system Python.
Settings location
The normal desktop chooses a per-user application configuration location and a settings.json file. An authorized developer launch can specify --settings=path. The exact default directory is resolved by Qt on that machine; do not assume a developer’s drive path applies to every user. See OpenSite/Guides/Arrange workspace and OpenSite/Guides/Save and reload settings.
If startup fails
Use OpenSite/Guides/Troubleshoot startup. Record the first error and exact executable/build. Re-extract a clean matching package before combining files from different builds.
Removing a development package
There is no documented product uninstaller in this snapshot. Close OpenSite before moving a standalone development folder. Preserve your documents, scripts, exports and settings backup; their locations can be outside that folder. An eventual installer’s instructions take precedence.
