Blua.blue can be run from a private network or a single machine and distribute content via webhooks. Depending on your organisation,
this might offer additional security (e.g. if employees connect via VPN into high-security systems). However, the API & the SDKs require public endpoints to operate.
On a basic level, blua.blue can run combinations of pull and push distribution.
If you want applications to be able to "ask for content", you should consider hosting blua.blue on a public domain.
If your applications only "receive content", then local installations might be sufficient.
Having problems getting it to run after following the instructions below? We gladly help.
As far as reasonable, we will guide you through the process.
However, please understand that we reserve the right to end free consultation and offer you payed support at any time.
We are also happily accepting requests for installation services.
Please ensure the following requirements are met before proceeding. Blua.blue might work in different environments as well,
but no sufficient testing was conducted to verify and we might only be able to give limited support for other environments or setups.
- PHP 7.2 or above
- MySQL database
- node & npm
As a contributor/open source developer, please visit the github repository instead of following this guide.
These instructions assume familiarity with your target system's OS and right management as well as with familiarity with the technologies mentioned in "Prerequisites".
- In the destination folder (e.g. public_html), run
composer create-project blua-blue/blua-blue -s beta
npm install to install dependencies
neoan3 migrate models up to execute database migration (create a dedicated database first)
- Modify line 5 of the file .htaccess to represent your public root (e.g. "/")
neoan3 credentials and create the credentials described below
The credentials you require are dependent on the plugins and addons you install. The minimum requirement to operate blua.blue is to provide the following credentials:
This entity requires the properties "name" (database name), "assumes_uuid" (must be set to
"password" (your database password), "host" (usually "localhost") and "user" (database user name). For additional information visit
neoan3-apps/db's environment variables
This entity requires the property "secret". As this string will be the basis of your authentication encryption, we recommend a minimum length of 16 characters. For additional information visit
This entity requires the properties "host" (e.g. mail.your-domain.com), "username" (e.g. email@example.com), "password" (e.g. myMailPassword),
"fromEmail" (e.g. firstname.lastname@example.org), "fromName" (e.g. John Doe), "port" (e.g. 25) and "secure" (e.g. ssl). Blua.blue uses PHPMailer.
For additional information visit
To protect you from spam, we recommend signing up with hCaptcha here and adding the following properties to blua_hcaptcha:
"secret" (Secret provided by hcaptcha), "siteKey" (site-key provided after registering your site). Note:
Due to the nature of the captcha mechanism, the contact forms do not work out of the box on local systems and adjustments have to be made.