Apis Networks

apnscp Update (hefty backlog edition)

(and by hefty I mean 2 months of unposted changes…)

There is good news to report though – a significant chunk of the changes were minor fixes to resolve regressions that appeared during rapid development of apnscp 2.   Even better – apnscp now has a very limited application lookup tool.

Access the search box either by mouse or as a shortcut junkie with the S access key, type in a few letters, hit enter to confirm the choice, and voila!  Zee app is loaded!

A notable mention, a long-standing bug preventing RubyGems from being upgraded via gem update --system has been patched, but unofficial until today.

Initial release of the inline search feature

Initial release of the inline search feature

ADD: inline search against application titles and taglines (Template)
ADD: proper 404/550 error pages (Template)
ADD: AJAX app method requestor, queries a public method of an application (apnscp)

FIX: rename operation does not work for subsequent subdomains (Subdomains)
FIX: tooltip displays undefined for “Administrative E-Mail” (Dashboard)
FIX: domain is not forgotten if omitted (Login)
FIX: login redirects only to dashboard (Auth UI)
FIX: updating credit card did not commit to database (Change Billing)
FIX: removing subdomain through Delete action fails (List Subdomains)
FIX: create_referral_profile()- missing invoice (Billing)
FIX: changing credit card details always results in failure (Billing)
FIX: bandwidth displays 0% (Template)
FIX: undefined Majordomo variables elicit warning (Majordomo)
FIX: referral profile is not synchronized to slave in time for reading (Billing)
FIX: footer is positioned at bottom
FIX: various IE6 rendering fixes – footer, login, postback “Hide Details” (UI)
FIX: prevent Overview event listener from handling propagated events (Page Template)
FIX: editing a DNS entry in an RR group triggers the edit for the respective position in the first RR group (DNS)
FIX: SPF Wizard does not warn of overwriting records (SPF Wizard)
FIX: add link to display tickets older than 90 days (Tickets)
FIX: browser detection returns spurious results (Page Container)
FIX: function permissions are not exported (SOAP)
FIX: WSDL generation exports uncallable methods (SOAP)
FIX: spurious free space report in storage gauge for users over quota (Template)
FIX: File Tree cancels first directory selection (File Tree)
FIX: methods reported missing within a module signature are not verified (afi)

CHG: parse “REFUSED” nsupdate response (DNS)
CHG: include default rbconfig.rb to allow gem update –system to complete sucessfully.  Make a symlink from /usr/bin/ruby to /usr/local/bin/ruby as well to clear up pathing by specifying a bindir of /usr/local/bin
CHG: referral system provides a one-time lump sum of $5, $10, $20, or $30 (Minimalist -> Super)
CHG: rename get_commissions() to get_referrals() (Billing)
CHG: omit 4 KB directory size from File Manager
CHG: omit parsing of @replies in Twitter feed (Dashboard)
CHG: consolidate frontend/backend functions (Majordomo)
CHG: increase base font size from 13px to 14px (UI)
CHG: remove extra service configuration information, update gauges (Manage Users)
CHG: remove unnecessary billing information from referral profile (Client Referrals)
CHG: display an excerpt of the latest news (Dashboard)
CHG: pulse postback status once for success, twice for warning, and thrice for error (Page Template)
CHG: lessen intensity of green table header for long tables (head1 pseudoclass) (CSS)
CHG: refactor delete() to stat just the parent directory (File)
CHG: improve stat() response for multiple lookups of the same file by statically caching before offloading to APC (File)
CHG: cache template configuration
CHG: fire postback status pulse on postback only (Template)
CHG: update disk space gauges (Quota Tracker)
CHG: use local session cache instead of global cache for tooltips (Tooltip)
CHG: rewrite user behavior logger for applications (Stats Logger)
CHG: promote referral statistics to dashboard (Dashboard)

REM: Legacy Help is irrelevant

(phew! nearly 50 changes)

Comments off

 

Earn more revenue through referrals

Our new referral system is here!  Earn rewards faster just after 90 days.  Whenever a client mentions your e-mail address or domain name during sign-up, we’ll credit $5, $10, $20, or $30 to your account depending on the package.   Better yet, earn 150% after your first referral.  Refer more than 4 clients and each additional referral earns a 200% bonus.

Let’s say you refer 2 friends directly and post a link on your site.  2 friends sign-up immediately and 4 prospective clients stumble upon your site serendipitously, fed up with their current host.  The earning schedule would look like-

Day 1: Minimalist $5
referrals 2 – 3 are multiplied by a bonus of 1.5x
Day 5
: Basic $15
Day 7: Advanced $30
referrals 4-5 receive a 2x bonus
Day 60: Basic $20
Day 90: Basic $20
referrals 6 and beyond receive a 2.5x bonus
Day 195: Minimalist $12.50

Total Earnings: $102.50

To kick off the new system, commission is doubled until the end of the year.  Make at least $10 for referring a friend or placing a link on your site to Apis.  Refer 2 friends?  Earn at least $15.  Refer 6 or more over your lifetime?  Earn no less than $12.50 for each additional person that you recommend.

Linking to Apis is just as simple.  Make a link to http://apisnetworks.com/r?myuname where myuname is the username created within the control panel (Account > Client Referrals).  Referrals made through links are good for 30 days.  Don’t worry about asking to mention your domain – it’s taken care of by the username affiliation.  Append a page location after myuname to redirect to a specific page, e.g. to redirect to the hosting package matrix use http://apisnetworks.com/r?myuname/web_hosting_packages

Enjoy!

- Matt

Comments off

 

Data Center Core Router Failure

Our data center, Gnax, experienced a core router failure when one of its supervisor cards went offline on Monday, October 26th at 5:50 AM ET. The duration of the outage was 6 hours, when servers were brought back online. We, along with many other hosting providers, were affected by this outage disrupting not only our clients, but clients of other businesses hosted through Gnax.

Gnax has not yet disclosed the cause of the excessive duration, but it will be noted in the RFO as more information comes forth. Two routers (core A/B) feed bandwidth to all clients of the data center. Our subnet resides on core A, which experienced the disruption Monday morning.

Monday and Friday are our most important days and likewise, your most important days. Sustaining an outage for any duration longer than a coffee break is debilitating. Although we provide no expressed SLA, clients affected by this outage will receive a one month credit for compensation. Please file a ticket within the control panel requesting credit. For those paying by PayPal, a refund will be issued to the e-mail address on record with the domain. Credit card-backed payments will receive a discount on the next transaction.

- Matt

Comments off