Bitnami ERPNext Installer

NOTE: Before running the commands shown on this page, you should load the Bitnami stack environment by executing the installdir/use_APPNAME script (Linux and Mac OS X) or by clicking the shortcut in the Start Menu under "Start -> Bitnami APPNAME Stack -> Application console" (Windows). Learn more.
NOTE: When running the commands shown on this page, replace the installdir placeholder with the full installation directory for your Bitnami stack.

Description

ERPNext is an open source, web based application that helps small and medium sized business manage their accounting, inventory, sales, purchase, administration, project, customer support and website.

First steps with the Bitnami ERPNext Stack

Welcome to your new Bitnami application! Here are a few questions (and answers!) you might need when first starting with your application.

What are the system requirements?

Before you download and install your application, check that your system meets these requirements.

How do I install the Bitnami ERPNext Stack?

Windows, OS X and Linux installer
  • Download the executable file for the Bitnami ERPNext Stack from the Bitnami website.

  • Run the downloaded file:

    • On Linux, give the installer executable permissions and run the installation file in the console.
    • On other platforms, double-click the installer and follow the instructions shown.

Check the FAQ instructions on how to download and install a Bitnami Stack for more details.

The application will be installed to the following default directories:

Operating System Directory
Windows C:\Bitnami\APPNAME-VERSION
Mac OS X /Applications/APPNAME-VERSION
Linux /opt/APPNAME-VERSION (running as root user)
OS X VM
  • Download the OS X VM file for the Bitnami ERPNext Stack from the Bitnami website.
  • Begin the installation process by double-clicking the image file and dragging the WordPress OS X VM icon to the Applications folder.
  • Launch the VM by double-clicking the icon in the Applications folder.

What credentials do I need?

You need application credentials, consisting of a username and password. These credentials allow you to log in to your new Bitnami application.

What is the administrator username set for me to log in to the application for the first time?

  • For Windows, Linux and OS X installers, the username was configured by you when you first installed the application.
  • For OS X VMs, the username can be obtained by clicking the Bitnami badge at the bottom right corner of the application welcome page.

What is the administrator password?

  • For Windows, Linux and OS X installers, the password was configured by you when you first installed the application.
  • For OS X VMs, the password can be obtained by clicking the Bitnami badge at the bottom right corner of the application welcome page.

How to start or stop the services?

Linux

Bitnami native installers include a graphical tool to manage services. This tool is named manager-linux-x64.run on Linux and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The native installer also includes a command-line script to start, stop and restart applications, named ctlscript.sh. This script can be found in the installation directory and accepts the options start, stop, restart, and status. To use it, log in to the server console and execute it following the examples below:

  • Call it without any service names to start all services:

      $ sudo installdir/ctlscript.sh start
    
  • Use it to restart a specific service only by passing the service name as argument - for example, mysql, postgresql or apache:

      $ sudo installdir/ctlscript.sh restart mysql
      $ sudo installdir/ctlscript.sh restart postgresql
      $ sudo installdir/ctlscript.sh restart apache
    
  • Obtain current status of all services:

      $ installdir/ctlscript.sh status
    

The list of available services varies depending on the required components for each application.

Mac OS X

Bitnami native installers include a graphical tool to manage services. This tool is named manager-osx on Mac OS X and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The native installer also includes a command-line script to start, stop and restart applications, named ctlscript.sh. This script can be found in the installation directory and accepts the options start, stop, restart, and status. To use it, log in to the server console and execute it following the examples below:

  • Call it without any service names to start all services:

    $ sudo installdir/ctlscript.sh start
    
  • Use it to restart a specific service only by passing the service name as argument - for example, mysql or apache:

     $ sudo installdir/ctlscript.sh restart mysql
     $ sudo installdir/ctlscript.sh restart apache
    
  • Obtain current status of all services:

     $ installdir/ctlscript.sh status
    

The list of available services varies depending on the required components for each application.

NOTE: If you are using the stack manager for Mac OS X-VM, please check the following blog post to learn how to manage services from its graphical tool.

Windows

Bitnami native installers include a graphical tool to manage services. This tool is named manager-windows.exe on Windows and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The Windows native installer creates shortcuts to start and stop services created in the Start Menu, under "Programs -> Bitnami APPNAME Stack -> Bitnami Service". Servers can also be managed from the Windows "Services" control panel. Services are named using the format APPNAMESERVICENAME, where APPNAME is a placeholder for the application name and SERVICENAME is a placeholder for the service name. For example, the native installer for the Bitnami WordPress Stack installs services named wordpressApache and wordpressMySQL.

These services will be automatically started during boot. To modify this behaviour, refer to the section on disabling services on Windows.

How to change the default administrator password?

For security, it is recommended that you change the default administrator password as soon as possible. Follow the steps below:

  • Log in to the application as an administrator.
  • Select the "My Settings" menu item.

    ERPNext password change

  • Enter the the new password once into the "Set New Password" field.

    ERPNext password change

  • Click "Save" to save your changes.

How to change the interface language?

The Bitnami ERPNext Stack uses the English language pack by default. However, translations also exist for other languages. To change the interface language, follow these steps:

  • Log in to the application as an administrator.
  • Click the "Setup" button in the main menu.

    Language

  • Select the "Settings -> System Settings" menu item.
  • Select a new language using the "Language" field.

    Language

  • Click the "Save" button to save your changes.

How to access the administration panel?

Access the administration panel by browsing to http://localhost/login.

How to configure outbound email settings?

To configure outbound email, follow these steps:

Edit the installdir/apps/erpnext/htdocs/frappe-bench/sites/erpnext/site_config.json file. Add or update the SMTP configuration in the file. Here is an example of how to configure a Gmail account. Replace the DB_PASSWORD placeholder with the correct database password and the USERNAME and PASSWORD placeholders with your Gmail account username and password respectively.

Your file should look like this:

{
    "db_name": "bitnami_erpnext",
    "db_password": "DB_PASSWORD",
    "mail_server": "smtp.gmail.com",
    "mail_login": "USERNAME@gmail.com",
    "mail_password": "PASSWORD",
    "use_ssl": 1,
    "mail_port": 587,
    "auto_email_id": "USERNAME@gmail.com"
}    
NOTE: Remember to use double quotes around the values and a comma after every line except the last one. All the parameters should be enclosed between curly braces as shown above.

To configure the application to use other third-party SMTP services for outgoing email, such as SendGrid or Mandrill, refer to the FAQ.

NOTE: If you are using Gmail as the outbound email server and have experienced issues trying to send emails correctly, check the How to troubleshoot Gmail SMTP issues to learn the causes of these issues and how to solve them.

How to create a full backup of ERPNext?

To perform a manual backup of ERPNext, follow these steps:

  • Log in to the server console using SSH.
  • At the server console, execute the following commands:

       $ cd installdir/apps/erpnext/htdocs/frappe-bench
       $ sudo bench backup-all-sites
    

    A new backup will be created.

  • Log in to the ERPNext administration dashboard.
  • Navigate to the "Setup -> Data -> Download Backups" page. You should see the newly-created backup. Click the backup link to download the backup file to your desktop.

    ERPNext backup

How to upgrade ERPNext?

It is strongly recommended to create a backup before starting the update process. If you have important data, create and restore a backup to ensure that everything works properly.

You can upgrade the application itself without modifying any other component included in the stack by executing the following commands as bitnami user or the user who installed the application:

    $ cd installdir/apps/erpnext/htdocs/frappe-bench
    $ bench --site erpnext migrate

How to create an SSL certificate?

OpenSSL is required to create an SSL certificate. A certificate request can then be sent to a certificate authority (CA) to get it signed into a certificate, or if you have your own certificate authority, you may sign it yourself, or you can use a self-signed certificate (because you just want a test certificate or because you are setting up your own CA).

Follow the steps below for your platform.

Linux and Mac OS X

NOTE: OpenSSL will typically already be installed on Linux and Mac OS X. If not installed, install it manually using your operating system's package manager.

Follow the steps below:

  • Generate a new private key:

     $ sudo openssl genrsa -out installdir/apache2/conf/server.key 2048
    
  • Create a certificate:

     $ sudo openssl req -new -key installdir/apache2/conf/server.key -out installdir/apache2/conf/cert.csr
    
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ sudo openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt -req -signkey installdir/apache2/conf/server.key -days 365
    
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ sudo openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ sudo openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
    

Windows

NOTE: OpenSSL is not typically installed on Windows. Before following the steps below, download and install a binary distribution of OpenSSL.

Follow the steps below once OpenSSL is installed:

  • Set the OPENSSL_CONF environment variable to the location of your OpenSSL configuration file. Typically, this file is located in the bin/ subdirectory of your OpenSSL installation directory. Replace the OPENSSL-DIRECTORY placeholder in the command below with the correct location.

     $ set OPENSSL_CONF=C:\OPENSSL-DIRECTORY\bin\openssl.cfg
    
  • Change to the bin/ sub-directory of the OpenSSL installation directory. Replace the OPENSSL-DIRECTORY placeholder in the command below with the correct location.

     $ cd C:\OPENSSL-DIRECTORY\bin
    
  • Generate a new private key:

     $ openssl genrsa -out installdir/apache2/conf/server.key 2048
    
  • Create a certificate:

     $ openssl req -new -key installdir/apache2/conf/server.key -out installdir/apache2/conf/cert.csr
    
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt -req -signkey installdir/apache2/conf/server.key -days 365
    
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
    

Find more information about certificates at http://www.openssl.org.

How to enable HTTPS support with SSL certificates?

TIP: If you wish to use a Let's Encrypt certificate, you will find specific instructions for enabling HTTPS support with Let's Encrypt SSL certificates in our Let's Encrypt guide.
NOTE: The steps below assume that you are using a custom domain name and that you have already configured the custom domain name to point to your cloud server.

Bitnami images come with SSL support already pre-configured and with a dummy certificate in place. Although this dummy certificate is fine for testing and development purposes, you will usually want to use a valid SSL certificate for production use. You can either generate this on your own (explained here) or you can purchase one from a commercial certificate authority.

Once you obtain the certificate and certificate key files, you will need to update your server to use them. Follow these steps to activate SSL support:

  • Use the table below to identify the correct locations for your certificate and configuration files.

    Variable Value
    Current application URL https://[custom-domain]/
      Example: https://my-domain.com/ or https://my-domain.com/appname
    Apache configuration file installdir/apache2/conf/bitnami/bitnami.conf
    Certificate file installdir/apache2/conf/server.crt
    Certificate key file installdir/apache2/conf/server.key
    CA certificate bundle file (if present) installdir/apache2/conf/server-ca.crt
  • Copy your SSL certificate and certificate key file to the specified locations.

    NOTE: If you use different names for your certificate and key files, you should reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the corresponding Apache configuration file to reflect the correct file names.
  • If your certificate authority has also provided you with a PEM-encoded Certificate Authority (CA) bundle, you must copy it to the correct location in the previous table. Then, modify the Apache configuration file to include the following line below the SSLCertificateKeyFile directive. Choose the correct directive based on your scenario and Apache version:

    Variable Value
    Apache configuration file installdir/apache2/conf/bitnami/bitnami.conf
    Directive to include (Apache v2.4.8+) SSLCACertificateFile "installdir/apache2/conf/server-ca.crt"
    Directive to include (Apache < v2.4.8) SSLCertificateChainFile "installdir/apache2/conf/server-ca.crt"
    NOTE: If you use a different name for your CA certificate bundle, you should reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in the corresponding Apache configuration file to reflect the correct file name.
  • Once you have copied all the server certificate files, you may make them readable by the root user only with the following commands:

     $ sudo chown root:root installdir/apache2/conf/server*
    
     $ sudo chmod 600 installdir/apache2/conf/server*
    
  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart the Apache server.

You should now be able to access your application using an HTTPS URL.

How to force HTTPS redirection with Apache?

Add the following lines in the default Apache virtual host configuration file at installdir/apache2/conf/bitnami/bitnami.conf, inside the default VirtualHost directive, so that it looks like this:

<VirtualHost _default_:80>
  DocumentRoot "installdir/apache2/htdocs"
  RewriteEngine On
  RewriteCond %{HTTPS} !=on
  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
  ...
</VirtualHost>

After modifying the Apache configuration files:

  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart Apache to apply the changes.

How to debug Apache errors?

Once Apache starts, it will create two log files at installdir/apache2/logs/access_log and installdir/apache2/logs/error_log respectively.

  • The access_log file is used to track client requests. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time.

  • The error_log file is used to record important events. This file includes error messages, startup messages, and any other significant events in the life cycle of the server. This is the first place to look when you run into a problem when using Apache.

If no error is found, you will see a message similar to:

Syntax OK

How to find the MySQL database credentials?

How to connect to the MySQL database?

You can connect to the MySQL database from the same computer where it is installed with the mysql client tool.

$ mysql -u root -p

You will be prompted to enter the root user password. This is the same as the application password.

How to debug errors in your database?

The main log file is created at installdir/mysql/data/mysqld.log on the MySQL database server host.

How to change the MySQL root password?

You can modify the MySQL password using the following command at the shell prompt. Replace the NEW_PASSWORD placeholder with the actual password you wish to set.

$ installdir/mysql/bin/mysqladmin -p -u root password NEW_PASSWORD

How to reset the MySQL root password?

If you don't remember your MySQL root password, you can follow the steps below to reset it to a new value:

  • Create a file in /home/bitnami/mysql-init with the content shown below (replace NEW_PASSWORD with the password you wish to use):

     UPDATE mysql.user SET Password=PASSWORD('NEW_PASSWORD') WHERE User='root';
     FLUSH PRIVILEGES;
    

    If your stack ships MySQL v5.7.x, use the following content instead of that shown above:

     UPDATE mysql.user SET authentication_string=PASSWORD('NEW_PASSWORD') WHERE User='root';
     FLUSH PRIVILEGES;
    
    TIP: Check the MySQL version with the command installdir/mysql/bin/mysqladmin --version or installdir/mysql/bin/mysqld --version.
  • Stop the MySQL server:

     $ sudo installdir/ctlscript.sh stop mysql
    
  • Start MySQL with the following command:

     $ sudo installdir/mysql/bin/mysqld_safe --pid-file=installdir/mysql/data/mysqld.pid --datadir=installdir/mysql/data --init-file=/home/bitnami/mysql-init 2> /dev/null &
    
  • Restart the MySQL server:

     $ sudo installdir/ctlscript.sh restart mysql
    
  • Remove the script:

     $ rm /home/bitnami/mysql-init
    

How to change the MySQL root password in Windows?

You can modify the MySQL password using the following command at the shell prompt. Replace the NEW_PASSWORD placeholder with the actual password you wish to set.

installdir\mysql\bin\mysqladmin.exe -p -u root password NEW_PASSWORD

How to reset the MySQL root password in Windows?

If you don't remember your MySQL root password, you can follow the steps below to reset it to a new value:

  • Stop the MySQL server using the graphic manager tool. Refer to the how to start or stop the services section.
  • Check the MySQL version:

    installdir\mysql\bin\mysqladmin.exe –version

  • Create a file named mysql-init.txt with the content shown below depending on your MySQL version (replace NEW_PASSWORD with the password you wish to use):
    • MySQL 5.6.x or earlier:

       UPDATE mysql.user SET Password=PASSWORD('NEW_PASSWORD') 
       WHERE User='root';
       FLUSH PRIVILEGES;
      
    • MySQL 5.7.x or later:

       ALTER USER 'root'@'localhost' IDENTIFIED BY 'NEW_PASSWORD'; 
      
  • Start MySQL server with the following command. Remember to replace PATH with the location in which you have saved the mysql-init.txt file:

     installdir " installdir\mysql\bin\mysqld.exe" --defaults-file=" installdir\mysql\my.ini" --init-file="\PATH\mysql-init.txt" --console
    
    • The --init file option is used by the server for executing the content of the mysql-init.txt file at startup, it will change each root account password.
    • The --defaults-file option is specified since you have installed MySQL using the Bitnami installer.
    • The --console option (optional) has been added in order to show the server output at the console window rather than in the log file.
  • After some minutes, hit Ctrl-C to force the shutdown.
  • Restart the MySQL server from the graphic manager tool.
  • After the server has restarted successfully, delete the mysql-init.txt file.

How to change a user's login name?

ERPNext users log in using their email address. To change a user's email address, follow the steps below:

  • Log in to the application as the user whose email address you wish to change.
  • Select the "My Settings" menu item.

    ERPNext user change

  • Click the "User" text field.

    ERPNext user change

  • Enter a new email address for your user.

    ERPNext user change

To check that the email address has been updated, log in to the application as the new user.

ERPNext user change

How to enable multitenant support?

With Bitnami ERPNext you can host several ERPNext sites at the same time. This section describes the steps required to add a second site.

Your first site is automatically set as default site. You can change it with the command:

    $ bench use sitename
NOTE: All bench commands should be executed as the bitnami user (or the user who installed the application) at 'installdir/apps/erpnext/htdocs/frappe-bench'.

There are two ways of setting up multitenant: Port based and DNS based multitenancy.

Port based multitenancy

To configure Bitnami ERPNext to automatically select the site based on the port, follow the steps below. With this configuration you will be able to access your different ERPNext sites using different ports.

  • Create a new site by executing the commands below:

     $ cd installdir/apps/erpnext/htdocs/frappe-bench
     $ bench new-site <site_name>
    
  • Comment out the line that includes the prefix configuration file in the installdir/apache2/conf/bitnami/bitnami-apps-prefix.conf file:

     # Include "installdir/apps/erpnext/conf/httpd-prefix.conf"
    
  • Include the virtual host configuration file for ERPNext in the installdir/apache2/conf/bitnami/bitnami-apps-vhosts.conf file:

     Include "installdir/apps/erpnext/conf/httpd-vhosts.conf"
    
  • Move the following lines from the beggining of installdir/apps/erpnext/conf/httpd-app.conf to installdir/apache2/conf/bitnami/bitnami-apps-vhosts.conf:

     <IfDefine !IS_ERPNEXT_LOADED>
         Define IS_ERPNEXT_LOADED
         WSGIDaemonProcess wsgi-erpnext user=daemon group=daemon processes=2 threads=15 home=installdir/apps/erpnext/htdocs/frappe-bench/sites python-path=installdir/apps/erpnext/htdocs/venv/lib/python2.7/site-packages:installdir/apps/erpnext/htdocs/frappe-bench/apps/erpnext:installdir/apps/erpnext/htdocs/frappe-bench/env/lib/python2.7/site-packages:installdir/apps/erpnext/htdocs/frappe-bench/apps/frappe python-eggs=installdir/apps/erpnext/htdocs/.tmp display-name=%{GROUP}
     </IfDefine>
    
     WSGIProcessGroup wsgi-erpnext
     WSGIApplicationGroup %{GLOBAL}
    
  • Copy the file installdir/apps/erpnext/conf/httpd-app.conf to installdir/apps/erpnext/conf/httpd-app2.conf

  • Modify installdir/apps/erpnext/conf/httpd-app2.conf replacing sites/erpnext by sites/NEW_SITE_NAME

  • Edit the file installdir/apache2/conf/bitnami/bitnami-apps-vhosts.conf, duplicate the two existing code blocks and configure them as shown below. Please, be aware of the Listen PORT lines. PORT is a placeholder, remember to replace it with the corresponding value.

     <VirtualHost *:80>
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
    
         Include "installdir/erpnext/conf/httpd-app.conf"
     </VirtualHost>
    
     <VirtualHost *:443>
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
         SSLEngine on
         SSLCertificateFile "installdir/erpnext/conf/certs/server.crt"
         SSLCertificateKeyFile "installdir/erpnext/conf/certs/server.key"
    
         Include "installdir/erpnext/conf/httpd-app.conf"
     </VirtualHost>
    
     Listen 8080
     <VirtualHost *:8080>
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
    
         Include "installdir/erpnext/conf/httpd-app2.conf"
     </VirtualHost>
    
     Listen 8443
     <VirtualHost *:8443>
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
         SSLEngine on
         SSLCertificateFile "installdir/erpnext/conf/certs/server.crt"
         SSLCertificateKeyFile "installdir/erpnext/conf/certs/server.key"
    
         Include "installdir/erpnext/conf/httpd-app2.conf"
     </VirtualHost>
    
  • Restart the Apache server:

     $ sudo installdir/ctlscript.sh restart apache
    

After this process, your first site should be reachable at http://SERVER_IP:80 or https://SERVER_IP:443 for SSL. To access your second site, enter http://SERVER_IP:8080 or https://SERVER_IP:8443 for SSL in your preferred browser. SERVER_IP is a placeholder, remember to replace it with the corresponding value. The credentials for the first site are the same credentials from the original ERPNext installation. The credentials for the second site are Administrator as username and the password you specified when creating the new site using bench.

DNS based multitenancy

To configure Bitnami ERPNext to automatically select the site based on the hostname you use to access it, follow the steps below. With this configuration you will be able to access your different ERPNext sites using different hostnames.

NOTE: Take into account that this configuration requires that you use different domains for each site. They can be public domains or local domains routed using the hosts file. Accessing the application using an IP address (127.0.0.1 or your server's one) will lead to the Bitnami ERPNext Stack welcome page.
  • Create a new site and enable DNS multitenant by executing the commands below. NEW_SITE_NAME is a placeholders. Remember to replace it with you preferred site name.

     $ cd installdir/apps/erpnext/htdocs/frappe-bench
     $ bench config dns_multitenant on
     $ bench new-site NEW_SITE_NAME
    
  • Comment out the line that includes the prefix configuration file in the installdir/apache2/conf/bitnami/bitnami-apps-prefix.conf file:

     # Include "installdir/apps/erpnext/conf/httpd-prefix.conf"
    
  • Include the virtual host configuration file for ERPNext in the installdir/apache2/conf/bitnami/bitnami-apps-vhosts.conf file:

     Include "installdir/apps/erpnext/conf/httpd-vhosts.conf"
    
  • Move the following lines from the beggining of installdir/apps/erpnext/conf/httpd-app.conf to installdir/apache2/conf/bitnami/bitnami-apps-vhosts.conf:

     <IfDefine !IS_ERPNEXT_LOADED>
         Define IS_ERPNEXT_LOADED
         WSGIDaemonProcess wsgi-erpnext user=daemon group=daemon processes=2 threads=15 home=installdir/apps/erpnext/htdocs/frappe-bench/sites python-path=installdir/apps/erpnext/htdocs/venv/lib/python2.7/site-packages:installdir/apps/erpnext/htdocs/frappe-bench/apps/erpnext:installdir/apps/erpnext/htdocs/frappe-bench/env/lib/python2.7/site-packages:installdir/apps/erpnext/htdocs/frappe-bench/apps/frappe python-eggs=installdir/apps/erpnext/htdocs/.tmp display-name=%{GROUP}
     </IfDefine>
    
     WSGIProcessGroup wsgi-erpnext
     WSGIApplicationGroup %{GLOBAL}
    
  • Copy the file installdir/apps/erpnext/conf/httpd-app.conf to installdir/apps/erpnext/conf/httpd-app2.conf

  • Modify installdir/apps/erpnext/conf/httpd-app2.conf replacing sites/erpnext by sites/NEW_SITE_NAME

  • Edit the file installdir/apache2/conf/bitnami/bitnami-apps-vhosts.conf, duplicate the two existing code blocks and configure them as shown below. firsthostname.com and secondhostname.com are placeholders. Remember to replace them with you preferred host.

     <VirtualHost *:80>
         ServerName firsthostname.com
         ServerAlias www.firsthostname.com
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
    
         Include "installdir/erpnext/conf/httpd-app.conf"
     </VirtualHost>
    
     <VirtualHost *:443>
         ServerName firsthostname.com
         ServerAlias www.firsthostname.com
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
         SSLEngine on
         SSLCertificateFile "installdir/erpnext/conf/certs/server.crt"
         SSLCertificateKeyFile "installdir/erpnext/conf/certs/server.key"
    
         Include "installdir/erpnext/conf/httpd-app.conf"
     </VirtualHost>
    
     <VirtualHost *:80>
         ServerName secondhostname.com
         ServerAlias www.secondhostname.com
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
    
         Include "installdir/erpnext/conf/httpd-app2.conf"
     </VirtualHost>
    
     <VirtualHost *:443>
         ServerName secondhostname.com
         ServerAlias www.secondhostname.com
         DocumentRoot "installdir/erpnext/htdocs/frappe-bench/sites/"
         SSLEngine on
         SSLCertificateFile "installdir/erpnext/conf/certs/server.crt"
         SSLCertificateKeyFile "installdir/erpnext/conf/certs/server.key"
    
         Include "installdir/erpnext/conf/httpd-app2.conf"
     </VirtualHost>
    
  • Restart the Apache server:

     $ sudo installdir/ctlscript.sh restart apache
    

Now, you should be able to access your first site using firsthostname.com. To access your second site enter secondhostname.com in your preferred browser. The credentials for the first site are the same credentials from the original ERPNext installation. The credentials for the second site are Administrator as username and the password you specified when creating the new site using bench.

nativeInstaller

Bitnami Documentation