##// END OF EJS Templates
u » pc » rhodecode-enterprise-ce-fork-pc
RSS

Fork of rhodecode-enterprise-ce

auth: don't break hashing in case of user with empty password....
auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.
marcink - - Load All Authors

File last commit:

r111:0e0e958e default
r2203:8a18c3c3 default
Show More
system-overview.rst
171 lines | 3.6 KiB | text/x-rst | RstLexer
/ docs / admin / system-overview.rst
History | Annotation | Raw |Copy content |Copy permalink

System Overview

Latest Version

  • |release| on Unix and Windows systems.

System Architecture

The following diagram shows a typical production architecture.

../images/architecture-diagram.png

Supported Operating Systems

Linux

  • Ubuntu 14.04
  • CentOS 6.2 and 7
  • Debian 7.8
  • RedHat Fedora
  • Arch Linux
  • SUSE Linux

Windows

  • Windows Vista Ultimate 64bit
  • Windows 7 Ultimate 64bit
  • Windows 8 Professional 64bit
  • Windows 8.1 Enterprise 64bit
  • Windows Server 2008 64bit
  • Windows Server 2008-R2 64bit
  • Windows Server 2012 64bit

Supported Databases

  • SQLite
  • MySQL
  • MariaDB
  • PostgreSQL

Supported Browsers

  • Chrome
  • Safari
  • Firefox
  • Internet Explorer 10 & 11

System Requirements

|RCM| performs best on machines with ultra-fast hard disks. Generally disk performance is more important than CPU performance. In a corporate production environment handling 1000s of users and |repos| you should deploy on a 12+ core 64GB RAM server. In short, the more RAM the better.

For example:

  • for team of 1 - 5 active users you can run on 1GB RAM machine with 1CPU
  • above 250 active users, |RCM| needs at least 8GB of memory. Number of CPUs is less important, but recommended to have at least 2-3 CPUs

Configuration Files

  • :file:`/home/{user}/.rccontrol/{instance-id}/rhodecode.ini`
  • :file:`/home/{user}/.rccontrol/{instance-id}/mapping.ini`
  • :file:`/home/{user}/.rccontrol/{vcsserver-id}/vcsserver.ini`
  • :file:`/home/{user}/.rccontrol/supervisor/supervisord.ini`
  • :file:`/home/{user}/.rccontrol.ini`
  • :file:`/home/{user}/.rhoderc`
  • :file:`/home/{user}/.rccontrol/cache/MANIFEST`

For more information, see the :ref:`config-files` section.

Log Files

  • :file:`/home/{user}/.rccontrol/{instance-id}/enterprise.log`
  • :file:`/home/{user}/.rccontrol/{vcsserver-id}/vcsserver.log`
  • :file:`/home/{user}/.rccontrol/supervisor/supervisord.log`
  • :file:`/tmp/rccontrol.log`
  • :file:`/tmp/rhodecode_tools.log`

Storage Files

  • :file:`/home/{user}/.rccontrol/{instance-id}/data/index/{index-file.toc}`
  • :file:`/home/{user}/repos/.rc_gist_store`
  • :file:`/home/{user}/.rccontrol/{instance-id}/rhodecode.db`
  • :file:`/opt/rhodecode/store/{unique-hash}`

Default Repositories Location

  • :file:`/home/{user}/repos`

Connection Methods

  • HTTPS
  • SSH
  • |RCM| API

Internationalization Support

Currently available in the following languages, see Transifex for the latest details. If you want a new language added, please contact us. To configure your language settings, see the :ref:`set-lang` section.

Licencing Information

  • See licencing information here

Peer-to-peer Failover Support

  • Yes

Additional Binaries

  • Yes, see :ref:`rhodecode-nix-ref` for full details.

Remote Connectivity

  • Available

Executable Files

Windows: :file:`RhodeCode-installer-{version}.exe`

Deprecated Support

  • Internet Explorer 8 support deprecated since version 3.7.0.
  • Internet Explorer 9 support deprecated since version 3.8.0.