Web based groupware server written in PHP, forum at https://help.egroupware.org/
Go to file
2025-02-20 17:27:25 -07:00
addressbook * Addressbook: use a hierarchical list to show distribution lists incl. groups (if groups are enabled) 2025-02-20 15:19:18 +01:00
admin fix create application token got editable 2025-02-20 09:55:40 +01:00
api Some more memory cleanup 2025-02-20 17:27:25 -07:00
calendar
doc
emailadmin
filemanager Et2File: Improvements for handling larger files 2025-02-18 14:47:18 -07:00
files
home
importexport Change Import Export navbar item 2025-02-20 12:03:59 +01:00
infolog
kdots Fix slotted templates / components weren't slotting properly in kdots 2025-02-10 17:22:43 -07:00
mail WIP hide From in mail compose header 2025-02-20 18:17:25 +01:00
notifications
pixelegg preferences hint styling changes 2025-02-13 16:55:56 +01:00
preferences * Admin/Preferences: allow to use templates for creating application-passwords (and optionally limit groups to just use pre-existing templates) 2025-02-18 12:12:44 +01:00
resources
saml
setup
timesheet
.gitignore
.htaccess
.travis.yml
about.php
composer.json
composer.lock
groupdav.htaccess
groupdav.php
Gruntfile.js
header.inc.php.template
icons-new.html
index.php
install-cli.php
json.php
LICENSE.md
login.php
logout.php
manifest.json
move-images
package-lock.json
package.json
README.md
redirect.php
remote.php
rollup.config.js
SECURITY.md
service-worker.js
share.php
status.php
tsconfig.json
updateGruntfile.php
web-test-runner.config.mjs Et2File WIP 2025-02-10 14:05:10 -07:00
webdav.php

EGroupware

Tools Usage
Travis CI runs unit-tests after each commit
Scrutinizer CI scrutinizer runs static analysis on our codebase
BrowserStack manual testing with unusual browser versions or platforms

Default and prefered installation method for EGroupware is via your Linux package manager:

Every other method (including a developer installation by cloning the repo) is way more complicated AND does not include all features, as part's of EGroupware are running in different containers, eg. the push-server!

Installing EGroupware 23.1 via Docker for non-Linux environments or not supported Linux distros:

EGroupware 23.1 can be installed via Docker, in fact the DEB/RPM packages also does that. Instructions on how to run EGroupware in Docker are in our Wiki and in doc/docker subdirectory.

Installing EGroupware development version via Docker:

Deprecated EGroupware development installation:

apt/yum/zypper install nodejs
npm install -g grunt-cli
  • install EGroupware and dependencies
cd /path/to/your/docroot
git clone https://github.com/EGroupware/egroupware.git # or git@github.com:EGroupware/egroupware.git for ssh
cd egroupware
./install-cli.php
  • install non-default EGroupware apps by cloning them into your egroupware directory eg.
cd /path/to/your/egroupware
git clone https://github.com/EGroupware/wiki.git

Keeping EGroupware up to date or switch to release branch:

cd /path/to/your/egroupware
./install-cli.php [<change-channel>]
setup/setup-cli.php # will tell you if a schema-update is necessary

install-cli.php supports the following "channels":

  • release: taged maintenance releases only eg. 19.1.20200701
  • bugfix: release-branch incl. latest bugfixes eg. 20.1, if you are currently on 20.1.20200710
  • <branch>: switch to given branch
  • master: latest development for next release

To change the channel, call install-cli.php <channel-to-update-to>.

For further instalation instructions see our wiki.