In March 1999, Microsoft released Internet Explorer 5, which supported favicons for the first time.
Google nor any visitor will see a change unless they look at the source code of the website. We’re going to make a few minor changes to make it possible to use this addresses without having to add a redirect. Let’s assume we’ve got an existing non-concrete5 site where the page paths look like this: Sometimes the trailing slash is missing but that doesn’t matter in our case. Before we start, you should know how a page path in concrete5 looks like. In this article we’re going to look at the last option. Make sure the old links still work but changing the concrete5 URLs.There’s an add-on for this written by ScottC that handles this task very nicely, Add a proper 301 redirect that forwards the visitors to the new page.
Do nothing and wait till Google updates its index, but keep in mind that other websites might never update their links unless someone tells them to do so.What choices do you have in such a situation? Depending on the old CMS, if there was one, the URLs might look different than common concrete5 URLs. If you move an existing site to concrete5 which was in the internet for a while, you’ll have a number of websites that point to your site. This article might be very specific for one issue and also a bit hacky, but something when you care about your search engine ranking a lot, it might be good idea to look at it.
However, I’m pretty confident that I could get concrete5 running on App Engine. I’d very much like to finish the experiment but I’ll wait till I have a project where I actually make some money before I spend money. Since I wanted to move my concrete5 site concrete5.ch to Google App Engine, the fact that storage isn’t free, is a killer argument at the moment. Here are a few technical things that you might want to check out. There are two different options, first Google Cloud Storage which is a simple database without a lot of functionality, if you want to port an existing SQL based application, you might want to look at Google Cloud SQL which is a MySQL database running in the cloud.
From what I can tell, you can run a PHP application for free but as soon as you want to store something in a database, you have to pay.
Unfortunately I wasn’t aware of that, I thought that if I only use very little resources, App Engine would be free. When working on your local computer, you can easily use your existing MySQL installation but if you want to deploy your application to the cloud, things work a bit different.
This is where you specify your applications settings as well as redirect rules. As you can see in this tutorial, Google doesn’t use a htaccess file but rather a file called app.yaml.
The Hello world tutorial explains almost everything you need to know to get concrete5 running, I’d recommend that you follow it too, it only takes you a few minutes to install everything and get the famous “hello world” output on your screen. You’ll need to install Python, PHP as well as the Google App Engine SDK for PHP, more about that here. The documentation has clear instructions that help you to get a test environment ready on your local computer. No surprise, I wanted to see if I could get concrete5 running on GAE for PHP. It’s a neat CMS to work with for end users but also very powerful to extend for developers. If you’re a returning visitors to this blog, you’ll probably have noticed that I often work with a CMS called concrete5. The official documentation is available here and gives you a lot of information to get started: You might have read or heard that Google added PHP as a supported language to their cloud hosting platform App Engine.