Gisteren vond de kijkmiddag plaats voor alle toekomstige bewoners van de Toekomst fase 2. Nadat we eerst even lekker zijn gaan lunchen bij het Grand Café konden we ons om half 3 melden bij de ingang van het flat. Hier dus een virtuele rondleiding in ons appartement, op alle foto’s kunnen geklikt worden voor een vergroting.

Ingang van het flat met onze brievenbus

Omdat de lift nog niet operationeel was konden we 10 trappen op naar de vijfde verdieping.

Trappenhuis

Aangekomen op de vijfde verdieping kunnen we via de galerij richting onze voordeur. We hebben het tweede huis op de verdieping.

Galerij

De eerste keer naar binnen !

Naar binnen!

Wanneer we bij binnenkomst helemaal doorlopen komen we in de woonkamer uit:

Woonkamer

Het balkon is vanuit de woonkamer bereikbaar middels een schuifpui en vanuit de slaapkamer via een deur.

Balkon

Woonkamer vanaf de andere kant

Samen

Vanuit de woonkamer en vanuit de gang kunnen we de keuken in:

Keuken

De slaapkamer zit naast de woonkamer:

Slaapkamer

De studeerkamer zit aan de kant van de gallerij:

Studeerkamer

Joyce voor de meterkast

Toilet

Vanaf de 5e verdieping heb je redelijk wat uitzicht vanuit de woonkamer. Zo kunnen we de ‘Hoge Witte’ gelegen in hartje Vlaardingen zien:

Uitzicht vanuit de woonkamer

Geen foto’s van de badkamer, er was nog geen verlichting Het leuke van zo’n kijkmiddag is dat ook we de mensen hebben kunnen zien die ook in het flat komen wonen.

Nu nog even wachten april! Waarschijnlijk krijgen we voor die tijd nog een kijkdag.

1. Go to the Apache Friends and download Xampp for windows from here http://www.apachefriends.org/en/xampp-windows.html download it.

2.  Double click xampp-control.exe and start the Apache and Mysql services.

3. Open your browser and go to this address: http://localhost/. From the menu on the left column, choose your preferred language.

4. Now that the interface displays a language that you can understand, click on phpMyAdmin (on the left column once again)

5. Enter “wordpress” (without quotes) in the “Create New Database” Field, and select utf8_unicode_ci in the drop down box in the next field (as shown in the picture below). Click on Create. The Xampp setup is now complete.

6.  Download WordPress and unzip it under c:\xampp\htdocs.

7. You should now have a wordpress folder under c:\xampp\htdocs. Browse to the folder, and you will see a file named wp-config-sample.php. Open it in your favourite text editor and replace the default values by the ones you see under this paragraph. Save the file as wp-config.php (under the same folder).

// ** MySQL settings ** //
define(‘DB_NAME’, ‘wordpress’); // The name of the database
define(‘DB_USER’, ‘root’); // Your MySQL username
define(‘DB_PASSWORD’, ”); // …and password (needs to be empty, just for local install)
define(‘DB_HOST’, ‘localhost’); // 99% chance you won’t need to change this value

After doing this changing  savethe file it.

8. Now,  copy WordPress files to Xampp htdocs root folder, open Internet Explorer, or Firefox, and type the exact path URL to where you copy the WordPress files:

http://localhost/wordpress/wp-admin/install.php

Now click on create a configuration file and proceed.

9. Then, on Let’s go

10. On the following screen, type the database name, username, and password. these are the same credentials we created at the beginning.

database name : wordpress

username : root

password:

password should be empty.

11. Click on Submit. If everything is all right, you should get a message telling you are all set to go:

12. Click on Run the install. Next, you will be asked to enter the name of the blog, and e-mail address.

13. After entering the name of your blog, and e-mail address, you should get your username and password to login to your blog admin panel.

14. Copy those credentials to a notepad page, and click on Log in. From there on, your wordpress test site should be up and running.

15. Use the URL http://localhost/wordpress/wp-admin to login to your blog admin panel.

That was easy, wasn’t it?

I’d like to share my workflow, as it has proven efficient for me. I’m running two ’servers’ locally (!). Hang on, I said it was efficient, even though it surely doesn’t sound like it. The workflow should gain teams of any sizes, in my opinion.

I am developing an app it in rails and it also exposes some RESTful web services,  with_feed :through => :third_party. The third parties aren’t necessarily third parties, as we develop these too, but they are external apps collecting and sending data to my app. Part 2 will cover the creation of dummy clients that send randomish data to the core app.

OK, I will share the script and procedure I did to have a running server locally alongside developing my app. I wanted to have the server running locally, being able to receive request to the web server, testing the app manually, fast. To distinguish this local server (say localhost:3001) from your development server (sat localhost:3000), I decided to name it experimental, for simplicity. This is my workflow cycle

1. developing, creating migrations and so on, running mongrel at localhost:3000
2. git commit -am “I commit small changes, often!”
3. back_to step 2 if more_should_be_done
4. relaunch experimental server at localhost:3001, continuously receiving WS requests.

git pull and git push is performed frequently as well, but not as frequent as the above.

So, why would you I want that last step?

• It’s a great way of proving your migration scripts work. That server is supposed to be running all the time, containing more data, and old data.
• proving that your code works (which you of course also have extensive unit and integration tests for)
• prove that the clients still submit data through the web services as expected. (more of this in Part 2)
• better break experimental than staging?

What? isn’t this just the same as Cap and a staging server?

Well, not exactly, but yes, very similar. Experimental is something in between of staging(pretty stable) and the development server(unstable). If stableish was a word, then that’s what it is;) Differences better explained:

• The staging server is shared, experimental is not.
• The round trip is shorter. ‘git commit’ is sufficient. For staging I bet you have agreements to perform ‘git push’  to share code before deploying to the server (or ‘cap uses git pull’)
• Local development server is too unstable to have other apps sending data to it every hour. So you wouldn’t normally do that, you’d set it up for staging.
• Breaking staging messes up for more people than yourself. Also, you checked the code in with git push, probably.
• With the local experimental server you may mess around as you see fit, without becoming an impediment in your team.

Script deploy_to_local

To do this locally, you can’t use Capistrano (if you can, please educate me), so I created my own super-simple script to automate it. Say I have this file structure :

dev/myrailsapp/ (with .git, app/, etc.)
dev/temp/myrailsapptest/ (.git, app/, etc.)

where myrailsapptest is a duplicate of myrailsapp, except of the standard configuration files, like database.yml and such. These must be ignored by git, in .gitignore, or they will be overwritten.

#script deploy_to_local
rm -rf ~/dev/temp/myrailsapptest/.git
cp -rf .git ~/dev/temp/myrailsapptest/
pushd ~/dev/temp/myrailsapptest/
echo "git checkout ."
git checkout .
echo "rake db:migrate"
rake db:migrate
echo "Note: remember that the server must have been started with 'mongrel_rails start -d --port 3001' (daemon mode)"
mongrel_rails restart
echo "Restarting backgroundrb workers"
script/backgroundrb restart -e development
popd

Pretty simple, right? You can’t do this with svn, though, as it infects every directory you’ve got. Git stores everything in .git/ and a ‘git checkout .’ will automatically replace, add or delete everything as long as they’re not listed in .gitignore.

I’m using backgroundrb for scheduled tasks, if you’re not, remove backgroundrb restart from the script.

Notice that ‘git commit’ must be done first. This is why I consider the experimental server more stable than the development server. You may argue that it could be done without performing git commit first, but I guess nobody will. To me, committing is a small, important task that should be done often.

First step

Backtracking a little, the first thing you have to do, a one-time effort, is

• copy your whole rails app project directory to ../temp/railsapptest so that you also get the ignored files.
• Or, copy the .git and fix the ignored files manually. Whatever suits you.

Note (as in the script): to be able to perform a mongrel restart, you have to start it in daemon mode.

mongrel_rails start -d --port 3001

I’m saying this, because it’s poorly explained and I struggled for hours with it stating “PID file log/mongrel.pid does not exist.” when trying restart after a standard server start (script/server).

Last note. Exposing the local experimental app over the internet.

You don’t need any other server than your own mac/linux/win to show off your app to other people through the internet. Why deploy to staging before showing off your changes?

I did this at home, logged into my router, set up port forwarding of port 3001 to my computer (I’ve set up my router to recognize my mac and always  give it the same local ip address)

Then, given the IP address of the router is abc.def.ghi.jkl I would call or email whomever and say, check out the app at abc.def.ghi.jkl:3000 and tell me what you think! This guy would see exactly the same as I would on localhost:3001, which is cool. I’m sorry if you’re a corporate guy with routines, rules or other a bureaucrazy environments, hehe. Well, of course you can’t go port forwarding to thousands of people, this one is just a snack for those of us wanting to show of stuff we make at home in our spare time;)

Hope somebody find this useful! In the next post I will talk about the dummy client apps I wrote to feed my app, using RESTful web services. Maybe something about the backgroundrb jobs I’m using, if I feel like it. Should I?

Anda pernah merasa terganggu oleh facebook, friendster, youtube, atau situs apa saja karena teman kerja selalu memakai komputer anda untuk online sehingga pekerjaan anda harus tertunda?? hehe… blok saja situsnya dari komputer anda !! hal ini bisa anda lakukan dengan mengutak utik file hosts. Dengan begitu hanya anda yang bisa mengakses situs tersebut… tertarik?

Sebaiknya pahami dulu pengertian tentang hosts file tersebut sebelum ide iseng anda dijalankan..

Hosts adalah file komputer yang digunakan oleh sistem operasi untuk memetakan nama host ke alamat IP yang gunanya untuk  menemukan node pada sebuah jaringan komputer. Komputer Anda menggunakan file hosts untuk membantu mempercepat resolusi nama domain di Internet untuk menyelesaikan alamat IP  sebuah website, kemudian memeriksa file hosts untuk melihat apakah sudah ada entri di sana. Jika ada, tidak perlu pergi ke server DNS dan menyelesaikan alamat.     Astaga… ribet sekali bahasa saya ya?…   hehehe   abaikan saja,  sebab  topik  yang kita bahas disini adalah cara memblok sebuah situs agar tidak bisa diakses dari komputer anda.

Secara teori, perubahan file hosts bertujuan membantu mempercepat browsing web, tetapi Anda juga dapat memanipulasi file hosts untuk memblokir situs dengan menunjuk nama domain ke alamat IP yang berbeda,  seperti  127.0.0.1  yang merupakan alamat IP mesin lokal Anda.

Heh?..langsung caranya aja?… waduh tidak sabaran sekali..

ok, this is how to :

1. Buka C:\Windows\Sytem32\Drivers\Etc\hosts dan buka / klik kanan -> openwith, pilih   notepad

2. Maka akan tampil pada notepad anda seperti ini:

==================================================
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost

==================================================

3. lalu tambahkan situs-situs yang anda ingin blokir,  ketik pada bagian paling dibawah tulisan 127.0.0.1 lokalhost, (yang berwarna hijau) disini saya akan memblokir beberapa situs seperti facebook, youtube dan friendster : (cara penulisan: 127.0.0.1 (tekan tab) facebook.com, sehingga pada notepad akan tertulis seperti ini :

==================================================
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
127.0.0.1 facebook.com
127.0.0.1 www.facebook.com
127.0.0.1 youtube.com
127.0.0.1 www.youtube.com
127.0.0.1 friendster.com
127.0.0.1 www.friendster.com
==================================================

4. lalu klik file -> safe atau tekan saja Ctrl + S. kalau sudah tutup notepad anda, dan coba browsing ke situs http://www.facebook.com/ …

… sampai disini anda sudah berhasil menjalankan ide iseng anda ? 

Bila anda ingin mengakses situs yang telah anda blok tadi, buka host file dan hapus alamat situs yang anda blok dan jangan lupa untuk safe sebelum anda menutup notepad.

Lokasi host file pada OS :

Mengapa IP nya harus 127.0.0.1 ?
karena ini adalah IP adress dari localhost,  cantumkan saja IP dari localhost ini sehingga alamat situs langsung di redirect ke IP yang sudah kita tentukan sendiri, yang artinya koneksi ke situs dimaksud akan gagal.

Sekarang tujuan utama penulisan topik ini :
Tujuan penulisan adalah untuk mengenalkan kita tentang pentingnya file host tersebut untuk tujuan yang baik, mengapa?.. karena dengan pemahaman diatas anda dapat memblokir berbagai situs misalnya situs porno ( berani? ), atau situs yang mengandung malware karena seperti kita ketahui bagaimana kemampuan spyware yang menempel pada PC Anda saat menjelajah situs web atau download file. Tehnik pengubahan file hosts ini juga dimanfaatkan oleh spyware dengan tujuan mendownload update virus dan memanggil varian worm lain ke komputer anda.

Sebagai contoh, misalnya situs “www.porno.com” adalah situs malware yang dikenal dan memiliki alamat ip 68.23.5.x. maka kita bisa merubah file host dengan menuliskan bahwa 127.0.0.1 adalah alamat IP “www.porno.com”. Jadi, ketika anda mengetik nama situs “www.porno.com” ke browser web anda, tak ada yang terjadi karena browser Anda menganggap alamat IP untuk “www.porno.com” adalah PC Anda.

Ada beberapa cara mengubah file hosts tersebut dengan menggunakan program seperti Spybot Search and Destroy, yang memiliki fitur Imunisasi yang memodifikasi file host anda. Atau Anda dapat melakukannya secara manual dengan mendapatkan host file dari situs yang sering memperbaruinya. Salah satu situs adalah  SomeoneWhoCares.org.

…. Rasanya sudah cukup ya?.. anda pasti sudah dapat dengan mudah melakukan pengaturan pada file hosts anda dan yang terpenting anda sudah dapat memahami mengapa topik ini ditulis..

Begitu saja …  maafkan ke-sok tahuan saya dan satu hal lagi, penulisan topik ini tidak bermaksud mendiskreditkan situs tertentu, semata-mata  hanya ingin berbagi, terimakasih sudah mencoba mengerti..
Salam ….

Siguiendo el post de Alo en su blog, se me ocurrió hacer exactamente lo mismo (soy poco original, y qué?) con los únicos algunos strips que llevo hechos con Stripgenerator.com, un servicio donde puedes hacer pseudohistorietas cortas sobre lo que se te ocurra con figuras prediseñadas al más puro estilo de Power Point (?). Bien, sin más, les presento mis creaciones:

El primero, un caso de la vida real que vivio un servidor en Al-Sheesha (o como se escriba), en compañia de Champi, Lealol y otros. Todo iba bien hasta que a champi se le ocurrió pedir una piña colada.

La siguiente es una anécdota que se repite cada vez que voy a comer tacos con mis amigos. Por alguna razón, cuando hay que pagar la cuenta, falta dinero. Y al poner más y volver a contar, sobra y por mucho, and so on…

El último es mi representación gráfica de algo de muchas cosas graciosas que viví y escuché en mi antiguo trabajo, cuando me desempeñaba como asesor de soporte técnico para el servicio de internet de Infinitum, de esos a los que le llamas cuando te quedas sin internet.

Por ahora son todos, luego haré otros y los estaré publicando por aquí.

Arrivederci amigos mios

Pues eso, me mude de mi antiguo blog (thefreakshow.uuuq.com) porque el servidor gratuito en el que lo monté era una porquería inestable y tenía otros pedos técnicos. Como no tenía dinero para el dominio, probe en blogger y wordpress para montar mi blog. La verdad es que ninguno me convence, pero ya había usado blogger antes y aunque es menos limitado que este puto servicio de wordpress, no tiene funciones básicas como las páginas y otras cosas. Así que heme aquí. Como ya es algo estable, por fin estaré pasándome por acá como debe ser.

Así que bueno, reinaugurando mi blog personal o algo así, visitenme ptas >:0.

Arrivederci.

Este é um tutorial simples que ensina a instalar o Drupal no localhost. No geral não existem grandes problemas na instalação do Drupal, mas o tutorial vale pra quem quer começar a usar este CMS.

Ficha técnica:

Servidor local: Windows Vista;

Versão do Wamp: Wamp5 1.7.3;

Versão do Drupal: Drupal 6.14;

1 – Download

Baixe o arquivo compactado do Drupal em drupal.org.

página inicial do Drupal

2 – Mova o arquivo

Depois de baixado, abra o arquivo compactado (pode ser com o Winrar) e cole na pasta www dentro do diretório de instalação do Wamp. Por padrão instalado no “C:“

wamp

3 – Instalação

Agora é só iniciar os serviços do Wamp e abrir o Localhost em seu Navegador (http://localhost/), para enfim partir para a instalação.

Neste momento será aberta a página inicial do Wamp, clique no link PHPmyadmin – em Tools. Nesta página criaremos o banco de dados que será usado pelo Drupal.

Coloque como nome do Banco de Dados: Teste, conforme a figura abaixo:

banco de dados mysql

O sistema informará que o banco foi criado com sucesso. Depois disto retorne para a página inicial do Localhost.

No Localhost clique em drupal-6.14, a tela aberta deve ser como a da figura:

selecione o idioma

Clique no link Install Drupal in English.

Neste momento o Drupal exibirá uma tela com um erro no arquivo /sites/default/default.settings.php. Para prosseguir com a instalação, abra a pasta: C:/wamp/www/sites/default/ e copie o arquivo default.settings e cole na mesma pasta, renomeie o arquivo para settings, assim ficarão dois arquivos.

Volte para a instalção do Drupal e clique no link Try again.

Agora é só colocar as informações do Banco de Dados e continuar a instalação, como na imagem:

banco de dados no drupal

Clique em Save e continue para prosseguir.

Aguarde um momento até que o drupal seja instalado e depois é só informar os dados do site, como Nome do site, Nome do administrador, e-mail de contato e senha. Depois de inserir os dados correspondentes ao site clique no botão Save e continue.

Então uma tela informando que seu site foi instalado será exibida, clique em your new site para visitar seu novo site Drupal!

Caso haja alguma dúvida é só comentar.

Het is alweer een tijd geleden dat ik deze blog bijgewerkt heb, en aangezien er genoeg gebeurd is de afgelopen tijd ben ik weer van plan om dit op te pakken.

Afgelopen juli hebben Joyce en ik een appartement gekocht in de Sperwerlaan in Vlaardingen.  Het gaat hier om het nieuwbouwproject de Toekomst.

De Toekomst

In dit project worden sociale huurwoningen uit 1964 gemoderniseerd zodat deze weer voldoen aan de normen van deze tijd. De indelingen van de appartementen zullen worden gewijzigd en er wordt een verdieping opgebouwd, de verdieping waar wij ook zullen gaan wonen.

Het flatgebouw in 1964

We hebben gekozen voor een 3-kamer appartement met een oppervlakte van 81 m2. Het terras van 7,5 m2 is bereikbaar via de schuifpui vanuit de woonkamer en vanuit de slaapkamer:

Indeling appartementen 5e woonlaag

Op 13 juli (op mijn verjaardag ) was het voorlopig koopcontract getekend en hadden we 6 weken de tijd om de financiering rond te krijgen. Na het regelen van mijn werkgeversverklaring en de  hypotheek konden we na onze vakantie in Italië op 9 september de hypotheekakte tekenen bij de notaris.

Uiteraard houden we foto’s bij van de vorderingen bouw en zal ik deze op mijn blog publiceren. Als eerste foto met de stand van zaken voor de vakantie, 5 juli, ons luchtkasteel:

Ons luchtkasteel 05-07-2009

Toen we het koopcontract tekende was de verwachtte oplevering juni 2010. Vorige week hebben we echter bericht gekregen dat de oplevering is vervroegd naar medio april 2010.

24 november krijgen we een rondleiding op het bouwterrein en kunnen we ons huis gaan bezichtigen.

Volgende keer wat meer foto’s van de vorderingen .

This is a tool I whipped up for use in the Microsoft’s Game development Imagine Cup competition. Its a simple one-click application that acts as a localhost server and runs an asp.net application.

Its targeted to imagine cup game development competitors who wishes to use submit their game in silverlight that uses a server that you already have in .net.

The core works ok without any crashes yet. I need to do a few improvements so I can submit my game in 1 package and start the project without navigating to it. Stay tuned for more updates on this little application.

The download is located on the left in a Box.net widget. The file is called XorianaServer.exe. Yes Our game is going to be called Xoriana.

Requirements:

My machine is vista sp2 and I’ve tested it on a windows 7 also. But this is what I think it requires:

.NET 3.5 SP1.

Official Description:

Xoriana Server is a local client server that can run ASP.NET 3.5 and under projects the same way visual studio’s internal server does.  (WebDev.WebServer.exe) There are many servers like this around including those used by commercial 3rd party control creators such as Telerik, ComponentOne and Infragistics. This is where I got my idea from.

Instructions:
Start XorianaServer.exe.
Browse to the root path of where you project is located. That is for example, the folder that Default.aspx is located.
There is a default port and virtual path set, if they are already in use, you can change them.

License:
Anyone is free to use this tool, distribute it or whatever.

Future Updates:

1. GUI tuneup, icons, etc.
2. Parameter Passing.
3. Minimize to System Tray.
4. Memory Optimization. (This currently uses 23MB+ Ram)

Also mein erster Post im Lerntagebuch – der Standard-Welcome ist ja wirklich nichts besonderes

Was habe ich bis jetzt für den Kurs gemacht? Viel und wenig!
Zunächst habe ich mir OntoWiki heruntergeladen, ohne mich vorher überhaupt zu informieren was das besondere an OntoWiki ist.

Dann XAMMP gestartet, Konfigurationsdatei editiert, MYSQL-Datenbank erstellt, OntoWiki durch Aufruf von http://localhost/ontowiki installiert.

Sieht gut aus:

Now that I have started my blog on wordpress, i am having all sorts of thoughts to customize it. After doing an extensive research y’day i found that i cant customize ,unless i move my blog to another server.

There are many ways to do this

1> You can you can purchase a plan at a web hosting provider for a few bucks a month.   OR

2>You can set it up on your home computer for free.

I dont intend to spend any money on this blog as of now , n moreover it will be fun to setup your own web server.

The cool thing about blogs (and many other web apps, like wikis) is that they don’t actually have to live online.

Lets look at how to set up weblog on your Windows PC using , WordPress in 7 Steps

Step 1: Install WAMP

1 . WAMP is an open source, simple installation package that bundles together Apache, MySQL, and PHP into one tight little Windows package. You can download WAMP here. Go ahead and accept the defaults unless you have a good reason to do otherwise and you know what you’re doing. Once you’ve finished, direct your browser the http://localhost/ and, if everything went smoothly, you should see the WAMP welcome page above.

Step 2: Change your MySQL password and create a new database

To add a password to your MySQL database. You can do this by clicking on the “PHPmyadmin” link on the WAMP homepage under Tools or by going to http://localhost/phpmyadmin/. To change your password, click on the “Privileges” link, then click the edit privileges icon for the user called, “root” (there should be no other users. If for some reason there are and you didn’t put them there, go ahead and delete them. On the “Edit Privileges” page, go to the “Change password” box, then change and save the password.

To continue using PHPmyadmin, we need to update your password in the config file. Open C:\wamp\phpmyadmin\config.inc.php in your favorite text editor (or just Notepad) and change:

$cfg['Servers'][$i]['password'] = ”;

to

$cfg['Servers'][$i]['password'] = ‘yournewpassword’;

Replacing yournewpassword with the password you just created with PHPmyadmin.

Step 3: Create a new database

Go back tohttp://localhost/phpmyadmin/ and enter a name for your database. It can be called whatever you want, but I kept things simple and called mine, “wordpress”. Hit the Create button and that’s all. Simple, huh?

Step 4: Download and extract WordPress

Go ahead and grab the latest WordPress package here. Unzip the package and extract all of its contents to C:\wamp\www. You can either keep the files in the folder called wordpress, in which case your blog’s URL will be localhost/wordpress/, or you can rename the folder if you’d prefer something like localhost/blog. If you want your root directory to bring up your blog, you can just extract all of the files inside the wordpress folder directly to the C:\wamp\www folder.

Step 5: Configure WordPress

Now we need to tell WordPress about your MySQL database. Assuming you installed WordPress in the default wordpress folder, open C:\wamp\www\wordpress\wp-config-sample.php in a text editor and add your database name, your database username (root), and your new password to the top of the file. (You won’t need to change the DB name if you called it wordpress, but you should replace username with root and password with the password you created in step 2. After you’ve edited the settings, save the file as wp-config.php.

Step 6: Install WordPress

Just go tohttp://localhost/wordpress/wp-admin/install.php (unless you put WordPress in a different folder in step 4). Continue through the dead-simple, two-step installation, until you’ve completed the installation. WordPress will have generated a new username and password that you’ll use to log in to your weblog’s Admin page. By default, the username is ‘admin’, and the password is a randomly generated string. Copy/write it down.

Step 7: You’re done. Configure and post to your blog

go to http://localhost/wordpress/wp-login.php and log in with the username and password WordPress created during the install (you did remember to write it down, right?). The first thing I’d do is change the admin password to something more memorable. To do that, log in and click on the Users tab, where you can add your personal info and change your password. Easy-peasy.

Congratulations, you’ve got your own, personal, locally hosted blog.Now that you’ve got WordPress installed on your local computer, you’ve got a lot of options. If you want to make your blog accessible to the outside world,you need to assign a domain name to your home web server like yourname.com – for an easy-to-remember, bookmarkable, professional web address.

Keep in mind that you wouldn’t be able to run a heavily trafficked blog from your home computer, but if it’s just a personal blog for friends and family, hosting it yourself is definitely an option.

How to assign a domain name to your webserver?

A dynamic DNS service is a constantly updated database of IP addresses and domain names. DynDNS.com is one provider of this service. For free, you can get one of the available DynDNS domain names plus a custom subdomain (like xyz.getmyip.net), or for a small fee you can register your own domain (like ashishjagani.com) and have it resolve to your home computer web server with DynDNS.

• Register for a free account at DynDNS. Agree to the site’s terms, and use a legitimate email address to complete registration. Once in awhile, DynDNS will email you at that address asking you to confirm that it continue your service.
• Log into your new account. Go to the “My Services” area on the left side. Under “Host Level Services” click “Add Host Services.” There, click “Add Dynamic DNS Host.” DynDNS will autofill your IP address (if you’re doing this from your home computer). Choose a domain and type in a custom subdomain, which can be anything from ajfundaes.myblog.org or ashish.is-a-geek.com or aj.dyndns.org.
• Now that your computer is registered with DynDNS, each time your computer’s IP address changes, it has to let DynDNS know. This can be done either with free updater client software or through your router. If your computer is connected directly to the Internet, download the DynDNS updater client for Mac or Windows here. Install and enter your DynDNS information so that your computer can update DynDNS’s database regularly

You’re done. Give your new domain a spin!

Type your new domain name by entering it in your web browser’s address bar. It should resolve to your home server. From here you can publicize or bookmark your server’s new domain name no matter how often your IP address changes.

ওয়ার্ডপ্রেস নিজের ডোমাইন এ ব্যবহার করতে গেলে প্রথমে ডাউনলোড করে কনফিগার করতে হয়। কাজটা এমন কিছুই কঠিন না সবাই পারবেন আশা করি। চলুন দেখি কিভাবে কমান্ড লাইনকে যথাসম্ভব এড়িয়ে গিয়ে কাজটি করা যায়ঃ

লিনাক্স এ localhost সেটআপ করতে হলে আমাদের LAMP সার্ভার ইনস্টল করতে হবে। LAMP এর অর্থ হল Linux,Apache,MySQL,PHP।   ল্যাম্প ইনস্টল করার জন্য সাইন্যাপ্টিক হতে এডিট মেনুতে ক্লিক করে Install by Task নির্বাচন করুন। এখন একটি তালিকা পাবেন। ওখান থেকে LAMP Server নির্বাচন করুন। এরপর Apply করলে ৪০ মেগা নামাতে হবে। এরজন্য আপনাকে কিছুক্ষণ অপেক্ষা করতে হবে। নামানো হয়ে গেলে যখন ইনস্টল করবে তখন MySQL এর একটি পাসওয়ার্ড চাইবে। আপনাকে পাসওয়ার্ড দিয়ে ওকে করতে হবে।

এবার টার্মিনাল চালু করে আমাদের নিজেদের ডাটাবেস তৈরী করতে হবে। আমাদের ডাটাবেজ এর নাম যদি হয় blog তাহলে আমাদের লিখতে হবে

mysql -u root –p . এরপর কিছু লেখা দেখাবে এরকমঃ

nirjhor@nirjhor-laptop ~ $ mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 33
Server version: 5.0.75-0ubuntu10.2 (Ubuntu)

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the buffer.

mysql>

এখন টাইপ করুন create database blog; এখন

mysql> create database blog;
Query OK, 1 row affected (0.00 sec)

এরকম কিছু দেখানোর কথা। যদি তা দেখায় তাহলে কাজ হয়েছে। আপনি এখন quit লিখে বের হয়ে আসতে পারেন। এইবার আমাদের /var/www ফোল্ডারের পার্মিশন চেঞ্জ করে দিতে হবে। একটি টার্মিনাল খুলে লিখুন

sudo chmod a+rwx /var/www

এখন আবার এই লাইনটি লিখুন

sudo gedit /etc/apache2/apache2.conf

একটি ফাইল আসবে যার নিচে এই লাইন দুইটি যোগ করুন

AddType application/x-httpd-php .php .phtml
AddType application/x-httpd-php-source .phps

এবার wordpress.org থেকে .tar.gz ফাইলটি নামায় নিয়ে এক্সট্রাক্ট করুন। এক্সট্রাক্টকৃত ফাইলগুলা /var/www ফোল্ডারে নিয়ে যান। এখানে আগে থেকে যে index.html ফাইলটি আছে তা মুছে ফেলুন। আবার কমান্ড লাইন চালু করে লিখুন sudo /etc/init.d/mysql restart। আমাদের কাজ শেষ।

আপনার ব্রাউজার ওপেন করে localhost লিখুন এড্রেস বারে। এবার অন স্ক্রীন গাইড ফলো করুন। ডাটাবেজ নেম হল localhost  এবং MySQL ইউজারনেম হল root। ব্যাস আপনারা এখন লগইন করে ইউজ করতে পারবেন আপনার লোকালহোস্টেড ব্লগ।

আপনার মতামত ও পরামর্শ জানাবেন।

No recordaba mi blog personal… veo que mi último post es desde mi cumpleaños… vaya, dos meses sin postear jaja, en fin, aquí ando de nuevo, postearé todo tipo de cosas por acá ahora si… no había tenido tiempo (en septiembre, en agosto me hice wey) pero espero que ahora si ya… so… veamos

Lo mejor que me ha pasado desde que abandoné este lugar, es.. que encontré a una chica muy especial y que es linda conmigo y ahora estoy enamorado de ella , pueden ver su blog acá (?). Llevamos poco, pero parece que será lindo y la quiero mucho y eso =D (me vale madres lo que digan).

Por otra parte, es un placer informarles que tengo Google Wave, ese nuevo juguetito de Google que revolucionará el Internet tal y como lo conocemos, vaya, va a marcar un antes y un después como lo hizo Jesucristo en sus tiempos (?).

Les presumo mi wave:

Lo único malo es que no me han dado invites y no puedo invitar a nadie para tener más contactos, pero ya llegarán. Aún así, soy uno de los 800,000 afortunados que tienen Google Wave en todo el mundo =). Si quieren saber más sobre Google Wave, pueden visitar acá para que vean de que va.

Sin más, nos estamos leyendo pronto, solo fue como un update rápido y para presumirles sobre mi GW .

Later.

This tutorial will guide you step by step in Installing WordPress locally in Windows Xp. So for that purpose we use WampServer. Now this Tutorial will tell you procedure to install, configure the wampserver and include WordPress in it and start creating your website in the localhost without the need of an Internet Connection.

It very useful to have a local copy of online content in our computer for easy access and to make any changes or to find errors in our computer itself than finding and correcting it online.

Eğer herşeyiniz hazır ve adres çubuğuna http://localhost/joomla yazarak Joomla kurulumuna başladıysanız ilk kurulum sayfasının en üstünde şöyle bir hata alabilirsiniz:

Deprecated:  Assigning the return value of new by reference is deprecated in C:\xampp\htdocs\joomla\libraries\pattemplate\patTemplate.php

Bunun sebebi büyük ihtimalle XAMPP’ın son versiyonu olan 1.7.2 kullanmanızdır. Çünkü bu XAMPP versiyonu PHP 5.3.0 içerir. Joomla ise şu anda PHP 5.3.0 ile çalışmak için onaylanmamıştır. Bu nedenle daha düşük bir XAMPP versiyonu kurarak sorun çözülebilir. Örneğin XAMPP 1.7.1 kurabilirsiniz. İndirmek için:

XAMPP 1.7.1 download

Aynı şey WAMP için de geçerli olabilir. Çünkü onun da son versiyonunda PHP versiyonu 5.3.0. Onun da düşük versiyonu bulunarak sorun çözülebilir.

Kişisel bilgisayarınızda hazırladığınız PHP ile kodlanmış sayfalarınızın çalışabilmesi için PHP kodlarını yorumlayarak HTML kodlarına dönüştüren bir yapıya ihtiyaç vardır. Bu yapının adı SUNUCU(SERVER)dur.

Normal şartlarda HOSTING (Ev Sahibliği, Barınma) hizmeti alınan şirketler WEB sitesi yayınlama işlemlerini bu SUNUCUlar ile yapmaktadırlar. Biz de hazırladığımız PHP Kodlu sayfalarımızı kişisel bilgisayarlarımızda çalıştırabilmek için YEREL SUNUCU (Local Host)’ya ihtiyacımız bulunmaktadır.

Bu noktada kurtarıcı bir program devreye girmekte ve SUNUCU, PHP ve MySQL (Veritabanı) ihtiyaçlarımızı tek seferde karşılamaktadır. Bu programı bilgisayarımıza kurduğumuzda APACHE sunucusu, PHP ve MySQL’i kurmaktadır.

Kurulumun yapılması ile bilgisayarımızda sunucumuz kurulacak ve “C:\Program Files\EasyPHP-Klasörü\www” klasörü bizim KÖK (ROOT) dizinimiz haline gelmektedir.

Programı çalıştırdığımızda resimdeki ekranı görmekteyiz. Eğer bir sorun yoksa Apache ve MySQL için yeşil ışık yanacak ve “Başlatıldı” ifadesi görünecektir.

Sorunsuz çalıştığını gördükten sonra İnternet Tarayıcımızı açıyoruz ve adres çubuğuna http://localhost/ yazıyoruz ve KÖK dizinimize ulaşıyoruz.

NOT: KÖK dizine direk PHP uzantılı dosya atarsanız göremezsiniz. Kök dizin içerisine klasör oluşturup içerisine dosyaları atmak en mantıklı yoldur.

Programın Adı EasyPHP

Son Sürümü İndirmek İçin

If Firefox is way slow to localhost on your computer, go to about:config and set “network.dns.disableIPv6″ to “true”.

In Google Chrome, it’s not as obvious how to do the same thing, as there is no such thing as about:config. The only way I could find that makes it work is to open “C:\Windows\System32\drivers\etc\hosts” and comment out the line saying “::1 localhost”.

This is now the contents of my hosts file:

127.0.0.1       localhost
# ::1             localhost

I hope that helps someone out there with the same problem!

Which of the two file will get loaded when a request for a directory is made to apache?

I was surprised to find that the behavoiur in my localmachine is different from my linux server. That made me think why this would be happening. The most likely place was “httpd.conf”. And I found the following entry:

<IfModule dir_module>
DirectoryIndex index.html index.html.var index.php index.php3 index.php4
</IfModule>

In my linux server, the configuration was :

<IfModule dir_module>
DirectoryIndex index.php index.php3 index.php4 index.html index.html.var
</IfModule>

What makes apache behaves that way is the order in which these files appear in the file “httpd.conf”

Então, está desenvolvendo um programa para Android e quer saber como ele reagirá ao ser interrompido por uma chamada telefônica? Não há problema nenhum! Fazer ligações para o emulador Android é muito fácil, mas se o seu sistema está com o cliente telnet desativado terá que ativá-lo primeiro seguindo o tutorial abaixo. Para testar se está desativada digite telnet em um prompt. Se você recebe uma mensagem de boas-vindas está ativada.

ATIVANDO TELNET NO WINDOWS VISTA/SEVEN

Para ativar a telnet em um desses sistemas vá em Iniciar -> Painel de Controle -> Programas -> Desinstalar um programa -> Ativar ou desativar funcionalidades do Windows na barra ao lado.

No diálogo que se segue, procure por Cliente Telnet na lista de funcionalidades, marque a sua checkbox e espere um pouco até que ele seja ativado e depois reinicie o computador. Para testar se o cliente está ativado, digite telnet em um prompt de comando. Se apareceu na tela uma mensagem do tipo  ” Welcome to Microsoft Telnet “, parabéns, você conseguiu!

SIMULANDO UMA CHAMADA

Agora que já temos tudo pronto abra um prompt e digite:

telnet localhost 5554

O localhost 5554 pode variar, mas geralmente é esse número. Pode ser visto no título da janela do emulador. Agora vamos fazer a chamada em si. No mesmo prompt digite:

gsm call 11122233

Qualquer número pode ser usado para fazer a chamada, desde que contenho 8 algarismos. Você ouvirá um toque de celular, e ao clicar no botão verde poderá atender a chamada, como na figura abaixo:

On my localhost site, I hadn’t updated permalinks, and when I did it told me I should edit my .htaccess file. I used TextWrangler to “open hidden” to find .htaccess, but it didn’t exist, so I made it and included the suggested code:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /naturallygeeky/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /naturallygeeky/index.php [L]
</IfModule>

Then I had to make it writable so that WordPress could do this automatically from now on – and the Codex to the rescue! I followed the links from the message about making .htaccess writable and pasted the following code in Terminal, and voila!

chmod -v 666 .htaccess

Online, this is all done automatically, but if I want to test stuff locally, I need to learn how to make these changes manually.

My permalinks are now “pretty” using /%category%/%postname%/

I installed WordPress on my hosted site this week – a one click super easy experience using Fantastico through HostGator’s C-Panel. I’ve played around with several themes and done some modifications, but have not added any content yet. I referred to this post-installation checklist from CSS-Tricks to make changes to various preferences. It was all easy and fun to explore and play around with.

When I went to install WordPress locally on my home computer, then, I figured the experience would be about the same. WordPress is famous for its “Five Minute Install” after all! However, my install was slightly longer than five minutes – and in fact took hours because of issues with setting up the database properly.

I am not sure what I did, unfortunately, but it had something to do with changing the password, or setting up a password for the database. I am still unclear about what the settings should be on the database config files, but they are working now, so until I learn more, I don’t think I’ll mess with them! I used PHPMyAdmin to change the password to the database, and then changed the wp-config.php file to match. At first I still had access to PHPMyAdmin, but was getting a “Error establishing a database connection” message when I tried to go to my site. Later, after messing around in Terminal and probably doing more damage than good with my changes, I couldn’t even access PHPMyAdmin, and only got this error message when I tried: “Error: Could not connect to MySQL server!” According to MAMP the MySQL server was running, though.

The thing that fixed it was following the solution presented in this forum for someone with my same issues. I tried with both MAMP and XAMPP, and it worked better (for me) with XAMPP. Macs come with Apache already installed, so all you have to do is turn on personal web sharing in the system prefs. I had already used MAMP to install MySQL previously, but ran into issues making it work properly this time.

Downloading and getting WordPress installed was a snap once the database was up and running, but for a while, I couldn’t even open PHPMyAdmin to make any changes to the database settings because of a database problem, so it was quite frustrating. Especially since it worked when I first started it up, but after I followed some directions (I think on the WP Codex page) for changing the password for the database, nothing worked. One place says the default username / password is ‘root’ / ‘root’, but it turned out to be ‘root’ for the user, but nothing for the password. I guess you can name your database whatever you want and it should work.

My big question about the site and database is how will this correspond to our online files and database? I’m used to creating something offline first then uploading it and having both local and remote files match up exactly. Should I have made my database name and settings exactly match the one Fantastico created for in in my (truly 5 minutes – probably less) online installation?

These lines in the wp-config.php file are what were confusing to me:

// ** MySQL settings – You can get this info from your web host ** // <– does that mean it should be the same locally as on my web host site? Or is this a generic instruction for people manually installing it online?
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘do I put the name of the database I created on my computer or the one Fantastico created when I installed it on my website? and do I need a filepath with the name, or just the name? I just put the local name only.‘);

/** MySQL database username */
define(‘DB_USER’, ‘what user name? the one for my computer? the one for the web host? or do I make up one? where do I find out what this should be if it already exists? I learned that the default is ‘root’ but should I change it, and if so, where else do I need to change it?‘);

/** MySQL database password */
define(‘DB_PASSWORD’, ‘again, which password? do I have to create it first in PHPMyAdmin? I found out that the default is blank (but some sources said the default was also ‘root’ – on mine it was blank, however.‘);

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost – I left this the same and it works.‘);

I wish everyone else much better luck in their local installations! And if anyone reading this has light to shed on the proper database setup and configuration file info, I would appreciate hearing about it.