Synchronizing UNA testserver installation with production server copy

Dear UNA experts,

I run a stable development/test server copy of UNA 11.0.4 (love it!) on a shared hosting system. In February next year we want to go live with our community. As the system admin I tweak and twist all the available settings to my community's unique needs and I test all of the interesting power apps (looking therefore forward to Andrew's idea to make them available for free until frequent usage on production sites) in that environment. Some moderators have also access to this test installation in order to test new updates and functionality with me.

My question is, how can I transfer all of my settings from that test/development server to a live/production server? Would you recommend using a tool like FreeFileSync?

I am aware of the fact, that there are server unique files like .htaccess, which must not copied to the live server. Which files to include and which to exclude from synching? I'm pretty sure that all of the cache files shouldn't be synched, for example.

I couldn't find anything on that in the search.

Cheers, thomlin

  • 596
  • More
Replies (4)
    • We usually use the following approach, in case you are using some cloud provider and have cloning functionality. So usually there is one production instance, however when you need to test some changes, then production instance is cloned and changes are tested on cloned version first, if everything is fine then same changes can be applied to the production instance. However there are some caveats, like stopping email/push queue and/or disabling cron, in case of remote storage some more actions needed.

      UNA Cloud supports cloning as well with automatic change of hostname for cloned instance.

      • Hello Alex T⚜️ 

        I would like to know how to do it this way:
        Production instance: production(.)com and

        Testing instance:  testing.production(.)com

        What do we need to change after rsyncing (copying) production to subdomain testing.production(.)com?

        Where to change the testing URL and what else do we need to change so that the testing.production(.)com will work? What about DB (we are using MySQL - Ubuntu 20.04 LTS LAMP server )?

        Thank you.

        Mayki

        • You need to change inc/header.inc.php file only.

          However I wouldn't recommend to do it this way, if you want to sync files then you can use git for it so all changes will be versioned, also you can add only particular files to the repository, so you can exclude inc/header.inc.php, storage, etc - so you will not need to change inc/header.inc.php after pulling changes from the repo.

            Login or Join to comment.