localhost/concerto not working on Apache 2.4 Alias Config for Concerto 2 on Ubuntu 14.04.2

[Ted]

Hello Everyone,

Concerto is great!

This is my first post after enjoying lots of experiments with Concerto on Ubuntu and Raspbery Pi servers. I hope you can help.

The problem is with a clean install of Concerto 2 on Ubuntu 14.04.2 LTS using the LAMP server with Apache 2.4.

The install was flawless.  Everything worked great and the default Concerto 2 login and setup admin page shows up in the browser on my localhost.

The problem comes in when I try to move concerto from "localhost" to "localhost/concerto"

I need to move Concerto to "localhost/concerto" because of other servers and services on the Apache2 server. 

For instance there is a Weewx weather station that is available at "localhost/weewx/public_html".  It is no longer available when Concerto is at "localhost".  So I need to move concerto to "localhost/concerto", so that Weewx and other services can run and display in the browser using Apache 2.  This way their output is available to the browser and for use in Concerto as content.

Somehow I have created a configuration where concerto does not run at "http://localhost/concerto/" it results in the display of "Index of /concerto" with the directories, files and dates.

Maybe I just need to know what file in that index is the link to click, to start Concerto in the browser. Is it that simple?

My guess is that I have overcomplicated what should be a simple change to
/etc/apache2/sites-available/concerto.conf

After multiple tries at editing concerto.conf (editing as sudo and using, a2ensite and reloading the service, as required), I figured there must be something more to it.  So I added a "concerto" symlink from /var/www/html back to /usr/share/concerto (both are Owner www-data Create and Delete : Group www-data access)  This symlink with the current configuration file /etc/apche2/sites-available/concerto.conf
is what allows me to see the "Index of /concerto" and that seems to be the closest I can get to returning to the working Concerto configuration at the desired location of localhost/concerto.

This is the current concerto.conf file

<VirtualHost *:80>
    Alias /concerto/ "/var/www/html/concerto/"
    <Directory "/var/www/html/concerto/">
        RackEnv production
        Options Indexes Includes FollowSymlinks
        AllowOverride all
        Options -MultiViews
        Require all granted
    </Directory>
  PassengerMinInstances 3
</VirtualHost>

Other edits that did not work when used in /etc/apache2/sites-available/concerto.conf
Did not work
    Alias /concerto/ "/usr/share/concerto/"
    <Directory "/usr/share/concerto/">

Did not work
    Alias /concerto/ "/var/www/html/concerto/"
    <Directory "/usr/share/concerto/">

I am familiar with Linux and LAMP servers and am learning about the new requirements of Apache 2.4 but I am not familiar with how Concerto works "under the hood" with Ruby and Gems and all that special magic that you do.  :-)  I am willing to learn, I am here to learn, but I am not sure if it is as simple as some line in the configuration or if it is more complex in terms of how you must call Concerto to run.

I can give any log files, data or any thing that will help you.  I am willing to do any homework that I need to but I have been working on this for days and have searched and tried everything I can think of. Please help.

Sorry for the long post.   Hopefully it gives you all that you need.

Thank you for any help you can offer.  Concerto is great!

[August]

My guess would be is that the Concerto Ruby on Rails application is not getting properly deployed. Deploying a Rails application in a sub-URI scenario has always been a bit of a mess. Since you’re using Passenger to do this, I would suggest this little article as a starting point: https://www.phusionpassenger.com/documentation/Users%20guide%20Apache.html#deploying_rack_to_sub_uri

-- 
August

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-s...@googlegroups.com.
To post to this group, send email to concerto-dig...@googlegroups.com.
Visit this group at http://groups.google.com/group/concerto-digital-signage.
For more options, visit https://groups.google.com/d/optout.

[August]

My guess would be is that the Concerto Ruby on Rails application is not getting properly deployed. Deploying a Rails application in a sub-URI scenario has always been a bit of a mess. Since you’re using Passenger to do this, I would suggest this little article as a starting point: https://www.phusionpassenger.com/documentation/Users%20guide%20Apache.html#deploying_rack_to_sub_uri

 

-- 
August

On July 24, 2015 at 8:38:57 AM, Ted (kmjt...@comcast.net) wrote:

[Ted]

Hi August,

Thank you for your help! 

I had tried everything I could think of.  The new starting point and what to try next were exactly what I needed.  Phusion and Ruby on Rails are the parts of the puzzle that I don't know much about.  In the past I had gotten Concerto to run successfully on the same server as Weewx and Motion (for a webcam).  I am willing to do the work to make it happen again on this new, updated install.  Just didn''t know if it was not possible any more for some reason...

Thanks for the guidance.  I will make the changes and do a little homework to see if I can understand exactly what I am doing and hopefully that will get Concerto running again.

Thanks for taking the time to help.

Ted