The benefit of using GIT in the way below is that it maintains version history AS WELL as offering a managed host, i.e. it deals with uploading as well as versioning (in 1 git bash push.)

So here’s the scenario – there’s one of you, or maybe a few core founders/dev’s and you want to use GIT to version control your developments of a new web app or site. You already have a shared hosting account with 1and1 which works fine up to 20k hits a day or so, is there really need to have the thing scalable on demand from day one? No? Great, read on. If you REQUIRE scalability off the bat (I bet you don’t, really) then go find a PaaS/jump on AWS, for now here’s how to get GIT versioning (with automatic publication) working on your 1and1 shared hosting.

Firstly go read this, its a great guide that pretty much* got me there (95% of the credit to Abhijit), there’s just a few changes to get it to work on 1and1.

How I did it: GIT on 1and1

Load up your FTP, get to the root of your hosting and make your main site dir, in this case we will call it AppDev1:
/AppDev1
Next make two directories underneath it: “repo” and “live”, I shall explain these after you have made them:
/AppDev1/live
/AppDev1/repo
What these two are going to do is give you a live “root” for your web app/site as well as a GIT repository (which stores all the changes.) By separating them you keep everything simple. [live = web root folder, repo (or whatever you call it) = git bare repository.]

Next locally (on your machine) create a folder which you want to develop in:
C:/EpicNewApp

…And load up GIT BASH (assume you have) and enter the following:
cd "C:/EpicNewApp";
git init;

Next go ahead and load your SSH client (putty) and log into your 1and1 Account (there is guidance on 1and1 under SSH accounts, if you need it.) Once logged in enter the following:

cd "/AppDev1/repo"
git init --bare
cat > hooks/post-receive
#!/bin/sh
GIT_WORK_TREE="../live" git checkout -f
chmod +x hooks/post-receive

*note: This differs from the aforementioned guide in the address entered under GIT_WORK_TREE, this is the only way I could get this setup to work on 1and1.

You can also simply stick these lines into a file called post-receive and upload the file to the “hooks” folder of your new bare repository (repo), if you are so inclined.

That’s it, your done with the SSH, now you can bind a remote location in GIT BASH (replace the obvious:)
$ git remote add web "ssh://u99999999@yourMain1and1Domain.com/~/AppDev1/repo/"
…And go ahead and push to 1and1 (you will need your SSH password to do so.)
$ git push web +master:refs/heads/master
All being well this should have pushed a version to your /AppDev1/repo folder and also updated the live files as per your changes!

Happy Ghetto Versioning!

Note: As per comments, removed .git reference from link, thanks Ano.

The post 1and1 Web Hosting & Git – Installing it for singular dev first appeared on Woody Hayday | Blog.

You can host facebook apps on any host, but hosting somewhere unsecure (not accessible via https) will flag up the following prompt for anyone browsing to the page with secure browsing turned on (high proportion of fb users.) You CAN also use amazon cloud storage (S3) for free https file storage, up to a level, however you cannot run server side code (php/ASP.NET) without setting up a server with their EC service.

Not pretty eh? What will that do to your conversion rates? Yep nothing good.

Its not just the mavericks either, for example brands like banana republic are still running http stuff, prompting the user with this message on loading their like-capture pages.

Set up 1and1 shared hosting to host Secure SSL facebook apps/applications/tab pages

So anyway here’s the cheap, quick way to hosting your facebook apps SECURELY using 1and1 shared hosting.

1. Log onto admin.1and1.co.uk (or .com)
2. (Optional) Register a domain name which you don’t mind generically hosting your fb content. For me this is www.whfb.co.uk – this will only show up if users looked at the information for the frame, probably wont ever matter, but if you are running a whole host of different niche pages it might be worth it for simplicity/segmentation.
3. Go to domain management section and click “Shared SSL Encryption” under SSL option
   
4. Assign the Shared SSL Encryption to your generic domain/main domain you want to use
   
5. Setup a folder under your domain like you would with any facebook page, use the facebook php api to fangate or just put some html up there, bare in mind all objects referenced in what you put up should direct resources to “https” not http. That is if you reference “http://www.example.com/someimage.png”, switch the http for https (save your own copy of the file if you need to. Referencing images locally in the folder should work fine for http/https if you use the same domain.
6. Setup your facebook app (theres thousands of guides on this…) and set the following (under “Select how your app integrates with Facebook -> Page Tab”)
   
7. Add the app to your facebook fan page and visit it, (setting it as default landing page perhaps ;)) – you should not get any security messages, if you have you need to go back and check your html is pointing to any external elements via https.

Chances are if you are running 1and1 shared hosting (or any other major) then you will have SSLRelays free of charge with your package, what’s more this takes about 1 minute to setup, so test with this before you stick stuff in the cloud!

The post Hosting facebook Apps/Applications/iFrame Pages on 1and1 (SSL) first appeared on Woody Hayday | Blog.

1. Use getcwd to find the working directory (make a new .php file with two lines “echo getcwd().'<br />’;” and “phpinfo();”, ftp this to the root of your domain on 1and1 shared hosting and then navigate your browser to the url and leave this open in a tab/write it down)

2. Download Linux (x86) .zip archived ionCube loader files from here (http://www.ioncube.com/loaders.php)

3. Upload ionCube folder to the absolute root of your hosting (this is so you don’t have to maintain a copy per website later if you have multiple sites) – I called the folder ioncube

4. Open up notepad and add a line “zend_extension = /homepages/**/**********/htdocs/ioncube/ioncube_loader_lin_5.2.so” – where the **** will be letters/numbers you will be able to find these out from step 1 – save this as php.ini on your desktop or similar (unless you already have a php.ini for this website/subfolders of this website at which point you will want to make a copy of them and add this line then re-upload)

5. Upload php.ini to the domain’s root folder (where you require ionCube to be loaded)

6. Revisit your original .php file and search the page – you should now find “ionCube” under additional modules

Notes:

• If  you are using something like auction2post you may need to copy this php.ini into any subfolders which have .php files in that may need ionCube, this seems to be a slight bug in the 1and1 php.ini system
• There is a 1and1 guide for doing this, however its not particularly helpful (http://faq.oneandone.com/miscellaneous/24.html)
• You might wan’t to make 1and1 run php5 before you do this, depending on what you are using it for – this will mean adding “AddType x-mapp-php5 .php” to the domains .htaccess file

The post ionCube on 1and1 shared hosting first appeared on Woody Hayday | Blog.