Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Silent Install : Ability to bypass the installer via env variables

Description

At this point in time, once the contentbox cli installs a new site, the server is started, which kicks off the orm (creating the database) and calls the web installer for completion. The installer is in charge of then setting up the default site and the first administrator by requesting user input.

Have a way to bypass the web installer via env variables to allow for silent installs and avoid the security risk of having an open web installer.

We can also update the cli installer to allow for the following inputs. If one is used, then all the fields are mandatory.

  • Admin First Name

  • Admin Last Name

  • Admin Email

  • Admin Username

  • Admin Password

The installer cli will remove the contentbox-installer module as part of its deployment process, since we will be in silent mode.

The env variables we can use are to do a silent install can be:

# The default is false, no silent install. # This is the key that allows for a silent install INSTALLER_SILENT=true|[false] # Installer Admin Settings INSTALLER_ADMIN_FIRSTNAME= INSTALLER_ADMIN_LASTNAME= INSTALLER_ADMIN_EMAIL= INSTALLER_ADMIN_USERNAME= INSTALLER_ADMIN_PASSWORD= # Enable full ses rewrites, by default we do INSTALLER_FULL_SES=[true]|false # Create site sample data INSTALLER_CREATE_SAMPLE_SITE=[true]|false # Create development site alongside production site INSTALLER_CREATE_DEVELOPMENT_SITE=[true]|false # Outgoing Email address for notifications INSTALLER_OUTGOING_EMAIL=

 

Once ContentBox is active via the cb_active flag. Then these installer env variables will be ignored, as this denotes that the site has been setup already and configured for operation.

Activity

Show:
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Priority

Sentry

Created October 2, 2021 at 12:07 AM
Updated December 12, 2023 at 11:17 AM