Blogs

August 11, 2010

SSH login using config

Posted by: {authorName}

My last blog, which discussed how you can login via ssh without entering a password, makes your life easier as you don't have to remember each and every password on every single computer. Not to mention, it ensures greater security as you are accessing the other computer with a key which only you have access to.

This time I'll make ssh login even easier by using a config file.

Instead of typing ssh with different arguments plus the long domain name or IP address and user name, you'll just need to type the command "ssh myserver".

Using our example from my previous blog, open console and run the following command:

[happy@mars ~] vim .ssh/config

Hit 'i' and type in the following:

Host jup
User happy
HostName jupiter

Hit esc button then type ':x" to save.

You can now just type:

[happy@mars ~] ssh jup

SSH command will read your config file and match up 'jup' from the Host in your config and use the User and Hostname to connect to another computer.

This is very useful, especially if you have many servers that you manage and have different usernames and parameters when connecting.

You can set all possible parameters for ssh in the config file instead of typing them one by one.

Examples are Port if the other computer uses a port other than 22, ForwardX11 to display GUI on your local computer, Protocol to force ssh protocol version, Tunnel for tunneling and many others. Type "man ssh_config" in your console to get more in depth information about possible parameters.

Posted by: {authorName}

What to choose? Web-based applications or desktop applications... that is the modern day question for businesses requiring a software solution.

Today, the IT world is swamped with applications and programs, and the internet is everywhere.

Applications, be they standalone desktop applications or web applications, can now interface with web services over standard network protocols, which raises a question: Which type is better?

The answer is there is no clear answer, but we may be approaching one. Read on...

Standalone (or desktop) apps traditionally performed a lot faster and had far more User Interface (UI) capabilities than web apps.

They are natively supported by the underlying operating system, which makes them dependent of the platform they run upon. The industry calls these Rich client apps.

Web apps were traditionally limited to the out-of-the-box UI capabilities, but they could and can be run without any specific requirements from users' operating systems. The industry calls these Thin client apps.

During recent years, a lot of initiatives have surfaces to somehow bridge the capability gap between Rich and Thin client applications. Some have been more successful than others.

There's specifically one that grabs attention - the EXT JavaScript library, which amazingly transforms the web experience into rich experience.

Now... having web apps covering wider and wider IT areas than ever before, will standalone apps become history someday?

I think so...

Posted by: {authorName}

Designers should take this into consideration since we are a highly creative bunch.

While most will probably have a natural eye for what looks good and what doesn't, experience counts most in the world of web design, and learning is a key part of the process en-route to the top. One of the fundamentals of any design – be it web or print – is that it’s the audience that counts, not you.

With that in mind, the one golden rule web designers should remember when carefully crafting their sites is that the second they are launched into cyberspace, they become global.

Anyone from Afghanistan to Zimbabwe can access your page, which means you need to design with the world in mind. Of course, you can’t please everyone. But you can design your website so it’s easy to adapt for other languages, other cultures. By thinking global from the start, the act of localising your website later on becomes a whole lot easier.

Content Is King

Visitors won’t keep coming back to you website for a nice layout and appealing colour scheme alone. The old adage that ‘content is king’ shouldn’t be forgotten amongst all the bells and whistles of an aesthetically pleasing design.

Having a website in English means that around a quarter of the Earth’s population can read your website (and the vast majority of them will have English only as  a second language). So if you’re serious about making international inroads online, the time will probably come when you need to start thinking about converting your content for the global masses.

The world has many different writing systems and scripts, with the likes of Arabic, Greek, Russians and Chinese having quite distinct characters in their respective alphabets. With that mind, the need to use Unicode is imperative if you’re planning to develop your website for other markets.

Unicode is a standard numeric representation of characters that can currently be used for over 90 scripts, and has a repertoire of over 100,000 characters. More specifically, UTF-8 is a variable-length character encoding for Unicode that most programmers will be familiar with.

It is the best option when creating websites for international markets, as it allows you to use characters from countless writing systems. All the standard web design applications facilitate Unicode documents, allowing you to choose the language of your pages and insert appropriate HTML tags within the code.

Colour Mix-up

The colour scheme is a key consideration on any website – in fact it may be one of the first things many web designers think about.

But whilst colour preference is subjective and you can’t please everyone, colours also have cultural significance and it’s perhaps worth thinking about this before settling on a scheme.

For example, black denotes ‘death’ in many western cultures, but not so in eastern cultures, where white is the signifying colour for this. Similarly, red represents ‘danger’ or ‘passion’ in North America and Western Europe, but it can mean ‘purity’ in India. Furthermore, Orange is often used to represent autumn (fall) or Halloween in many regions around the world, but in Northern Ireland, it holds religious connotations for Protestants.

This doesn’t mean you should build a different website for each of your target markets, it just means it pays to be wary of culture and colour.

Graphics & Imagery

This depends on how you would like your website to look. A liberally-clothed lady on a website isn’t all that offensive to western audiences, but it may be a major letdown if you’re targeting more conservative cultures. So you may want to reconsider having such imagery on your website.

The same applies to any potentially divisive graphics, whether it relates to gender, religion, age…anything.

But there is a more practical consideration to be made when thinking about your graphics. Believe it or not, there are still many countries across the world without high-speed internet access, which means fancy Flash animations or other bandwidth-sapping graphics may preclude millions of potential visitors from accessing your pages. To circumvent this, one option is to have a simple HTML version for those on slower connections, and another version for those lucky enough to have superfast web access on tap.

Design & Layout

It’s not the end of the world if you have to develop separate templates to cater for other languages, but it will save you a little hassle if your navigation bar is in the same place across all your websites. A horizontal navigation bar will go some way towards aiding this consistency process.

These are just the very basics of creating a cross-cultural website.

The key point to remember when designing a website is that it is for international audiences and adopting a global mindset from the outset will stand you in good stead.

Happy designing and good luck!