[Pkg-mono-svn-commits] [xsp] 01/01: Reflow readme files (Closes: #773658)

Jo Shields directhex at moszumanska.debian.org
Sun Dec 21 19:14:24 UTC 2014


This is an automated email from the git hooks/post-receive script.

directhex pushed a commit to branch master
in repository xsp.

commit b7170edad11706e0ca601e341d4fd2e0cff5d630
Author: Jo Shields <directhex at apebox.org>
Date:   Sun Dec 21 19:14:07 2014 +0000

    Reflow readme files (Closes: #773658)
---
 debian/mono-xsp2.README.Debian | 37 +++++++++++++++++++++----------------
 debian/mono-xsp4.README.Debian | 37 +++++++++++++++++++++----------------
 2 files changed, 42 insertions(+), 32 deletions(-)

diff --git a/debian/mono-xsp2.README.Debian b/debian/mono-xsp2.README.Debian
index 7e05a37..30b5e56 100644
--- a/debian/mono-xsp2.README.Debian
+++ b/debian/mono-xsp2.README.Debian
@@ -2,19 +2,20 @@ xsp2 for Debian
 --------------
 
 The mono-xsp2 package contains a standalone WebServer to run ASP.NET, developed
-by the Mono hackers, it should run in port 8080 or 8081, the scripts detects which port
-to use.
+by the Mono hackers, it should run in port 8080 or 8081, the scripts detects 
+which port to use.
 
-For example, if you have a mail proxy (or http proxy) using 8080 it should run in 8081.
+For example, if you have a mail proxy (or http proxy) using 8080 it should run
+in 8081.
 
-To change the port, you need to kill your http/mail proxy or move them to other port, and then
-reconfigure xsp2 as root:
+To change the port, you need to kill your http/mail proxy or move them to 
+other port, and then reconfigure xsp2 as root:
 
 # dpkg-reconfigure mono-xsp2
 
-The way that xsp2 manage the /alias (virtual hosts) is like exim does. We have a directory in 
-/etc called xsp2, inside it we have a conf.d directory, were we have directories for each 
-'virtualhost'.
+The way that xsp2 manage the /alias (virtual hosts) is like exim does. We have
+a directory in /etc called xsp2, inside it we have a conf.d directory, were we
+have directories for each 'virtualhost'.
 
 For example, we have monodoc-http, so we have:
 
@@ -26,19 +27,23 @@ Every file is marked by a number, an underscore and the alias name, for example:
 
 /etc/xsp2/conf.d/monodoc/10_monodochttp
 
-If you want to install a new virtualhost to XSP 2, you just need to apt-get it, and if 
-XSP 2 is running it should be started normally, if it's the first virtualhost and you configured
-mono-xsp2 to be started automatically it will start xsp2 by default.
+If you want to install a new virtualhost to XSP 2, you just need to apt-get 
+it, and if XSP 2 is running it should be started normally, if it's the first 
+virtualhost and you configured mono-xsp2 to be started automatically it will 
+start xsp2 by default.
 
-If you configured mono-xsp2 to NOT be started automatically, you should start mono-xsp2 manually:
+If you configured mono-xsp2 to NOT be started automatically, you should start
+mono-xsp2 manually:
 
 /etc/init.d/mono-xsp2 start
 
-Also, if you are installing YOUR OWN VirtualHost, you should use mono-xsp2-admin (and also the manpage)
+Also, if you are installing YOUR OWN VirtualHost, you should use 
+mono-xsp2-admin (and also the manpage)
 
-NOTE: In some cases you can find that /etc/mono-server|/etc/xsp2 exists with other virtualhosts and you  
-don't have mono-server|mono-xsp2 installed, don't get in panic, some virtualhosts installs host configuration 
-files in both server (xsp2 and mono-server).
+NOTE: In some cases you can find that /etc/mono-server|/etc/xsp2 exists with 
+other virtualhosts and you don't have mono-server|mono-xsp2 installed, don't 
+get in panic, some virtualhosts installs host configuration files in both 
+server (xsp2 and mono-server).
 
 Happy Hacking
 
diff --git a/debian/mono-xsp4.README.Debian b/debian/mono-xsp4.README.Debian
index 7802016..2564d0a 100644
--- a/debian/mono-xsp4.README.Debian
+++ b/debian/mono-xsp4.README.Debian
@@ -2,19 +2,20 @@ xsp4 for Debian
 --------------
 
 The mono-xsp4 package contains a standalone WebServer to run ASP.NET, developed
-by the Mono hackers, it should run in port 8080 or 8081, the scripts detects which port
-to use.
+by the Mono hackers, it should run in port 8080 or 8081, the scripts detects 
+which port to use.
 
-For example, if you have a mail proxy (or http proxy) using 8080 it should run in 8081.
+For example, if you have a mail proxy (or http proxy) using 8080 it should run
+in 8081.
 
-To change the port, you need to kill your http/mail proxy or move them to other port, and then
-reconfigure xsp4 as root:
+To change the port, you need to kill your http/mail proxy or move them to 
+other port, and then reconfigure xsp4 as root:
 
 # dpkg-reconfigure mono-xsp4
 
-The way that xsp4 manage the /alias (virtual hosts) is like exim does. We have a directory in 
-/etc called xsp4, inside it we have a conf.d directory, were we have directories for each 
-'virtualhost'.
+The way that xsp4 manage the /alias (virtual hosts) is like exim does. We have
+a directory in /etc called xsp4, inside it we have a conf.d directory, were we
+have directories for each 'virtualhost'.
 
 For example, we have monodoc-http, so we have:
 
@@ -26,19 +27,23 @@ Every file is marked by a number, an underscore and the alias name, for example:
 
 /etc/xsp4/conf.d/monodoc/10_monodochttp
 
-If you want to install a new virtualhost to XSP 4, you just need to apt-get it, and if 
-XSP 4 is running it should be started normally, if it's the first virtualhost and you configured
-mono-xsp4 to be started automatically it will start xsp4 by default.
+If you want to install a new virtualhost to XSP 4, you just need to apt-get 
+it, and if XSP 4 is running it should be started normally, if it's the first 
+virtualhost and you configured mono-xsp4 to be started automatically it will 
+start xsp4 by default.
 
-If you configured mono-xsp4 to NOT be started automatically, you should start mono-xsp4 manually:
+If you configured mono-xsp4 to NOT be started automatically, you should start
+mono-xsp4 manually:
 
 /etc/init.d/mono-xsp4 start
 
-Also, if you are installing YOUR OWN VirtualHost, you should use mono-xsp4-admin (and also the manpage)
+Also, if you are installing YOUR OWN VirtualHost, you should use 
+mono-xsp4-admin (and also the manpage)
 
-NOTE: In some cases you can find that /etc/mono-server|/etc/xsp4 exists with other virtualhosts and you  
-don't have mono-server|mono-xsp4 installed, don't get in panic, some virtualhosts installs host configuration 
-files in both server (xsp4 and mono-server).
+NOTE: In some cases you can find that /etc/mono-server|/etc/xsp4 exists with 
+other virtualhosts and you don't have mono-server|mono-xsp4 installed, don't 
+get in panic, some virtualhosts installs host configuration files in both 
+server (xsp4 and mono-server).
 
 Happy Hacking
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-mono/packages/xsp.git



More information about the Pkg-mono-svn-commits mailing list