{"id":20028784,"url":"https://github.com/phase2/openatrium","last_synced_at":"2025-08-11T14:41:02.017Z","repository":{"id":22989334,"uuid":"26339740","full_name":"phase2/openatrium","owner":"phase2","description":"Open Atrium 2.x.  Release is on drupal.org.  This is dev release for Travis CI testing","archived":false,"fork":false,"pushed_at":"2015-01-19T17:05:07.000Z","size":3944,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":12,"default_branch":"7.x-2.x","last_synced_at":"2025-01-12T17:35:44.466Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Shell","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/phase2.png","metadata":{"files":{"readme":"README.txt","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-11-07T21:57:04.000Z","updated_at":"2022-12-20T19:14:29.000Z","dependencies_parsed_at":"2022-08-21T08:11:02.953Z","dependency_job_id":null,"html_url":"https://github.com/phase2/openatrium","commit_stats":null,"previous_names":[],"tags_count":1,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phase2%2Fopenatrium","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phase2%2Fopenatrium/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phase2%2Fopenatrium/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phase2%2Fopenatrium/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/phase2","download_url":"https://codeload.github.com/phase2/openatrium/tar.gz/refs/heads/7.x-2.x","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":241460048,"owners_count":19966518,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-13T09:16:31.304Z","updated_at":"2025-03-02T04:45:22.617Z","avatar_url":"https://github.com/phase2.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"Open Atrium is a rich distribution of many (150+) Drupal modules. Installing \nOpen Atrium may require additional resources beyond a minimal Drupal 7 \ninstallation.\n\nSystem Requirements\n-------------------\n\nIn addition to the normal Drupal 7 requirements, you should ensure your PHP \nmemory_limit (php.ini) is set to at least 256M and your MySQL \nmax_allowed_packet (my.cnf) is at least 32M.\n\nOn a production Open Atrium site, keep in mind that the nature of \ncollaboration software implies many logged-in users. Caching layers, such \nas Varnish, that are typically used to improve Drupal performance will be \nless effective because authenticated users bypass these caching layers. \nThus, a production environment may require additional database memory and \nresources to handle larger numbers of users. Using a hosting company \nspecifically tailored for Open Atrium can also help. You should not expect \nto run Open Atrium effectively on minimal (cheap) shared VM hosts.\n\nPlease also see Additional OpenAtrium requirements when installing under Aegir.\n\nOne-click installation\n----------------------\n\nHosting companies, such as Pantheon provide an optimized infrastructure for \nOpen Atrium and offer a 1-click installation process. When using Pantheon, \nskip down to the \"Actual Installation\" section for details.\n\nGetting the Open Atrium files\n-----------------------------\n\nBefore you can install Open Atrium, you need to get the files. There are two \ndifferent methods for this:\n\n** Using Releases from Drupal.org (recommended)\n\nOfficial releases of Open Atrium are available on the drupal.org project page. \nClick the link for the \"gz\" or \"zip\" archive of files for the latest release. \nOlder releases are also available, though not recommended. Once you have \ndownloaded this file, use your systems unarchive or unzip software to extract \nall the files from the archive. These files form the \"root\" or top-level of \nyour web site, so transfer them to the appropriate top level location of your \nweb server. This will replace any existing Drupal or other web site that you \nhave, so if you are overwriting existing files, be sure to make a BACKUP first!\n \n** Using \"git\" and \"drush make\" for the latest -dev version (for expert Drupal devs)\n\n(NOTE: These instructions are for *nix-based systems, such as Linux or MacOSX. \nWindows users will need to research how to use these tools on their system).\n\nIf you require the absolute latest development version of Open Atrium, you need \nto be familiar with the \"git\" and \"drush\" tools:\n\n * From a command line shell, run \n     \"git clone --branch 7.x-2.x http://git.drupal.org/project/openatrium.git\" \n   to download the latest version of Open Atrium to the \"openatrium\" folder \n   on your computer.\n\n * Move to that folder using \"cd opentrium\"\n\n * Download and build the files for Open Atrium using the script \n   \"./build.sh path-to-web-server\". For example, if the root of your webserver \n   is in /htdocs/drupal, then you would use \"./build.sh /htdocs/drupal\". \n   This will build OA2 using the latest -dev files from drupal.org. For the \n   *absolute* latest code, you can get the development code from drupal by \n   running \"./build-dev.sh path-to-web-server\" instead. This script requires \n   the \"drush\" command and uses \"drush make\" to download and build all of the \n   dependencies for Open Atrium 2. You should be using at least Drush 5.x.\n\n * If you receive the following error message when you attempt to build the \n   the files, you will need to install the Drupal.org Drush commands.\n\n    \"The drush command 'verify-makefile' could not be found. Run drush \n     cache-clear drush to clear the commandfile cache if you have installed \n     new extensions.\"\n\nUpdating your Open Atrium distribution\n--------------------------------------\n\nIn the future when you wish to update to a newer version of Open Atrium, you \nhave two choices, based on how you originally obtained the files as described \nin the previous section.\n\nIMPORTANT NOTE: Before performing any site updates, it is extremely important \nto BACKUP your Drupal files and MySQL database for your site. Updating Open \nAtrium can cause irreversible changes to the database and if you decide to \nroll back you'll need this backup.\n\n** Updating files from drupal.org (recommended)\n\nSave a copy of your Drupal sites/ directory. This contains any local code or \ncustomization you might have made to your site. Now run the same procedure \nshown above to download the latest version of Open Atrium from drupal.org and \nreplace your entire root web directory with the new version. Finally, replace \nthe copy of the sites/ directory that you previously saved. Follow the \ninstructions in the \"Clearing Cache\" section below to update your database and \nyour site should be updates.\n \n** Updating the latest -dev version (for expert Drupal devs)\n\nIf you built your site using \"git\" and \"drush\" then you can use these same \ntools to update your site. First, save a copy of your Drupal sites/ directory \nas this will be overwritten by the update process. Next, go to the \"openatrium\" \nfolder where you initially used \"git\" to fetch the Open Atrium repository. Use \n\"git pull\" to retrieve the latest version of the distribution. Then run the \n./build.sh or ./build-dev.sh script exactly as before. Instead of pointing \nthese scripts to your root web directory, you can point them to a temp \ndirectory in case the installation fails. The build.sh scripts delete \neverything in the target directory so building to a temp directory prevents \nyour current web site from being lost if the build fails. Once the build is \nsuccessful you can move the temporary directory in place of your web root, \nthen restore the /sites directory that you previously saved.\n\nIf you just need to make a quick update of a specific open atrium module, you \ncan also just go to that module directory and use \"git pull origin\" to pull \nin the latest changes without rebuilding the entire distribution.\n\nDo NOT update Drupal core or any modules within Open Atrium 2 manually unless \nyou are an expert Drupal developer who knows exactly what you are doing. \nDrupal Distributions such as Open Atrium are a complex collection of many \nmodules, often with specific patches to make them work together. If you update \na module manually you can easily break your Open Atrium site. The Open Atrium \ndistribution is regularly updated with security patches and new features and \nis constantly evaluating new versions of modules. The advantage of using a \ndistribution is to let other people handle the headache of updating modules \nand keeping them all working together.\n\nClearing Cache\n--------------\n\nIf you are installing for the first time, ignore this section. If you are \nupdating your Open Atrium distribution you'll need to run a couple of commands \nto clear the drupal cache and update your database:\n\ndrush updb\n    This is the same as running the update.php script on your site and is \n    needed to run any update hooks required for the new version.\ndrush rr\n    This is an OPTIONAL command but is sometimes needed if modules or files \n    have moved to a different directory location within Open Atrium. If you \n    get weird errors when clearing cache after an update, try this command. \n    It is a shortcut for the \"registry rebuild\" command which might need to \n    be installed into drush separately.\ndrush cc all\n    This clears the Drupal database cache and is the same as clicking \"Clear \n    All Caches\" from the admin/config/development/performance page on your \n    site. This drush command lets you clear cache from the command line more \n    quickly.\ndrush fra -y (Read notes first)\n    This command is required to update all of Open Atrium's features to the \n    latest version. Running it will revert and overwrite any existing \n    features, including any changes that you may have made to Open Atrium's \n    configuration. It is therefore very important to capture any customization \n    using the Features Override module before running this command. This \n    command can be run at any other time to restore Open Atrium's features to \n    their default settings (Eg: if someone has inadvertently tampered with any \n    Views or layouts within Open Atrium).\n\nActual Installation\n-------------------\n\nTo install Open Atrium the first time, you will run the \"install.php\" script \nfrom your web browser. NOTE when using a hosting company such as Pantheon, it \nwill run install.php for you. The Install script will take you through \nmultiple pages of steps. There is very little difference between this process \nand a normal Drupal site installation except that it takes longer to install \nthe large number of modules. \n\nIf you are a Maintainer of Open Atrium, you should copy the gitignore.example \nfile to .git/info/exclude to avoid adding extra files to the repository.\n\nThe most common problem encountered during installation is the lack of system \nresources on your web server. Be sure to follow the instructions in the System \nRequirements section shown above. If you still have trouble, try doing a plain \nDrupal 7 installation using the links in the previous section to ensure that \nyour host is capable of installing Drupal itself.\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fphase2%2Fopenatrium","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fphase2%2Fopenatrium","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fphase2%2Fopenatrium/lists"}