To 'localhost' or not to 'localhost', that is the question ...

Relax and enjoy The Lounge. For all Non-Joomla! topics or ones that don't fit anywhere else. Normal forum rules apply.
Locked
User avatar
sozzled
Joomla! Champion
Joomla! Champion
Posts: 7335
Joined: Sun Jul 05, 2009 3:30 am
Location: Canberra, Australia
Contact:

To 'localhost' or not to 'localhost', that is the question ...

Post by sozzled » Sun May 29, 2016 9:23 pm

Greetings.

This is my 250th post on this forum and to celebrate this milestone in my "career", I thought I "vent" my views on all the I-have-a-problem-with-my-Joomla-on-a-PC-hosted-website topics that I read here on an almost-daily basis. From the outset let me say that the forum here is excellent but, while people help here with all manner of webcraft-related issues, assisting Joomlaphiles with problems that exist in their own private webiverse is an incredibly difficult task to do via a forum.

Everywhere I travel, whether it's in my own local JUG or attending national and international conferences relating to Joomla, our community seems to be divided on the necessities of designing, developing, building and testing websites on a PC-hosted platform and then deploying it on a "real" server. I meet people who are more than passionate about their use of PC-hosted sites; they're almost obsessive-compulsive about it. Whenever I challenge their beliefs—sometimes bordering on fanaticism—about the requirement to undertake their craft in a one-person "world" (usually one solitary personal computer that's not networked to others), I'm met with the resolute response, "This is the only way and you can't tell me otherwise!"

Having worked in this industry for nearly forty years before I retired, and (about eight years ago) I looked into Joomla as a means of maintaining my IT skills, I am aware of the benefits of prototyping—establishing a proof-of-concept—to establish the feasibility of a new idea. Before I built my first Joomla website, I purchased a book on the subject—my Joomla library has grown a lot since that time—and that book recommended installing XAMPP (or some other equivalent software) as a means of helping people get a leg-up to adopt this great CMS software used by millions of people today.

So, yeah, I installed XAMPP, worked through a basic install and then ... I ran into problems. Networking XAMPP across your own private LAN, dealing with the vagaries of Microsoft's firewall, but (Oh, dear Lord!) it was painfully frustrating! Still, I persevered for a few weeks learning as I went about Apache, MySQL and PHP (and wonderful tools like myPhpAdmin), FTP and all the other things we require. I couldn't believe the liberation when I saw my first site appear on a "real" server on the internet. It was almost like someone witnessning their first [two-page] novel going into print!

Undoubtedly there are benefits to using a localhost-served proving ground, perhaps in the event that something goes awry in a real internet-hosted website or if you're trying to migrate a 1.97 TB J! 1.0 site to J! 3.5, but how often do most of us really require this contingency? I suspect that there will be people reading this essay who will say "You're wrong: xAMPx is a "must-have" to build/test/fix Joomla websites."

In eight [plus] years of using Joomla, I don't think I've revisited XAMPP once. I do my development exclusively within an internet-hosted environment; I must have built hundreds of test sites—places to do that proof-of-concept that I mentioned earlier. I can usually get a "real" site up and running within a day or two ... and, if I have problems with it, I can share it with others instanteously over the www. Perhaps I'm the odd-man-in-the-room?

When I browse the topics in this forum, people struggle with questions like "my localhost site works but the copy of it on the internet site doesn't" or "my internet site works but my localhost copy doesn't". Other people then launch themselves into those topics with all kinds of advice—that has nothing to do with Joomla—about how to use "brand-X" software. Really? Is that what we're all about?

As I say, I am aware of some usefulness in a localhost-based testbed but its usefulness is limited. In many cases (unless you can afford the luxury of having total control over the target environment where the site will ultimately be deployed) the localhost environment is quite different to its "real" counterpart: the hardware is [invariably] different, the mix of end-users is different, the software may be different and the "visibility" thing—"can other people see your site"—is totally different. That's why I wonder why we spend as much time as we do helping people work through their difficulties in their own private webiverse. Perhaps I could sum it up this way: if you choose to use "Brand-X" localhost software then, when you have problems with it, go to the people (or a forum) who specialise in it.

Don't get me wrong; the assistance we receive on this forum is fantastic. But I do get frustrated when I read a topic that begins with "My Joomla site has problems" only to discover (25 posts down the track) that the person having the problems can't share their experience with the world because their site doesn't exist beyond a piece of wire extending from their office/bedroom/closet.

Would I use a localhost platform if my site(s) was/were broken beyond all redemption? Perhaps, before I slit my wrists in total desperation, I would ... but a bit of personal blood-letting isn't necessarily a bad thing, sometimes :laugh:

For what it's worth! Cheers!
https://www.kuneze.com/blog
Former member of Kunena project team
If you think I’m wrong then say “I think you're wrong.” If you say “You’re wrong!”, how do you know?

pintobuck
Joomla! Explorer
Joomla! Explorer
Posts: 294
Joined: Tue Mar 06, 2007 9:39 am

Re: To 'localhost' or not to 'localhost', that is the question ...

Post by pintobuck » Sun May 29, 2016 10:31 pm

Happy 250th to sozzled!

User avatar
Gany
Joomla! Ace
Joomla! Ace
Posts: 1169
Joined: Wed Jan 02, 2008 12:38 am

Re: To 'localhost' or not to 'localhost', that is the question ...

Post by Gany » Fri Jul 15, 2016 2:51 am

Mind if I bite?

I work almost exclusively on localhost. All sites I develop, I build on local host. No exceptions. Why?
Because I don't want other people to see my works in progress. That's one reason.
Second, my internet is variable (Amazing Thailand!!!). Sometimes I simply cannot get online, or it's horrendously slow. It always is, when you have to meet a deadline.
Third, I don't do really complicated sites. What I see on localhost is what I will get online.
Fourth, deploying I always do with Akeeba. So I have always a backup stored off line, being the site under development/delivered.

So working on localhost makes it quick, easy, fast, secure and reliable for me.

NickC4555
Joomla! Explorer
Joomla! Explorer
Posts: 457
Joined: Sun Jan 30, 2011 10:09 am
Location: Leicester, UK

Re: To 'localhost' or not to 'localhost', that is the question ...

Post by NickC4555 » Fri Jul 15, 2016 10:19 am

I'm with sozzled. I do all of my development on the hosting account in which the site will be deployed, using a dev subdomain. I set it offline when I'm not working on it and to nofollow. I use this for development, testing and user acceptance, then for testing upgrades once the site has been deployed. That's something else that never ceases to amaze me, why do people deploy upgrades onto a live site, seem surprised when it breaks and often don't have a backup to restore?

I defer to your 40 years in the industry, sozzled. I've only got 35, but probably sufficient to know that if all of your development cycle environments aren't the same, you are unnecessarily introducing risk to a project.


Locked

Return to “The Lounge”