Apache2 Default Page

Willkommen Foren LogoControl Apache2 Default Page

3 Beiträge anzeigen - 1 bis 3 (von insgesamt 3)
  • Autor
    Beiträge
  • #3444
    Heiper
    Teilnehmer

    Sehr geehrte Gemeinde ich benötige noch einmal eure Hilfe und hoffe ihr wisst eine Lösung oder konntet selber schonmal das Problem lösen.
    Und zwar habe ich vor ein paar Tagen erfolgreich meine LogoControl in Betrieb nehmen können und für mich konfigurieren können.
    Bis dann gestern diese Meldung kam:

    Debian Logo Apache2 Debian Default Page
    It works!

    This is the default welcome page used to test the correct operation of the Apache2 server after installation on Debian systems. If you can read this page, it means that the Apache HTTP server installed at this site is working properly. You should replace this file (located at /var/www/html/index.html) before continuing to operate your HTTP server.

    If you are a normal user of this web site and don’t know what this page is about, this probably means that the site is currently unavailable due to maintenance. If the problem persists, please contact the site’s administrator.
    Configuration Overview

    Debian’s Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Debian tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz. Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server.

    The configuration layout for an Apache2 web server installation on Debian systems is as follows:

    /etc/apache2/
    |– apache2.conf
    | `– ports.conf
    |– mods-enabled
    | |– *.load
    | `– *.conf
    |– conf-enabled
    | `– *.conf
    |– sites-enabled
    | `– *.conf

    apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server.
    ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime.
    Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively.
    They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod, a2dismod, a2ensite, a2dissite, and a2enconf, a2disconf . See their respective man pages for detailed information.
    The binary is called apache2. Due to the use of environment variables, in the default configuration, apache2 needs to be started/stopped with /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not work with the default configuration.

    Document Roots

    By default, Debian does not allow access through the web browser to any file apart of those located in /var/www, public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv) you may need to whitelist your document root directory in /etc/apache2/apache2.conf.

    The default Debian document root is /var/www/html. You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box.
    Reporting Problems

    Please use the reportbug tool to report bugs in the Apache2 package with Debian. However, check existing bug reports before reporting a new bug.

    Please report bugs specific to modules (such as PHP and others) to respective packages, not to the web server itself.

    Wenn ich es richtig übersetzt habe soll ich die Datei unter /var/www/html/index.html ersetzen ja soweit so gut aber sogegen und voralem wie ?

    Ich hoffe Ihr habt Tipps und Ratschläge für mich

    Wünsche euch noch einen schönen Abend

    Freundliche Grüße
    Tobi

    #3460
    jphermans
    Teilnehmer

    Hello, you don’t need apache to let LogoControl running on a linux server.
    Just install for example ubuntu server 32bit version and follow the install notes for installing on RPi.
    After that copy libnodave.so to Logocontrol and delete the arm version. In logocontrol.exe.conf change the

    <dllmap dll="libnodave.dll" target="libnodave-arm.so" />' to libnodave.so.

    Then do a start.sh and everything should work.
    if you use another username then pi make also following changes in init.sh before installing

    echo ======================================================================
    echo -n "Create Autorun entry in rc.local: "
    if grep -Fq "LogoControl" /etc/rc.local
    then
        echo Skipped! Entry already exits in rc.local 
    else
    	sudo sed -i -e '/^exit 0/i\# Start LogoControl\nsu pi -c "nohup /home/pi/LogoControl/start.sh &"\n' /etc/rc.local
    	echo entry was created in rc.local
    fi
    echo ======================================================================
    

    Change /home/pi/LogoControl/start.sh –> /home/your username/LogoControl/start.sh and also every place where you see pi.
    It is much easier to create a pi user in linux then these lines are not needed.

    • Diese Antwort wurde vor vor 7 Jahren, 5 Monaten von jphermans bearbeitet.
    • Diese Antwort wurde vor vor 7 Jahren, 5 Monaten von jphermans bearbeitet.
    #3491
    stpg
    Teilnehmer

    Nochmal auf Deutsch. LogoControl liefert den Webdienst gleich mit.
    Installieren und via IP:Port aufrufen. (z.b 192.168.2.20:8088)
    Möchtest du die angezeigte Webseite verändern sehe unter „\Remote\Resources\index.st“ nach.
    Und natürlich die CSS Datein dazu nicht vergessen.

3 Beiträge anzeigen - 1 bis 3 (von insgesamt 3)
  • Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.