<div dir="ltr"><div><div><div><div><div><div><div><div>Hi Zack,<br><br></div>Thanks for the explanation.<br><br></div>I was confused about my old setup (I have not dug into it for years). My 2.0.2 setup is actually only involving /var/www/CDash, everything is there, including the minimal config.local.php. Forget everything I said about whatever is in my home directory, this was my first try a long time ago.<br><br></div><div>Unfortunately, I am not able to log as administrator in the new CDash (step 10 below)<br></div><div><br></div>Now here is what I did to move to 2.4.0:<br></div>1. Stop apache2: sudo systemctl stop apache2<br></div>2. Save the CDash DB: sudo -u postgres pg_dump -U postgres cdash > cdashbackup.sql<br></div>3. Move the old cdash: cd /var/www ; mv CDash CDashOld<br></div>4. unpack cdash 2.4.0 at /var/www/CDashRoot, making sure the owner and group are www-data recursively (to match the values in /etc/apache2/envvars APACHE_RUN_USER and APACHE_RUN_GROUP)<br></div><div>5. Copy the old minimal /var/www/CDashOld/cdash/config.local.php into /var/www/CDashRoot/config/ <br></div><div>6. Create a symlink /var/www/CDash->/var/www/CDashRoot/public<br></div><div>7. Restart apache2: sudo systemctl start apache2</div><div><div><div><div><div><div>8. Open the CDash home page, which redirects to CDash/viewProjects.php (by the way, the open page says 2.5.0 not 2.4.0)<br></div><div>9. As documented on the wiki, I have the page with the warning message:The current database schema doesn't match the version of CDash
you are running, upgrade your database structure in the
Administration/CDash maintenance panel of CDash. So far so good.<br></div><div>10. I click on "Login" in the upper left corner to be able to log as administrator, which redirects to CDash/user.php but this is a totally empty page so I cannot proceed further as I cannot even log in as administrator... What am I missing here?<b><br><br></b></div><div>Best,<br><br>--<br></div><div>François Bertel<b><br></b></div><div><br></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jul 9, 2017 at 12:54 AM, François Bertel <span dir="ltr"><<a href="mailto:fbopensource@gmail.com" target="_blank">fbopensource@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,<br><br>I am currently running CDash 2.0.2 and I would like to upgrade to 2.4.0.<br>I am using Ubuntu 17.04 with postgresql 9.6.3.<br><br></div><div>I have some questions about steps 5,6,7 as well as the new "public" hierarchy and<br></div><div>the required "public" symlink.<br></div><div><br>Side note: <a href="https://www.cdash.org/download/" target="_blank">https://www.cdash.org/<wbr>download/</a> is still saying that 2.2.3 is the<br>current stable release but I downloaded CDash-2.4.0.zip from the wiki: <a href="http://public.kitware.com/Wiki/File:CDash-2-4-0.zip" target="_blank">http://public.kitware.com/<wbr>Wiki/File:CDash-2-4-0.zip</a><br><br>I extracted the archive in my home directory at:<br><br>~/install/cdash/cdash-2.4.0<br><br>therefore the root directory is at: ~/install/cdash/cdash-2.4.0/<wbr>CDash<br><br>I see that composer.phar is already part of the archive, I assume that I don't<br>have to apply step 5 of the upgrade, correct?<br><br><a href="https://public.kitware.com/Wiki/CDash:Upgrade#Upgrading_CDash" target="_blank">https://public.kitware.com/<wbr>Wiki/CDash:Upgrade#Upgrading_<wbr>CDash</a><br><br>"step 5: Download composer (if you haven't already) and run php composer.phar install --no-dev --optimize-autoloader."<br><br>Same question for step 6 (npm install) and 7 (gulp). Are they just here for people using git instead or are they mandatory when using the zip archive as well?<br><br>If I need to follow step 6, where do I run "npm install" from? Is is from ~/install/cdash/cdash-2.4.0/<wbr>CDash for me?<br><br>(Note that I installed the Ubuntu packages for composer and npm, the composer package does not provide a composer.phar but /usr/bin/composer instead).<br><br>Last question, where do I setup the symlink to public and do I have to do it? To help you answer my question, here are some details about my current 2.0.2 setup:<br><br>The 2.0.2 is extracted here:<br>~/install/cdash/CDash-2-0-2 where I have a custom config file in ./cdash/config.local.php<br><br>Therefore I will copy my config.local.php to ~/install/cdash/cdash-2.4.0/<wbr>CDash/config/ , right?<br><br>My /var/www looks like this:<br>drwxr-xr-x 4 root root 152 Apr 27 2014 ./<br>drwxr-xr-x 16 root root 432 Apr 21 2016 ../<br>drwx------ 17 www-data www-data 4912 Apr 26 2016 CDash/<br>drwxr-xr-x 2 root root 48 Apr 3 2014 html/<br>-rw-r--r-- 1 root root 177 Oct 19 2013 index.html<br>-rw------- 1 www-data www-data 20 Mar 2 2012 test.php<br><br>In /etc/apache2/,<br><br>./sites-enabled/default-ssl.<wbr>conf and ./sites-enabled/000-default.<wbr>conf<br>are symlink to files in ./sites.available both having DocumentRoot pointing<br>to /var/www<br><br>./conf-enabled/cdash.conf is a symlink to ./conf-available/cdash.conf which is just:<br><Directory /home/fbertel/install/cdash/<wbr>CDash-2-0-2/><br> Order allow,deny<br> Allow from all<br></Directory><br><br>Therefore, I will change it to:<br><Directory /home/fbertel/install/cdash/<wbr>cdash-2.4.0/CDash/><br> Order allow,deny<br> Allow from all<br></Directory><br><br>right? Or is it where I should use "public" instead with the following statement<br>(and not use a symlink) ?<br><br><Directory /home/fbertel/install/cdash/<wbr>cdash-2.4.0/CDash/public/><br> Order allow,deny<br> Allow from all<br></Directory><br><br></div><div>Best,<br></div><div><br>--<br></div>François Bertel<br><br></div>
</blockquote></div><br></div>