Choose a Simbioza installation
These guides install Simbioza 0.3.48. See module versions and dependencies for the current package inventory. Framework remains 0.0.25. The 0.3.x baseline starts with a new application directory, configuration and database. An upgrade from 0.2.x or reuse of its Simbioza backups is not supported.
Choose one complete guide below. Each starts at an administrator terminal, installs/checks the host tools, downloads the release, prepares the database and permissions, configures the web server, runs the wizard and verifies the first sign-in. Do not use this overview as an extra installation step.
| Installation | PHP identity | Package preparation and later application updates | Complete guide |
|---|---|---|---|
| Apache mod_php | Shared Apache account | CLI, as the code owner | Start the mod_php installation |
| Ordinary PHP-FPM | Shared system web account in an FPM pool | CLI, as the code owner | Start the ordinary FPM installation |
| Secured PHP-FPM (recommended) | Dedicated FPM and deployment accounts, restricted helper | GUI through the worker, or CLI as a deploy maintainer | Start the secured FPM installation |
All three have a graphical initial installer and configuration GUI. Ordinary FPM is not the same as secured FPM: adding a FastCGI handler alone does not create deployment isolation or enable GUI Composer/application updates. Nginx requires FPM; it cannot run Apache's mod_php. Docker installation is a separate, optional image-based route.
Before choosing a PHP mode
The default examples are for a new Linux or macOS host, not an existing production pool. Have an administrator shell, a domain/TLS certificate for a public site and a database choice. SQLite needs no database service. Every chosen guide repeats the exact preparation commands; no existing Simbioza FPM/deploy account is assumed.
For reinstallation, the system administrator first handles the old site's processes and data, checks existing identities and selects the correct instance and port. The guides never delete another installation or recreate a running site merely because the download directory exists.
Private module configuration uses HPH_CONFIG_PATH (default config/); persistent files use data/. Only public/ is exposed by the web server.
After installation
Set up log rotation for cron, updater and FPM output. The application's rotating app.log handler does not rotate those separate files.
Each complete guide includes its own module, language and update commands, backup boundaries and final checks. Routine package/code work belongs to the maintainer/deploy identity, not the web account and not root. Language packs can be updated independently of an application release.
The application's updater refreshes bundled User guides from the installed release packages. Reading GitHub main does not automatically replace pages already stored on a site; their content can belong to an older release. The bundled installation pages are generated from these Markdown sources.
Choosing Simbioza features
Simbioza brings pages, a Wiki, calendars, surveys and collaboration together in one complete application. If you need only some of these features, the modular HeartPhrame framework also allows a focused installation. The following presets describe that additional option.
Simbioza is Croatian for symbiosis: different organisms living together. The application is named after that idea because its modules have distinct roles but can work together. A page explains a calendar event, a Wiki connects team knowledge, and a survey collects feedback. The complete Simbioza combines these tools, tasks, comments, notifications and integrations in one environment.
Choose a purpose
| What you need | Installation preset | Feature modules |
|---|---|---|
| All available features together | Full Simbioza | All optional modules |
| A simple website with HTML pages | HTML website | HTML Editor |
| Events, meetings and CalDAV | Calendar | Calendar |
| A searchable Wiki organized into Workspaces | Wiki | Workspace, Workspace Search and Simbioza User |
| Surveys with questions, branching and results | Surveys | Survey |
Every installation includes Auth, ORM, Menu, Theme, Backup and Audit. They provide authentication and permissions, database access, menus, appearance, backups and activity logs. “Standalone” means without other business modules, not without the shared foundation and required dependencies.
The installer adds required dependencies automatically. For example, Survey uses HTML Editor for introductions and explanations; the Wiki also needs the Editor, and Simbioza User adds notifications. API, accessibility and other optional integrations do not require unrelated business features.
Install the selected tool
- Prepare a new installation using the appropriate installation guide.
- In the wizard's application settings step, select an Installation preset and click Apply preset.
- Review the selected modules. Required dependencies remain included; select additional features only if you need them.
- Select the installation languages and finish setup. Content and translation languages are selected from installed, active languages.
- Sign in as administrator, create your content and add menu links so visitors can find it.
The result is one application for your chosen purpose. Sample pages, calendars and surveys are not business data automatically shipped to every new site; you create your content after installation.
Share a standalone HTML website
An HTML website does not need Wiki to work with several authors or private pages. As administrator, open Settings → HTML editor → Page permissions and add users or groups. Adding permits creating and editing their own pages. Editing permits managing all standalone pages, including private ones; it does not grant access to administrator settings.
On an individual page, open Page settings and permissions. Choose public reading, all signed-in users, or only selected users and groups. This choice also protects attachments, direct links and API reads. In a Wiki, continue to use the existing Workspace and page permissions instead.
Extend an existing installation
For example, add a calendar or surveys to an HTML website, or add surveys, tasks and comments to a Wiki. Settings → Setup and modules shows what is installed, what is enabled and which dependencies are required.
On a correctly configured dedicated FPM installation, an administrator can click Install beside another module. For mod_php and ordinary FPM, a maintainer runs the corresponding CLI command from the application root using the maintenance account:
php vendor/bin/hph modules add calendar --fresh
php vendor/bin/hph modules add survey --fresh
These are separate examples: choose the module you need. The system adds its required dependencies. Use task and comment for tasks and comments; a Wiki can later add confluence-import to import existing content. After extending the installation, configure the new module's permissions, menus and settings. Installing a module does not give every user permission to edit content.
Make a backup before changing the installation's composition. Disabling an optional module is not the same as uninstalling it: disabling retains data, while uninstalling removes its tables and package after preparing a recovery backup. The six required modules cannot be disabled or uninstalled.
Add Workspaces to an existing HTML website
Adding Workspaces does not move existing HTML pages. They keep their addresses, content, translations, attachments and standalone permissions. Standalone HTML pages and pages in Workspaces can be used together, including through the API.
Only an administrator can move an existing page into a Workspace:
- Open Settings → HTML editor → Pages outside workspaces.
- Find the page and choose Move into workspace.
- Open the destination list or search by name. More workspaces load as you scroll.
- Review the destination's visibility and confirm its permissions, then move the page.
The result is one page at the top level of the destination tree. All translations, version history and attachment versions move with it. Files are transferred into the Workspace's storage; database HTML remains in the same version records with new Workspace ownership. Links in stored pages are repaired, including language choices and anchors, and existing page and attachment addresses remain usable with the destination's access checks. Published versions remain published and working drafts remain drafts.
Destination permissions replace standalone access. The old readers are not automatically added as exceptions. Moving a public page into a private Workspace can restrict it; moving a private page into a public Workspace can make its published content public. Review the destination before confirming. Take a backup first if you need a return point: this screen does not offer an inverse move.
Updates and backups
New installations receive independent sign-in cookies, including when several sites share one domain. A restore preserves the target site's local session identity instead of copying another site's sign-in cookie identity.
Dedicated FPM with a correctly configured restricted helper supports updates through Settings → Setup and modules → Run update. Merely using FPM is not enough: the environment check must confirm that GUI updates are available.
For other classical installations, the maintainer runs these commands from the application root:
php update.php --check --lang=en
php update.php --lang=en
Updates preserve the selected modules and existing data. A new optional module becomes available to install; it is not enabled automatically. A full backup includes the data and portable settings of enabled modules. Also retain a separate copy of host configuration and local secrets, which are not transferred by business-data backups.
Docker
Docker uses the same feature selection. If an image contains all modules, select and enable only the necessary ones during installation. For a smaller custom image, build with selected modules and their required dependencies. A module absent from the image requires a replacement image, not a code change inside a running container. Updates replace the image while preserving the database and runtime data. Follow the Docker guide.
Guides and integration with other systems
With a Wiki, these pages live in the User guides Workspace. Without a Wiki, the same manual is available through Guides, with a chapter list and navigation. There is no need to install a Wiki just to read the manual.
API can be added to any purpose. An API key determines permitted calls but never bypasses its owner's permissions. Available routes and scopes follow installed, enabled modules. This supports integration with other systems and custom HeartPhrame applications without rebuilding authentication, navigation, database access and other common foundations.
Commentaires
0Il n'y a pas encore de commentaires.
Vous devez vous connecter pour ajouter un commentaire.