1.3 Installation

  1. 3 weeks ago

    I'm eager to start testing this beta. I do have a question before I get started though: since this is a fresh installation and has a lot of code rework, is it possible to pull the database over from 1.2.1?

    Not yet, I need to create a database update script. I won't have that ready until the next beta.

  2. clonedeploy

    Aug 29 Administrator Answer

    Not yet, I need to create a database update script. I won't have that ready until the next beta.

  3. Alright, I'll prop up a new host and start tinkering then. Thank you!

  4. last week

    One thing I have noticed, if I uninstall 1.2.1 completely and remove all the folders and reinstall 1.3.0 it does not seem to work correctly with the IIS or if you reinstall 1.3.0 it does not work.

    I want to thank you thou - 1.3 is looking very good and I know I appreciate all that you have done and continue to do.

  5. Edited last week by calbrecht

    Our Server Admin found a work around to this issue -

    In IIS:

    If there’s a default website, delete it, then:

    • Add website
    • Site name: clone deploy
    • Physical path:
    o C:\Program Files (x86)\clonedeploy\frontend
    o Hostname: site_acronym.clonedeploy.XXXXXXXX.net
    • Right click on the new site- add application
    o Alias- API
    o Physical path: C:\Program Files (x86)\clonedeploy\application

  6. clonedeploy

    Sep 13 Administrator

    You are correct. When installing 1.3.0 on a server that already had 1.2 there will be some manual steps required similar to what you have described.

 

or Sign Up to reply!