Installation Steps
If you are using one of the following Linux Operating Systems, follow our simple instruction steps to get started:- Ubuntu
- CentOS
- RHEL
- Oracle Linux
1
Run the Installation Script
SSH into your web server, ensure you’re using a user that has full sudo access, and run the command below:
2
Retrieve Your Credentials
Locate your license key (sent from InterWorks) and open
/var/www/curator_info.txt to retrieve your default
administrator credentials.3
Open the Installer
Open
http://curatorexample.com/install.php in a browser - replacing curatorexample.com with your site’s URL. If
you’re on the server you installed, you may also use localhost.This may be an IP address or computer name until your IT team sets up DNS.4
Credentials
The installer will generate credentials for use during installation and will store them in a file in the installation
directory (Default:
/var/www/curator_info.txt or C:\InterWorks\Curator\curator_info.txt in Windows). You will need
these credentials to complete the installation and to log in to the Curator backend after installation.5
License Key
Enter your license key when prompted. If you do not have a license key, please contact InterWorks to obtain one.

6
Database Connection
You may be prompted to enter your database connection information if the installer is unable to automatically find the
database for you.

7
Success
If the installation is successful, you will be redirected to your new Curator homepage
Using the same auto-generated credentials created in the install script above, you can log into the Curator backend which
can be accessed from

http://curatorexample.com/backend. If you’re on the server you installed, you may also use localhost.
Keep in mind this may be an IP address or computer name until your IT team sets up DNS.Custom Setup
The install script can take optional parameters to specify values for the installation script. This can be helpful in distributed setups, or scripted installations.-hThe database hostname Needed when using an external database host-uThe database usernameDefault: curator-pThe database password Default: auto-generated password. Use this when you need to use a connection to a database for a user that has already been created with a specific password.-PThe database portDefault: 3306-dThe database nameDefault: curator-lThe License Key for your Curator installation. When performing a full installation, this is required.-sPath to a persistent storage location Container-based or distributed installations typically require this.-vSets the version of Curator to install. Default: most recent version.
-fFull Installation, this flag is required in most custom setups to avoid the in-browser installer.
Key File Locations
These are the default paths for a standard Curator Linux installation. Exact locations may vary based on your distribution and web server configuration.To confirm the exact
php.ini path on your system, check the php_ini_path field returned by the
/portal/info endpoint.Ubuntu 22.04 / 24.04
- Webroot:
/var/www/html - Environment file:
/var/www/html/.env - PHP.ini (Apache):
/etc/php/8.3/apache2/php.ini - PHP.ini (FPM):
/etc/php/8.3/fpm/php.ini
RHEL 9 / CentOS 9 / Oracle Linux 9+
- Webroot:
/var/www/html - Environment file:
/var/www/html/.env - PHP.ini:
/etc/opt/remi/php83/php.ini
Environment Configuration
Optional settings can be added to the environment file (/var/www/html/.env) to override Curator’s
defaults. Curator ships with sensible values for all of these, so only set them if you need to change
the default behavior. Restart Apache or PHP-FPM after editing the file.
FILESYSTEM_DRIVER and FILESYSTEM_DISK are two separate settings, not old and new names for the same
thing. Curator media and uploads always follow FILESYSTEM_DRIVER. If you have only ever set
FILESYSTEM_DRIVER, your media and uploads continue to work unchanged and no action is required.CACHE_PREFIX is derived from your APP_NAME unless you set it explicitly. Changing either value
changes the cache keys, so Curator rebuilds its cache on the next page load. This is safe, but the first
load afterward may be slower than usual.APP_DEBUG defaults to false, so a generic error page is shown when something goes wrong. Set
APP_DEBUG=true temporarily while troubleshooting an installation to see the detailed error page with a
full stack trace, then set it back to false (or remove it) once you’re done — leaving it enabled can
expose sensitive information about your application and infrastructure to untrusted users.Log Locations
- Application Log:
/var/www/html/storage/logs/system-YYYY-MM-DD.log - PHP Installer Log:
/var/www/html/assets/install.log - Shell Installer Log:
~/iw_install.log
AWS EC2 Process
AWS provides a helpful outline on how to connect to an AWS EC2 instance from Windows using Putty.Network Whitelist Requirements
For installations in environments with restricted internet access or firewall configurations, the following URLs should be whitelisted to ensure proper functionality:RHEL/CentOS/Oracle Linux Systems
- InterWorks API
api.curator.interworks.com
- EPEL Repository
dl.fedoraproject.orgdownload.fedoraproject.org(covers mirrors.fedoraproject.org)
- Remi Repository (PHP packages)
*.remirepo.net(covers rpms.remirepo.net, repo.remirepo.net, mirrors.remirepo.net)
- Base RHEL/CentOS Repositories
*.centos.org(covers vault.centos.org, mirror.centos.org)download.redhat.comcdn.redhat.com
- Oracle Linux Repositories (Oracle Linux only)
yum.oracle.comoss.oracle.com
- CDN Networks
*.akamaiedge.net(covers*.akamaitechnologies.com- same Akamai network)
Ubuntu Systems
- InterWorks API
api.curator.interworks.com
- Ubuntu Repositories
*.archive.ubuntu.com(covers archive.ubuntu.com, us.archive.ubuntu.com, gb.archive.ubuntu.com, etc.)security.ubuntu.comports.ubuntu.comchangelogs.ubuntu.com
- Launchpad PPAs (for ondrej/apache2 and ondrej/php)
*.launchpad.net(covers ppa.launchpad.net, launchpad.net)ppa.launchpadcontent.netkeyserver.ubuntu.com
Testing Connectivity
To confirmapi.curator.interworks.com is reachable through your firewall or proxy before installing or
upgrading, request the same endpoint Curator itself uses to check for new versions:
200 with a body similar to:
If the request times out, fails a TLS handshake, or returns anything other than a
200 status, the
whitelist entry is not taking effect yet — recheck your proxy and firewall rules before continuing with
installation or upgrades.