<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>www.nitecon.com</title>
	<atom:link href="http://www.nitecon.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nitecon.com</link>
	<description>National I.T. Consultants</description>
	<lastBuildDate>Fri, 11 Mar 2011 05:16:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Varnish HTTP Accelerator</title>
		<link>http://www.nitecon.com/tutorials-articles/develop/linux/varnish-http-accelerator/</link>
		<comments>http://www.nitecon.com/tutorials-articles/develop/linux/varnish-http-accelerator/#comments</comments>
		<pubDate>Fri, 25 Feb 2011 02:44:35 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[http accelerator]]></category>
		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://www.nitecon.com/?p=92</guid>
		<description><![CDATA[For years we've used squid on a lot of projects, and in the past few years we have been installing varnish on clients sites.  More and more customers have also been asking about varnish. Initially in the earlier versions of varnish it was sometimes a bit tricky to explain to customers how to get it compiled and built as most of our customers are windows users with  servers in the Linux environment, however recently varnish has been offering RPM's for easy installation through yum.  I mention only yum here as the debian and other installations are equally as easy, and [...]]]></description>
			<content:encoded><![CDATA[For years we've used squid on a lot of projects, and in the past few years we have been installing varnish on clients sites.  More and more customers have also been asking about varnish.

Initially in the earlier versions of varnish it was sometimes a bit tricky to explain to customers how to get it compiled and built as most of our customers are windows users with  servers in the Linux environment, however recently varnish has been offering RPM's for easy installation through yum.  I mention only yum here as the debian and other installations are equally as easy, and all of the architectures have installation instructions available here: <a title="Varnish Installations" href="http://www.varnish-cache.org/releases/varnish-cache-2.1.5" target="_blank">http://www.varnish-cache.org/releases/varnish-cache-2.1.5</a>

So once you follow the guides available above a lot of people get stuck and are confused about what to do even though there is a really good documentation system available.  So to get you an idea on where to start...  Once varnish has been installed via a yum install varnish, it should create a default.vcl file which lives underneath /etc/varnish/default.vcl

Technically speaking the *ONLY* thing you need to have in this file at this point is:
<pre>backend default {
  .host = "127.0.0.1";
  .port = "8000";
}
</pre>
<p>
Now you'll notice that the port here is listed at 8000, this means that Varnish will ask the apache or other web server that you have for information on port 8000.  This means however that you will need to update your apache server or web server of choice to listen on port 8000.  Once you've completed that, restart your web server to prevent it from taking up the default port 80.

Now the final magic.

Please note in the below example I have a backslash ( \ ) at the end of the first line, this is to create a double line input.
</p>
<pre>
varnishd -f /usr/local/etc/varnish/default.vcl -s malloc,1G \
-T 127.0.0.1:2000 -a 0.0.0.0:8080
</pre>
<p>
What the above line does is as follows: it starts varnish, and tells it that the configuration file it should use is default.vcl (-f /usr/local/etc/varnish/default.vcl)  Now in our case the documentation is wrong, as varnish installed a file for us in /etc/varnish/default.vcl, so this needs to be updated.  The second part to this is -s malloc,1G.  Malloc means that varnish will be caching to memory and use up 1GB of space.  Then there is the -T directive.  This specifies where the administration telnet console will listen.  You can once issuing the command run telnet localhost 2000 and log into varnish to perform several different tasks which at this point is out of our scope.  The final and most confusing attribute to our users is the line that reads -a 0.0.0.0:8080.  This line however complicated is completely unnecessary.  What it does is to tell varnish to listen on address 0.0.0.0 on port 8080.  Due to our web server previously running on port 80 by default we want it to listen on port 80 not 8080, and we want to keep it listening on all interfaces so we can now exclude this entire switch.

So finally on our redhat based system with the default vcl file installed under /etc/varnish/default.vcl, and apache already listening on port 8000 all we need to issue is the following, followed by viewing our website provided by our http accelerator...
</p>
<pre>
 varnishd -f /etc/varnish/default.vcl -s malloc,1G -T 127.0.0.1:2000
</pre>
<p>
One last thing before we let you go, if you are running on a 32bit system for whatever reason, it is not recommended to run varnish witth more than 1GB swap.  Varnish was designed to run on 64bit systems and performs outstanding, however if you have to run on 32bit it will still work, however if you increase this limit too much then you will run into issues with the stack, as well as 32bit memory limits etc.<p>
<p>We hope you enjoyed this very basic but asked for tutorial</p>]]></content:encoded>
			<wfw:commentRss>http://www.nitecon.com/tutorials-articles/develop/linux/varnish-http-accelerator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Server Setup in RH9</title>
		<link>http://www.nitecon.com/tutorials-articles/develop/linux/web-server-setup-in-rh9/</link>
		<comments>http://www.nitecon.com/tutorials-articles/develop/linux/web-server-setup-in-rh9/#comments</comments>
		<pubDate>Sun, 13 Feb 2011 16:05:06 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[dhcp]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[rh9]]></category>
		<category><![CDATA[vsftpd]]></category>

		<guid isPermaLink="false">http://nitecon.com/?p=40</guid>
		<description><![CDATA[Complete Guide to setting up a web server in RedHat Linux 9.

Features : Apache / PHP / MySQL / FTP / SSH / ++]]></description>
			<content:encoded><![CDATA[        <h2>Complete Guide to setting up a web server in RedHat Linux 9.</h2>
        <h3>Features : Apache / PHP / MySQL / FTP / SSH / ++</h3>
        <em>Please note : If you vi anything and the file does not exist or it is  empty you should add the information into it. Several people have  complained that files do not exist but all you need to do is add the  info I have on the site. To be quite honest, even if the files exist and  they have info in you could clean them and just use my info. This is if  you are a first time user and just have to get the site up and running.</em>
        <strong>How to use this guide :</strong>
        <p>This guide walks you through the entire process of getting a webserver  up, however it will only show you how to get a web server up and not to  configure your machine for other things, you have to add those yourself.  As you boot and start the install you will have to keep track of all  the items needed to be installed according to the packages. The  development tools is theoreticaly not needed at all for instalation  however if you decide to upgrade etc you will need the compilers so it's  better to get it done with fast. The guide is seperated into 2 stages  the first of wich packages are needed to install and the second as to  what to type to get everything working. Here is how the second stage  works. Everything typed in <span style="color: red;">RED </span>is actual commands that you give the server. Everything in <span style="color: blue;">Blue </span>is  things you type in vi ( the text exitor ) and also stuff that should be  written in the file specified. Everything in the normal orange color is  information and explinations on why you do certain things.</p>

        <h4>:: = FIRST STAGE = ::</h4>
        Prefered instalation type : Server<br />
        Firewall Configuration :<br />
        Allow Incomming<br />
        <ul>
            <li>WWW</li>
            <li>FTP</li>
            <li>SSH</li>
            <li>Allow DHCP if you need it also</li>
        </ul>
        <h4>Package Selection : [ Package Group Selection ]</h4>
        <p>
            Once you click on Editors / Web Server keep all the items under  detailed enabled unless otherwise specified below. The sections without :  Details means that you can just click the button to enable that section  and it is all you need.
        </p>
        <pre>Editors &gt; Details &gt; Enable only vim-enhanced.</pre>

        <pre>Web Server &gt; Details &gt; Add : mod_auth_mysql / php-mysql</pre>
        <pre>FTP Server</pre>
        <pre>SQL Database Server Details &gt; Add mysql-server</pre>
        <pre>Development Tools</pre>

        <h4>:: = SECOND STAGE = ::</h4>

        <p><em><strong>For everything after this you have to be a super user, so log in as root.</strong></em></p>

        Initialize MySQL first.
        <span style="color: red;">
            <pre>
/usr/bin/mysql_install_db
/etc/rc.d/init.d/mysqld start
cd /usr/bin
mysqladmin -u root password 'password'
            </pre>
        </span>
        <h4>Test MySQL now</h4>

        <pre>/usr/bin/mysql -u root -p</pre><span style="color: red;"></span>enter password when asked</span>
    <pre>show databases;</pre>
    <p>It should show you the databases. [ mysql ] and [ test ]</p>
        <pre>exit</pre>
        <h4>Adding a test to the website now.</h4>
        <pre>cd /var/www/html</pre>
        <pre>vi index.php</pre>
        <p><em>This will bring up a text editor, first press i (to initiate insert mode) then type the following.</em></p>
        <pre>&lt;?php phpinfo(); ?&gt;</pre>

        <p>Now hit <span style="color: red;">ESC</span>, then press <span style="color: red;">:wq</span> this will save the file and exit.
        If you made a mess just hit <span style="color: red;">:qa!</span> to exit</p>

        <pre>/etc/rc.d/init.d/httpd start</pre>
        <p>Now check if your website works. It should show the php info. You are  nearly complete. Now to add the ability to log in and save files via  FTP. SSH will already work, but the majority of people will most likely  want to use FTP.</p>

        <h4>FTP Setup beginning now.</h4>
        <pre>vi /etc/xinetd.d/vsftpd</pre>
        <p>The file should be <img src='http://www.nitecon.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  /etc/xinetd.d/vsftpd ) Nowhere else, some OS's  install a pre-configured version in another directory as an example.</p>
<pre style="color: blue;"> service ftp{
            disable = no
            socket_type = stream
            wait = no
            user = root
            server = /usr/sbin/vsftpd
        }</pre>
        <pre style="color: red;"> vi /etc/vsftpd/vsftpd.conf</pre>
        <p>The file should be <img src='http://www.nitecon.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  /etc/vsftpd/vsftpd.conf )</p>
        <p>The following commands are not commented out or rather # character  before the command for instance #anonymous_enable=NO, it should be  without the # Make sure only these commands are in the file nothing  more.</p>

        <pre style="color: blue;">
            anonymous_enable = NO
            local_enable=YES
            write_enable=YES
            local_umask=022
            dirmessage_enable=YES
            xferlog_enable=YES
            connect_from_port_20=YES
            xferlog_std_format=YES
            pam_service_name=vsftpd
            userlist_enable=YES
            tcp_wrappers=YES
            local_root=/var/www/html
         </pre>

        <h4>The FTP Server is now set up we just have to add a user now to log in.</h4>
        <pre style="color: red;">
            groupadd www
            useradd -g www -d /var/www/html ftpuser
            passwd ftpuser
            chown ftpuser:www /var/www/html
            chmod 7777 /var/www/html
            cp /etc/vsftpd/vsftpd.conf /etc/vsftpd.conf
            /etc/rc.d/init.d/xinetd restart
        </pre>
        <h4>Lets test the FTP now.</h4>

        <pre style="color: red;"> ftp localhost</pre>
        <p>Server will ask you for user and password. Use the ftpuser you just  created with it's password once you are logged in do ls (LS) but lower case.</p>

        <pre style="color: red;"> ls</pre>

        <p>You should see 2 files 1 being index.php that we created earlier, and  other wich is usage that is created by the server when apache was  installed. 
            Please note that since you did all the FTP stuff as root you  might get problems where your FTP won't let you copy files to a certain  folders that you created as root. To fix the error just do 
            </p><pre style="color: red;">chmod 7777</pre><p> as root on the particular folder that has the error.</p>

            <p>You have completed the setup of your web server, for all the other info  you can get via google and the websites of the products youre having  problems with.</p>

            <p>Now open a browser and see your new apache server running. It should  pop up to a page with PHP Version info and a lot of garbage. This means  that your PHP is working together with the apache install. This will  also indicate that if you did everything I said mysql will be ready to  be installed. This whole instalation is for a pretty basic website. All  the other changes to httpd.conf etc you can read about on the web and  ask others to help. This doc wasn't made to show how to make a  production class server but merely to help the struggling new to linux  user to get his / her website up quick and easy.</p>

            <h5>:: Tutorial Created by Nitecon</h5>
        <h5>:: Reason : Many people have hard times getting linux servers up and this tutorial<h5>
        <h5>:: is there so that more people will get into linux instead of having to bother with MS.<h5>

        <h5>:: This tutorial was created after running setups several times to make sure it works.<h5>
        <h5>:: Reinstalled my linux box 11 times and just used those commands and it works <img src='http://www.nitecon.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> <h5>
        <h5>:: I hope this helps and you enjoy it. All I ask is you keep this whole document as is.<h5>
        <h5>:: If someone needs help post the whole thing, please <img src='http://www.nitecon.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> <h5>]]></content:encoded>
			<wfw:commentRss>http://www.nitecon.com/tutorials-articles/develop/linux/web-server-setup-in-rh9/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>C++ MySQL Beginner Tutorial</title>
		<link>http://www.nitecon.com/tutorials-articles/develop/cpp/c-mysql-beginner-tutorial/</link>
		<comments>http://www.nitecon.com/tutorials-articles/develop/cpp/c-mysql-beginner-tutorial/#comments</comments>
		<pubDate>Sun, 13 Feb 2011 15:57:54 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[C++]]></category>

		<guid isPermaLink="false">http://nitecon.com/?p=36</guid>
		<description><![CDATA[This is a working code example of using C++ to interface with MySQL.]]></description>
			<content:encoded><![CDATA[<h2>This is a very old but still useful tutorial on integrating MySQL with C++</h2>
This  is a working code example of using C++ to interface with  MySQL.  I have  tested this code to work several times, please do note  however that it  was originally written in Visual Studio 2005, at this  point in time  Visual Studio 2010, and MySQL 5.1 is out, however with  some minor  tweaking you should be able to receive the same results.   The source  code itself is documented very well and should explain  everything you  need to know on the coding side, however setting up the  project may be a  little different to what you are use to, as you need  to include the  mysql library to your project.

Here is the Visual Studio 2005 example on how to do that.
<h3><strong><em>First things first!</em></strong></h3>
<strong>Open Visual Studio, or whatever C++ Programming IDE that you normally use.</strong>

1. Create a new Empty Console Project/Solution. - That means it has nothing in it no pre defined headers nothing!!
2. Add a new source file to your project. Lets just call it main.cpp
3. This step is VERY IMPORTANT. If you don't follow this you will get unresolved external errors when you try to link your app.
- Open your project settings and go to linker.
- Add additional dependency : <strong>libmysql.lib</strong>
4. Make sure you  have the include files, libraries, and binary files.  If you don't have  it then just download MySQL Server without the  installer, then point the  include paths for your project to the lib  directories for mysql that  you downloaded. I have included mine in  global settings, because I use  it so much and it's too tedious in my  opinion to constantly re-add it  for every project.


<div class="wp-geshi-highlight-wrap5"><div class="wp-geshi-highlight-wrap4"><div class="wp-geshi-highlight-wrap3"><div class="wp-geshi-highlight-wrap2"><div class="wp-geshi-highlight-wrap"><div class="wp-geshi-highlight"><div class="cpp"><pre class="de1"><span class="co2">#include &quot;my_global.h&quot; // Include this file first to avoid problems</span>
<span class="co2">#include &quot;mysql.h&quot; // MySQL Include File</span>
<span class="co2">#define SERVER &quot;localhost&quot;</span>
<span class="co2">#define USER &quot;username&quot;</span>
<span class="co2">#define PASSWORD &quot;password&quot;</span>
<span class="co2">#define DATABASE &quot;databasename&quot;</span>
&nbsp;
<span class="kw4">int</span> main<span class="br0">&#40;</span><span class="br0">&#41;</span>
<span class="br0">&#123;</span>
    MYSQL <span class="sy2">*</span>connect<span class="sy4">;</span> <span class="co1">// Create a pointer to the MySQL instance</span>
    connect<span class="sy1">=</span>mysql_init<span class="br0">&#40;</span><span class="kw2">NULL</span><span class="br0">&#41;</span><span class="sy4">;</span> <span class="co1">// Initialise the instance</span>
    <span class="coMULTI">/* This If is irrelevant and you don't need to show it. I kept it in for Fault Testing.*/</span>
    <span class="kw1">if</span><span class="br0">&#40;</span><span class="sy3">!</span>connect<span class="br0">&#41;</span>    <span class="coMULTI">/* If instance didn't initialize say so and exit with fault.*/</span>
    <span class="br0">&#123;</span>
        <span class="kw3">fprintf</span><span class="br0">&#40;</span><span class="kw2">stderr</span>,<span class="st0">&quot;MySQL Initialization Failed&quot;</span><span class="br0">&#41;</span><span class="sy4">;</span>
        <span class="kw1">return</span> <span class="nu0">1</span><span class="sy4">;</span>
    <span class="br0">&#125;</span>
    <span class="coMULTI">/* Now we will actually connect to the specific database.*/</span>
&nbsp;
    connect<span class="sy1">=</span>mysql_real_connect<span class="br0">&#40;</span>connect,SERVER,USER,PASSWORD,DATABASE,<span class="nu0">0</span>,<span class="kw2">NULL</span>,<span class="nu0">0</span><span class="br0">&#41;</span><span class="sy4">;</span>
    <span class="coMULTI">/* Following if statements are unneeded too, but it's worth it to show on your
    first app, so that if your database is empty or the query didn't return anything it
    will at least let you know that the connection to the mysql server was established. */</span>
&nbsp;
    <span class="kw1">if</span><span class="br0">&#40;</span>connect<span class="br0">&#41;</span><span class="br0">&#123;</span>
        <span class="kw3">printf</span><span class="br0">&#40;</span><span class="st0">&quot;Connection Succeeded<span class="es1">\n</span>&quot;</span><span class="br0">&#41;</span><span class="sy4">;</span>
    <span class="br0">&#125;</span>
    <span class="kw1">else</span><span class="br0">&#123;</span>
        <span class="kw3">printf</span><span class="br0">&#40;</span><span class="st0">&quot;Connection Failed!<span class="es1">\n</span>&quot;</span><span class="br0">&#41;</span><span class="sy4">;</span>
    <span class="br0">&#125;</span>
    MYSQL_RES <span class="sy2">*</span>res_set<span class="sy4">;</span> <span class="coMULTI">/* Create a pointer to recieve the return value.*/</span>
    MYSQL_ROW row<span class="sy4">;</span>  <span class="coMULTI">/* Assign variable for rows. */</span>
    mysql_query<span class="br0">&#40;</span>connect,<span class="st0">&quot;SELECT * FROM TABLE&quot;</span><span class="br0">&#41;</span><span class="sy4">;</span>
    <span class="coMULTI">/* Send a query to the database. */</span>
    <span class="kw4">unsigned</span> <span class="kw4">int</span> i <span class="sy1">=</span> <span class="nu0">0</span><span class="sy4">;</span> <span class="coMULTI">/* Create a counter for the rows */</span>
&nbsp;
    res_set <span class="sy1">=</span> mysql_store_result<span class="br0">&#40;</span>connect<span class="br0">&#41;</span><span class="sy4">;</span> <span class="coMULTI">/* Receive the result and store it in res_set */</span>
&nbsp;
    <span class="kw4">unsigned</span> <span class="kw4">int</span> numrows <span class="sy1">=</span> mysql_num_rows<span class="br0">&#40;</span>res_set<span class="br0">&#41;</span><span class="sy4">;</span> <span class="coMULTI">/* Create the count to print all rows */</span>
&nbsp;
    <span class="coMULTI">/* This while is to print all rows and not just the first row found, */</span>
&nbsp;
    <span class="kw1">while</span> <span class="br0">&#40;</span><span class="br0">&#40;</span>row <span class="sy1">=</span> mysql_fetch_row<span class="br0">&#40;</span>res_set<span class="br0">&#41;</span><span class="br0">&#41;</span> <span class="sy3">!</span><span class="sy1">=</span> <span class="kw2">NULL</span><span class="br0">&#41;</span><span class="br0">&#123;</span>
        <span class="kw3">printf</span><span class="br0">&#40;</span><span class="st0">&quot;%s<span class="es1">\n</span>&quot;</span>,row<span class="br0">&#91;</span>i<span class="br0">&#93;</span> <span class="sy3">!</span><span class="sy1">=</span> <span class="kw2">NULL</span> <span class="sy4">?</span>
        row<span class="br0">&#91;</span>i<span class="br0">&#93;</span> <span class="sy4">:</span> <span class="st0">&quot;NULL&quot;</span><span class="br0">&#41;</span><span class="sy4">;</span> <span class="coMULTI">/* Print the row data */</span>
    <span class="br0">&#125;</span>
    mysql_close<span class="br0">&#40;</span>connect<span class="br0">&#41;</span><span class="sy4">;</span>   <span class="coMULTI">/* Close and shutdown */</span>
    <span class="kw1">return</span> <span class="nu0">0</span><span class="sy4">;</span>
<span class="br0">&#125;</span></pre></div></div></div></div></div></div></div>


]]></content:encoded>
			<wfw:commentRss>http://www.nitecon.com/tutorials-articles/develop/cpp/c-mysql-beginner-tutorial/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LinksAlpha</title>
		<link>http://www.nitecon.com/tutorials-articles/linksalpha/</link>
		<comments>http://www.nitecon.com/tutorials-articles/linksalpha/#comments</comments>
		<pubDate>Sun, 13 Feb 2011 03:30:11 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://nitecon.com/?p=31</guid>
		<description><![CDATA[Post to all the social networks that you visit by just creating a post on your WordPress site!]]></description>
			<content:encoded><![CDATA[As with all things recently I started building a new connector API to connect to multiple networks at the same time.  What is the purpose for this?  Well I have an insane work schedule and social networking is just not within my daily schedule.  So I decided to start building a new program that will hook into my website, the goal would be as soon as I post something on my website it should push the post to all my social networks.

I recently rebuilt my site and decided to just to check and see if there already is a WordPress plug-in that may be able to just what I was starting to build.  To my surprise there already is a site that already does this and it also includes analytics.  Best thing of all is it supports all the networks that I am interested in and also allows 5 networks free.  So how does this work?  First you go to their website and sign up for an account by logging in with your already available accounts... I decided to use my facebook account since it's already one of the networks I want to directly post to.

Here is a quick summary of how you can get this running on WordPress...
<ol>
	<li>Head on over to <a title="LinksAlpha" href="http://www.linksalpha.com" target="_blank">LinksAlpha</a></li>
	<li>Click on the golden start publishing now button</li>
	<li>Select the network you want to use to create your account.</li>
	<li>Once you've been logged in add up to 5 networks to your account, keep in mind that you are only allows 5 networks for free, if you want more you will have to upgrade to a paid subscription.</li>
	<li>At this point in time you will want to add LinksAlpha to your WordPress.</li>
	<li>In the plug-in market search for LinksAlpha, there are a few plug-ins like this but try to find the one by the creators.</li>
	<li>Once installed it will ask you for your API key, go back to Links Alpha, then click on account in the top right of their site, and copy your api key.</li>
	<li>Once you return back to your WordPress site you can now add the API into the plug-in.  Go ahead and set up some of the settings that they have there.</li>
	<li>Once you are happy with your settings return to LinksAlpha and click on Publish in the top then Configure publish in the left menu.  Then at the bottom of the list you will see publish to  all from all websites.  Your posts from WordPress should now be pushed to all the network sites that you have enabled</li>
</ol>
Enjoy!]]></content:encoded>
			<wfw:commentRss>http://www.nitecon.com/tutorials-articles/linksalpha/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Welcome to Nitecon.com</title>
		<link>http://www.nitecon.com/home/welcom/</link>
		<comments>http://www.nitecon.com/home/welcom/#comments</comments>
		<pubDate>Sat, 12 Feb 2011 18:38:02 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Home]]></category>

		<guid isPermaLink="false">http://nitecon.com/?p=1</guid>
		<description><![CDATA[We are still in the transitioning period of moving from our old CMS and datacenter to the newer technology and servers.  During this time some of our services will still be offline to our customers, however this *does not* include actual customer services, only services that customers use to interface with us.  All mail, subversion, hosting, and other networking related services has not been down for more than a 5 minute break during our transition from the old datacenter to the new datacenter.  We appreciate your business and we are definitely excited to share our new technologies with you, our [...]]]></description>
			<content:encoded><![CDATA[We  are still in the transitioning period of moving from our old CMS and  datacenter to the newer technology and servers.  During this time some  of our services will still be offline to our customers, however this  *does not* include actual customer services, only services that  customers use to interface with us.  All mail, subversion, hosting, and  other networking related services has not been down for more than a 5  minute break during our transition from the old datacenter to the new  datacenter.  We appreciate your business and we are definitely excited  to share our new technologies with you, our customers!

We will be  including some new services including an automatic sign up for new  services directly through this website.  This includes new subversion  repositories, shared hosting accounts on our hosting servers, and  automatic payments for services rendered.  We will also be implementing a  couple of other very exciting new features which most of our customers  will be able to benefit from, please note that more detail on this will  be released through our mailing list.

Most of our older tutorial  items will be moved from this particular site, to the liaisonworld  domain which now contains a brand new wiki available to the community.

Thank you,
The Nitecon.com team!]]></content:encoded>
			<wfw:commentRss>http://www.nitecon.com/home/welcom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

