Latest Updates: php RSS

  • How to Create Google Adsense with Open Source Software

    The Truth 11:44 am on January 19, 2009 | 0 Permalink | Reply
    Tags: Ad serving, , , , Google Adsense, , , , , openx, php,

    After being banned from Google Adsense a few times while learning the ropes of SEO (and slipping through a few) I decided I wanted to learn more about 3 things.

    1. Why was I banned?
    2. What detected the violation?
    3. What can I do to get around this?

    So I began learning about CPM, CTR and ROI, investigating other PPC programs like Adbrite, and researching the path a popular piece of original content took on its way to “viral” status. I’ve developed a few theories on the subject however these are not what this article is about. This is about starting your own PPC ad network and taking Google out of the equation. 

    So here are the steps on how to create a mini-Google Adsense with Open Source Software and $100.00 in overhead. 

    What you’ll need:

    • Dedicated Server: 3 months ($89.00) Server Pronto
    • Domain Name 1 year (9.99) Godaddy
    • OpenX 
    • Linux, Apache, PHP5, MYSQL (free) Gentoo Linux

    Steps

    1. Buy your server. I wouldn’t recommend buying more than 3 months to begin with unless you can really afford it. Its easy to extend your contract and if you’ve got backups of your site you can ditch your company for a cheaper one anytime you want. The great thing about Linux based hosts is that you have total control over your system, security, and backups. Moving to a new host is as easy as dumping the database and SCP’ing the files. Server Pronto has a great deal for 3 months with a price tag of $89.00. They also support Linux.
    2. Head over to your favorite domain registrar and grab a catchy name. GoDaddy always has specials for 9-14 dollars for the first year. Try and get something that will appeal to your audience of advertisers. A silly Web 2.0 name like SpanDingle.com is not going to work. I didn’t Google that so SpanDingle.com might be available…but anyways…
    3. Get OpenX AdServer. This is the real meat and potatoes of the tutorial. OpenX is an ad server that allows you to specify campaign profiles and assign them to your different sales managers and agents. Your stats are fully tracked and emailed to the right person on a weekly basis. You can set your own cost per impression and determine a fair CPM/CPC rate for your advertisers. Pair the stats with a Google Analytics account and you’ll have everything you need to invoice your clients at the end of the month. 
    4. OpenX is designed to run in an LAMP environment. There is no overhead for this open source software. The only overhead is the learning curve, which varies from distribution to distribution. I use Gentoo for all of my servers for its security, tight documentation and active developer base. Linux, if configured correctly, will get you much more life out of your server’s hardware, and cut costs on monthly overhead. 
    Now for the hard part: Selling the ads. You’re going to need to do 2 things. First, you need places to show your ads. Contact medium-traffic websites within your market and ask them if they’d like free advertising on the web. Tell them you’re starting a “Ads by Google” system (people will recognize this more than ‘Adsense’) and you’re GIVING away impressions to anyone who wishes to show a few text links on their own site. You can assure them that their direct competition will not be advertising on their site by sectioning your campaigns into inter-market niches. For example: if you’re targeting the Gardening industry, sell your soil and mulch campaigns to the hardware stores, and the hardware stores to the materials suppliers, and so on. Every advertiser is a potential publisher and vice versa. 
    Well, thats all for now. Has anyone else tried this before? Am I crazy?

     

    Related articles
    Reblog this post [with Zemanta]
     

  • XAAMP for Windows Mac and Linux

    The Truth 3:37 am on December 2, 2008 | 0 Permalink | Reply
    Tags: , Apache HTTP Server, , , php, , , XAMPP

    This chart shows several of the SQL language e...

    Image via Wikipedia

    This package looks like it’s maturing quite nicely. Check out XAMPP, available for Windows, Mac, and Linux<3.

    Many people know from their own experience that it’s not easy to install an Apache web server and it gets harder if you want to add MySQL, PHP and Perl.

    XAMPP is an easy to install Apache distribution containing MySQL, PHP and Perl. XAMPP is really very easy to install and to use - just download, extract and start.

    Related articles by Zemanta
    Reblog this post [with Zemanta]
     

  • Creating a PHP5 Framework

    The Truth 6:39 pm on August 30, 2008 | 0 Permalink | Reply
    Tags: , Design pattern, , php, Singleton pattern, Web application, ,

    202px-PHP-logo.svg Creating a PHP5 FrameworkImage via Wikipedia

    With websites becoming more and more dynamic and interactive, developers often look to frameworks to help build websites and web apps rapidly. While there are a number of great frameworks available, a custom framework gives you the ability to easily customize the framework as you need, and to build with it even quicker - as you would already know the ins and outs of it before working with it. In this series of tutorials, we are going to build our very own PHP5 Development Framework! Let’s start with planning our framework and put the basic structure into place.

    Step 1: This Series

    In this series, we will create our own PHP5 Framework from scratch. The Framework will include basic content management features, and we will use it to build a web-based directory for a small organization.

    Hopefully, as we go along, you will improve, build up and optimize this framework to suite your needs better, however in these tutorials we are aiming to get a simple framework up and running and powering a website.

    one Creating a PHP5 Framework

    Over the next few weeks, during these tutorials we will cover:

    • Creating authentication handler, database abstraction layer and template manager
    • Bringing these objects together
    • Using the framework to manage content, and power our site
    • Creating a fantastic front end design.
    • Designing for the login process by storyboarding
    • How the Framework can be extended and expanded

    Step 2: Design Patterns and their use within our Framework

    When creating any large computer-based system, be it a desktop application, a distributed network system, or a web application there will always be architectural challenges associated with its implementation.

    Design patterns address some of these common problems, and we will make use of a number of design patterns as we create our Framework, to ensure that we have a quality, flexible, robust and usable framework, fit for any purpose! In particular, in this tutorial we are going to look at the Singleton pattern and the Registry pattern.

    Step 3: Files and Folders

    The first thing to get started creating our Framework, is to create a suitable file structure, such that everything has its place. As well as the files powering the framework, we also need to make provisions for files relating to the website we are going to create with our framework. Most websites and web applications have:

    • Some commonly used functions / objects.
    • Business logic.
    • A design

    This gives us a great starting point, files relating to each of those three categories should be grouped together in their own section. Take a look at the directory structure below, we will then discuss the reasons for the structure.

    three Creating a PHP5 Framework

    Note that the .settings folder and the .project file were created by the IDE I use, and don’t need to be present in your application

    Core functions and objects, such as database access, authentication, template handling, email sending objects, email parsing objects, should be stored within a folder called objects, within the PCARegistry folder. This allows us to separate the logic from the Registry (which we will look at shortly) from the objects stored within the Registry.

    Next, we need somewhere to store our business logic which is the files we will create which make use of our framework. We should keep these files in a folder called controllers. Each major function that our website or web application does (e.g. business directory listing, providing and managing content, providing an image gallery, etc) would be a separate controller, stored within its own folder within the controllers folder. We are not going to use these in this tutorial, but it is important to have our directory structure in place, so we know how it will work.

    The sites design and templates, should be stored within the skins folder. Since we may want different designs (either so users of the application/website we create with our framework can chose from a number of designs, or to change the design depending on season or special event), each skin will be contained within its own folder.

    Read The Rest of this Great Tutorial at Nettus

    Related articles by Zemanta
    Reblog this post [with Zemanta]
     

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel

Powered by Yahoo! Answers