Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Forums
  • Support Installation & Updates

Content

Migrate from Docker Compose to Packaged

Added by Mircea Marin over 1 year ago

Hi,

we are currently testing OpenProject (v. 11.2.3) internally and have it deployed through docker-compose. We are thinking about starting to use the tool productively but not as docker-compose. Instead we want to use the RPM version. We would also like to keep the data that is already available in the test instance. My question is, how would we be doing this the right way? Is it enough to dump the PostgreSQL DB from our test instance and restore it in the "live" one? Or should we take anything else into account? I could not find any guides for migrating from docker-compose to packaged installation.

Thanks!


Replies (2)

RE: Migrate from Docker Compose to Packaged - Added by Mircea Marin over 1 year ago

Here's part of the answer (in case you don't have custom settings or attachments) - covers the migration of the database. I hope this works for you but if it doesn't, I probably can't help you!

  1. Backup your docker database as described here: Backing up your OpenProject installation | OpenProject Help & Documentation
  2. Copy the dump (openproject.sql) to the new server. Note down the location.
  3. On the new system, install OpenProject as described here: Install OpenProject with DEB/RPM packages | OpenProject Help & Documentation
  4. NOTE: we're using CentOS 8 and for some reason the OpenProject configuration wants to install PostgreSQL 9.4 which is not supported in this version anymore. As such, we had to install the PostgreSQL database separately. We used PostgreSQL 13. We used the official instructions from here: PostgreSQL: Linux downloads (Red Hat family)
  5. Setup your database:
[root@host] su - postgres
[postgres@host] createuser -P -d openproject
[postgres@host] createdb -O openproject openproject
  1. Run the configuration script as described here: Install OpenProject with DEB/RPM packages | OpenProject Help & Documentation
  2. For the step about configuring the database, select "Use an existing database" and enter the connection details of the DB you just set up
  3. Finish the setup and test that OpenProject works (for now with an empty database)
  4. Once everything works, we need to import the data you exported in the first step by doing these steps:
[root@host] service openproject stop
[root@host] su - postgres -c psql
postgres=# DROP DATABASE openproject;
postgres=# CREATE DATABASE openproject OWNER openproject;
postgres=# \c openproject
openproject=# \i /path/to/openproject.sql
# make sure all commands run without errors!
openproject=# \q

At this point you already imported the database (if all went well) but the problem is that the importing of the data in the previous step messed up with the permissions for the tables in the "openproject" database. For this I used a script that changes all permissions for the tables in the "openproject" database which I found here: Changes the owner on all tables, sequences, views, and functions in a PostgreSQL database with support for identifiers with whitespace and non-public schemas. · GitHub

[root@host] nano pg_change_schema_owner.sh
# paste the sctipt mentioned earlier and save the file
[root@host] chmod u+x pg_change_schema_owner.sh
[root@host] ./pg_change_schema_owner.sh -d openproject -o openproject
# make sure the script executes without errors
[root@host] reboot

If all went well you can now access OpenProject at the new location. If not, then try running sudo openproject configure to re-run the configuration steps. Lastly, if all else fails, check the logs sudo openproject logs

Hope this helps!

RE: Migrate from Docker Compose to Packaged - Added by Connor Moroney over 1 year ago

I ended up answering alot of these myself.
Did you end up needing the old Database password for the import? (NO)

Do you need to know the path to the current database location?(NO)

This was a huge help, thanks so much, i managed to migrate my install from docker to self sustainable in no time thanks to you and your work.

  • (1 - 2/2)
Loading...