[Ubuntu-cat] Dubte montar servidor en ubuntu
Aniol Martí
amarti a caliu.cat
dis jun 3 17:36:24 UTC 2017
On 06/03/17 19:22, Joan Carles wrote:
> Hola!
> Fet i sí aparex. Mira imatge
>
> 2017-06-02 20:47 GMT+02:00 Aniol Martí <amarti a caliu.cat
> <mailto:amarti a caliu.cat>>:
>
> On 06/02/17 18:14, Joan Carles wrote:
>> El 02/06/17 a les 08:02, Aniol Martí ha escrit:
>>> On 06/02/17 07:11, Joan Carles wrote:
>>>> El 01/06/17 a les 23:52, Aniol Martí ha escrit:
>>>>> On 06/01/17 20:43, Joan Carles wrote:
>>>>>>
>>>>>> Bona tarda!
>>>>>>
>>>>>> Bo, com neòfit en informàtica, encara que molts anys fent
>>>>>> servir ubuntu em trobe amb un problema, que a veure si podeu
>>>>>> ajudar-me.
>>>>>>
>>>>>> Estic fent un curs de edició i publicació pàgines
>>>>>> web(html5,css3, javascript), el tema que més m'interessa surt
>>>>>> quan hem de pasar els fitxers a un servidor local amb php per
>>>>>> penjar el darrer projecte i ver la web final pública.
>>>>>>
>>>>>> A classe treballem amb windows(Vista) i ens han fet
>>>>>> instal.lar, al pen on guardem la feina de cada dia, el
>>>>>> UsbServer i podem accedir, però a casa amb Ubuntu 16.04, he
>>>>>> seguit les passes que he trobat al web de
>>>>>>
>>>>>> http://infinitubuntu.blogspot.com.es/2016/04/montar-servidor-web-ubuntu-16.04-lamp-php-mysql-apache2.html
>>>>>> <http://infinitubuntu.blogspot.com.es/2016/04/montar-servidor-web-ubuntu-16.04-lamp-php-mysql-apache2.html>
>>>>>>
>>>>>> i cap problema a l'instal.lació però després no puc llegir
>>>>>> els fitxers php i realment no se per on surtir per què el
>>>>>> professor m'ha dit que ell amb temes de casa no pot fer res
>>>>>> (i ho veig lògic) i clar el temps que tinc s'escurça i no puc
>>>>>> fer feina a casa.
>>>>>>
>>>>>> He trobat un Linux Usb Server
>>>>>> <https://www.virtualhere.com/usb_server_software> però no se
>>>>>> si pot servir-me.
>>>>>>
>>>>>> Potser us falta informació del que tinc al meu equip però ara
>>>>>> mateix no se quina proporcionar-vos.
>>>>>>
>>>>>> Si algú pot donar-me un cop de mà o indicació possible,
>>>>>> s'agrairia.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Salutacions,
>>>>>>
>>>>>> Joan Carles
>>>>>> Usuari GNU/Linux #324197#
>>>>>> http://counter.li.org/
>>>>>>
>>>>>>
>>>>>>
>>>>> Hola Joan Carles,
>>>>>
>>>>> Prova de crear el fitxer *info.php* al directori
>>>>> */var/www/html *del servidor web. El fitxer ha de contenir
>>>>> aquestes línies:
>>>>>
>>>>> |<?php // Show all information, defaults to INFO_ALL phpinfo(); ?>|
>>>>>
>>>>>
>>>>> Un cop fet, obre un navegador i accedeix a
>>>>> http://127.0.0.1/info.php a veure què et surt.
>>>>>
>>>>>
>>>>> Salut!
>>>>>
>>>>>
>>>>> ||
>>>>> --
>>>>> Aniol Martí gpg C6F0514F
>>>>> http://www.aniolmarti.cat <https://www.aniolmarti.cat>
>>>>>
>>>>> Linux Registered User #614499
>>>>> __________________________________________
>>>>> P Abans d'imprimir aquest correu pensa bé si és necessari fer-ho.
>>>>>
>>>>>
>>>> Hola!
>>>>
>>>> Doncs em surt, que no puc accedir. Afegeixo captura pantalla també.
>>>>
>>>> --
>>>> Salutacions,
>>>>
>>>> Joan Carles
>>>> Usuari GNU/Linux #324197#
>>>> http://counter.li.org/
>>>>
>>>>
>>>>
>>> Bon dia!
>>>
>>> M'he mirat la guia que vas seguir i diria que ja veig d'on ve el
>>> problema. A la guia et suggereixen que canviïs l'arrel del
>>> servidor web a un directori del teu home (en aquest cas sitios).
>>> Suposant que vas crear el directori "Sitios" dins del teu home
>>> fes un "chown -R <ElTeuUsuari>:www-data
>>> /home/ElTeuUsuari/Sitios". Per assegurar que les configuracions
>>> estiguin bé, ens podries passar el contingut dels fitxers
>>> /etc/apache2/apache2.conf i
>>> /etc/apache2/sites-available/000-default.conf ? Per fer-ho, et
>>> suggereixo que utilitzis una eina com l'etherpad de Mozilla [0].
>>>
>>>
>>> [0]: https://public.etherpad-mozilla.org/
>>> <https://public.etherpad-mozilla.org/>
>>>
>>>
>>> Salut!
>>>
>>>
>>> --
>>> Aniol Martí gpg C6F0514F
>>> http://www.aniolmarti.cat <https://www.aniolmarti.cat>
>>>
>>> Linux Registered User #614499
>>> __________________________________________
>>> P Abans d'imprimir aquest correu pensa bé si és necessari fer-ho.
>>>
>>>
>> Hola!
>>
>> Si ho faig amb l'eina que dius. No em deixa:
>>
>> Cannot GET /p//etc/apache2/sites-available/000-default.conf i
>> Cannot GET /p//etc/apache2/apache2.conf
>>
>> No se per què se li posa una p, quan he mirat i no tenia cap
>> espai davant. Per tant t'envie el contingut dels fitxers a qui sota.
>>
>> Del segon:
>>
>> # This is the main Apache server configuration file. It contains the
>> # configuration directives that give the server its instructions.
>> # See http://httpd.apache.org/docs/2.4/
>> <http://httpd.apache.org/docs/2.4/> for detailed information about
>> # the directives and /usr/share/doc/apache2/README.Debian about
>> Debian specific
>> # hints.
>> #
>> #
>> # Summary of how the Apache 2 configuration works in Debian:
>> # The Apache 2 web server configuration in Debian is quite
>> different to
>> # upstream's suggested way to configure the web server. This is
>> because Debian's
>> # default Apache2 installation attempts to make adding and
>> removing modules,
>> # virtual hosts, and extra configuration directives as flexible
>> as possible, in
>> # order to make automating the changes and administering the
>> server as easy as
>> # possible.
>>
>> # It is split into several files forming the configuration
>> hierarchy outlined
>> # below, all located in the /etc/apache2/ directory:
>> #
>> # /etc/apache2/
>> # |-- apache2.conf
>> # | `-- ports.conf
>> # |-- mods-enabled
>> # | |-- *.load
>> # | `-- *.conf
>> # |-- conf-enabled
>> # | `-- *.conf
>> # `-- sites-enabled
>> # `-- *.conf
>> #
>> #
>> # * apache2.conf is the main configuration file (this 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
>> # supposed to determine listening ports for incoming
>> connections which 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.
>>
>>
>> # Global configuration
>> #
>>
>> #
>> # ServerRoot: The top of the directory tree under which the server's
>> # configuration, error, and log files are kept.
>> #
>> # NOTE! If you intend to place this on an NFS (or otherwise network)
>> # mounted filesystem then please read the Mutex documentation
>> (available
>> # at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>
>> <http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
>> # you will save yourself a lot of trouble.
>> #
>> # Do NOT add a slash at the end of the directory path.
>> #
>> #ServerRoot "/etc/apache2"
>>
>> #
>> # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
>> #
>> #Mutex file:${APACHE_LOCK_DIR} default
>>
>> #
>> # The directory where shm and other runtime files will be stored.
>> #
>>
>> DefaultRuntimeDir ${APACHE_RUN_DIR}
>>
>> #
>> # PidFile: The file in which the server should record its process
>> # identification number when it starts.
>> # This needs to be set in /etc/apache2/envvars
>> #
>> PidFile ${APACHE_PID_FILE}
>>
>> #
>> # Timeout: The number of seconds before receives and sends time out.
>> #
>> Timeout 300
>>
>> #
>> # KeepAlive: Whether or not to allow persistent connections (more
>> than
>> # one request per connection). Set to "Off" to deactivate.
>> #
>> KeepAlive On
>>
>> #
>> # MaxKeepAliveRequests: The maximum number of requests to allow
>> # during a persistent connection. Set to 0 to allow an unlimited
>> amount.
>> # We recommend you leave this number high, for maximum performance.
>> #
>> MaxKeepAliveRequests 100
>>
>> #
>> # KeepAliveTimeout: Number of seconds to wait for the next
>> request from the
>> # same client on the same connection.
>> #
>> KeepAliveTimeout 5
>>
>>
>> # These need to be set in /etc/apache2/envvars
>> User ${APACHE_RUN_USER}
>> Group ${APACHE_RUN_GROUP}
>>
>> #
>> # HostnameLookups: Log the names of clients or just their IP
>> addresses
>> # e.g., www.apache.org <http://www.apache.org> (on) or
>> 204.62.129.132 (off).
>> # The default is off because it'd be overall better for the net
>> if people
>> # had to knowingly turn this feature on, since enabling it means that
>> # each client request will result in AT LEAST one lookup request
>> to the
>> # nameserver.
>> #
>> HostnameLookups Off
>>
>> # ErrorLog: The location of the error log file.
>> # If you do not specify an ErrorLog directive within a <VirtualHost>
>> # container, error messages relating to that virtual host will be
>> # logged here. If you *do* define an error logfile for a
>> <VirtualHost>
>> # container, that host's errors will be logged there and not here.
>> #
>> ErrorLog ${APACHE_LOG_DIR}/error.log
>>
>> #
>> # LogLevel: Control the severity of messages logged to the error_log.
>> # Available values: trace8, ..., trace1, debug, info, notice, warn,
>> # error, crit, alert, emerg.
>> # It is also possible to configure the log level for particular
>> modules, e.g.
>> # "LogLevel info ssl:warn"
>> #
>> LogLevel warn
>>
>> # Include module configuration:
>> IncludeOptional mods-enabled/*.load
>> IncludeOptional mods-enabled/*.conf
>>
>> # Include list of ports to listen on
>> Include ports.conf
>>
>>
>> # Sets the default security model of the Apache2 HTTPD server. It
>> does
>> # not allow access to the root filesystem outside of /usr/share
>> and /var/www.
>> # The former is used by web applications packaged in Debian,
>> # the latter may be used for local directories served by the web
>> server. If
>> # your system is serving content from a sub-directory in /srv you
>> must allow
>> # access here, or in any related virtual host.
>> <Directory />
>> Options FollowSymLinks
>> AllowOverride None
>> Require all denied
>> </Directory>
>>
>> <Directory /usr/share>
>> AllowOverride None
>> Require all granted
>> </Directory>
>>
>> <Directory /home/$HOME/Sitios>
>> Options Indexes FollowSymLinks
>> AllowOverride None
>> Require all granted
>> </Directory>
>>
>> #<Directory /srv/>
>> # Options Indexes FollowSymLinks
>> # AllowOverride None
>> # Require all granted
>> #</Directory>
>>
>>
>>
>>
>> # AccessFileName: The name of the file to look for in each directory
>> # for additional configuration directives. See also the
>> AllowOverride
>> # directive.
>> #
>> AccessFileName .htaccess
>>
>> #
>> # The following lines prevent .htaccess and .htpasswd files from
>> being
>> # viewed by Web clients.
>> #
>> <FilesMatch "^\.ht">
>> Require all denied
>> </FilesMatch>
>>
>>
>> #
>> # The following directives define some format nicknames for use with
>> # a CustomLog directive.
>> #
>> # These deviate from the Common Log Format definitions in that
>> they use %O
>> # (the actual bytes sent including headers) instead of %b (the
>> size of the
>> # requested file), because the latter makes it impossible to
>> detect partial
>> # requests.
>> #
>> # Note that the use of %{X-Forwarded-For}i instead of %h is not
>> recommended.
>> # Use mod_remoteip instead.
>> #
>> LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
>> \"%{User-Agent}i\"" vhost_combined
>> LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
>> \"%{User-Agent}i\"" combined
>> LogFormat "%h %l %u %t \"%r\" %>s %O" common
>> LogFormat "%{Referer}i -> %U" referer
>> LogFormat "%{User-agent}i" agent
>>
>> # Include of directories ignores editors' and dpkg's backup files,
>> # see README.Debian for details.
>>
>> # Include generic snippets of statements
>> IncludeOptional conf-enabled/*.conf
>>
>> # Include the virtual host configurations:
>> IncludeOptional sites-enabled/*.conf
>>
>> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
>>
>>
>> --------------------------
>>
>> del primer:
>>
>> <VirtualHost *:80>
>> # The ServerName directive sets the request scheme, hostname
>> and port that
>> # the server uses to identify itself. This is used when creating
>> # redirection URLs. In the context of virtual hosts, the
>> ServerName
>> # specifies what hostname must appear in the request's Host:
>> header to
>> # match this virtual host. For the default virtual host (this
>> file) this
>> # value is not decisive as it is used as a last resort host
>> regardless.
>> # However, you must set it for any further virtual host
>> explicitly.
>> #ServerName www.example.com <http://www.example.com>
>>
>> ServerAdmin webmaster a localhost
>> DocumentRoot /home/$HOME/Sitios
>>
>> # Available loglevels: trace8, ..., trace1, debug, info,
>> notice, warn,
>> # error, crit, alert, emerg.
>> # It is also possible to configure the loglevel for particular
>> # modules, e.g.
>> #LogLevel info ssl:warn
>>
>> ErrorLog ${APACHE_LOG_DIR}/error.log
>> CustomLog ${APACHE_LOG_DIR}/access.log combined
>>
>> # For most configuration files from conf-available/, which are
>> # enabled or disabled at a global level, it is possible to
>> # include a line for only one particular virtual host. For
>> example the
>> # following line enables the CGI configuration for this host only
>> # after it has been globally disabled with "a2disconf".
>> #Include conf-available/serve-cgi-bin.conf
>> </VirtualHost>
>>
>> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
>>
>> ----------------------------
>>
>> Ja diràs.
>>
>>
>> --
>> Salutacions,
>>
>> Joan Carles
>> Usuari GNU/Linux #324197#
>> http://counter.li.org/
>>
> Bones!
>
> Amb l'eina aquella em referia que copiessis el contingut dels
> fitxers allà, així no hi ha tanta parrafada a les llistes.
>
> Doncs per evitar problemes fem un canvi fàcil. Als dos fitxers
> canvia la "/home/$HOME/Sitios" per "/var/www/html". Després,
> reinicia l'Apache fent "sudo service apache2 restart". Un cop fet,
> torna a provar d'accedir a http://127.0.0.1/info.php
>
>
> Ja ens diràs!
>
>
> --
> Aniol Martí gpg C6F0514F
> http://www.aniolmarti.cat <https://www.aniolmarti.cat>
>
> Linux Registered User #614499
> __________________________________________
> P Abans d'imprimir aquest correu pensa bé si és necessari fer-ho.
>
> --
> Ubuntu-cat mailing list
> Ubuntu-cat a lists.ubuntu.com <mailto:Ubuntu-cat a lists.ubuntu.com>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-cat
> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-cat>
>
>
>
>
> --
> Joan Carles
> Usuari GNU/Linux #324197
>
>
Bones!
Doncs ara només cal que posis els fitxers del curs a /var/www/html.
Hauria de funcionar.
Salut!
--
Aniol Martí gpg C6F0514F
http://www.aniolmarti.cat <https://www.aniolmarti.cat>
Linux Registered User #614499
__________________________________________
P Abans d'imprimir aquest correu pensa bé si és necessari fer-ho.
-------------- part següent --------------
Un document HTML ha estat eliminat...
URL: <https://lists.ubuntu.com/archives/ubuntu-cat/attachments/20170603/76d02ce5/attachment-0001.html>
Més informació sobre la llista de correu Ubuntu-cat