When using Aegir to upgrade production websites I follow a method very similar to the one outlined by Omege8cc – Safe Workflow
The safe workflow technique is nice as it lets you migrate sites into production without having to bring your live site down to basically test the migration. Occasionally, during the test migration Aegir reports that the migration has failed. However, if I look at my files it has successfully moved the entire site to the new platform but could not delete the settings.php file from the old platform and site. The important thing to check is that everything is now actually on your intended platform and is properly setup, vhost files, files dir, settings.php, etc…
If everything is peachy, Aegir did everything besides deleting the old settings.php file correctly. So, to clean up your Aegir interface you first want to delete the site that failed not using the delete button but by clicking the edit tab on the site and then in the URL changing the word edit to delete, and press enter. Confirm the deletion of the site.
Then on the server, delete the remaining old files off of the original platform. On the new platform navigate to your recently migrated site and change the file permissions on settings.php to 664. When you do your final migration Aegir will set the permissions back to the proper settings.
Next, go to the platform you migrated your site onto and verify the platform. Aegir will pick up the site, import it and you will be ready to finish your migrations.
I can blog and share my thoughts, code snippets, pictures, etc… with you my friends, the transient visitors, regulars, and the bots who see and digest my blog and other sites.
This can happen because you have unfettered access to my site. No one is blocking your attempts to visit, at least not if you are in the USA. I also don’t have to pay any extra for you to see the content I publish. I watched the FCC hearing live and after Tom Wheeler said his piece I was under the impression that he was for net neutrality. Then the vote was taken and I realized what he had been saying was in favor of a regulated internet.
My career has been built on an open internet and the sharing of thoughts. If a website like SitePoint, once a scion of the early CSS web development movement, had at that time had to pay to ensure a user could connect at a decent speed, I don’t think they would be around, which possibly means my current job, would not be around. There are data intensive services, case in point is Netflix. Now sure, I watch Netflix, but I don’t watch cable TV, and as a recent Huffington Post article details Netflix is taking up 34.2% of internet traffic so I would think a percentage of those folks don’t watch cable either. Comcast and other internet data providers are often said to throttle the internet for traffic intensive services. Netflix is also competition though, served over the cable provider’s infrastructure. In the future as more and more devices get connected and we have more bandwidth intensive applications running it won’t just be Netflix that is an issue.
The FCC needs to take a stand and ensure that the internet is a public good. If more bandwidth is needed, why can we not start laying fiber to the home, FTH, so that bandwidth is not an issue. That is happening in many places and there is a grass roots movement to provide quality service to underprivileged areas. My favorite is The Free Network Foundation. The solution should not be charging other companies more money if they want to provide a popular product. A tiered system is not the solution.
Please let the FCC hear your voice. Go to http://www.fcc.gov/comments and click 14-28 and leave a public comment. So many people are doing this, there are 26,726 comments at this point in time 5/19/2014 10:18PM PST. Add your voice.
I started playing with Pico CMS this weekend. I converted everything that is on my Concrete5 based site into the Pico site on my development box. I am pretty happy so far with the system.
The markdown syntax is not hard, it is just unfamiliar to me. However, I can already see how it simplifies content entry. Once I get up to speed it will be fast and quite fun. Creating links with () as a syntax is cool.
I also was not aware that tabs in your formatting makes Markdown misbehave. I am quite certain it is a feature, so that if you want to show code in pretty formatting you can just tab on a new line and it will output HTML rather than rendering the HTML. The same is true if you want a list and you press tab and then use an asterix, no list appears just an asterix and your content on the screen.
I have not yet determined the best way to include a “widget” in the markdown syntax. For instance, I have a display of recently read books generated from Good Reads and the HTML/JS/CSS that is generated for that is bulky. I would love to be able to include that chunk of code with something like
<?php include ('goodreads.html'); ?>
That may be possible but I haven’t figured it out yet as the include would be in a .md file not .php. For now, I just pasted the chunk into the page and it works but it does not seem to be maintainable.
It is simply awesome to be able to create directories and have that become a path that is responded to by the CMS.
The system is so raw it lets me really see the web as a canvas again for playing and experimenting on.
In Drupal, it is very easy to create new paths using path-auto and alias. However, where that page lives is in the database. When it comes time to do a redirect it updates the database. Within the Pico paradigm, you just move the file or directory and the paths are updated. An Apache rewrite rule I am sure would be needed for continuity but there is no admin interface to go into, no menu structure to explain, it is simple. That is refreshing.
The default theme is not responsive but it doesn’t do anything with the content either. It is plopped onto the screen. As Pico is based on Twig I am excited to build a simple Twig and Singularity based theme. The theme will also have some classes built in to support slideshows. It will be a good adventure.
My website is powered by Concrete5 and WordPress. I develop professionally sites in Drupal. Now, I am considering migrating my blog and site to Pico. It is an interesting landscape, these “flat-file” CMS systems. There are a few very exciting looking pay-to-play products, Statamic and Kirby. However, Pico is free, uses an MIT license, and is built by the folks at Dev7 who seem to make nice products, and frankly it looks good out of the box as well.
I am a happy vi user so using a product name pico has a bit of an internal dig built into it. There are several other free flat-file systems out there as well. What I find intriguing about Pico is that it uses the twig template system. The twig system is what powers the themes in Drupal 8 so there is a good chance what I learn in Pico will be applicable to my D8 theme modifications and vice-versa.
What all of these systems use for text entry is Markdown. I am slowly beginning to see the convenience of it though HTML isn’t difficult for me, learning Markdown has been a process. Making lists with an * or headings with ## is quite cool. I’ll be able to adapt.
Pico’s code seems to be fairly stable too. The github issue page is fairly active and folks are making pull requests. This is what makes choosing a new system difficult, trying to answer the question of will it be around in the future? One way to make sure it sticks around is to take the plunge and give it a try.
For those of us who work with digital goods every day it can be hard to find meaning in the work we do. It is certainly something I struggle with. I stumbled upon The Pastry Box Project during the summer last year.
The site in their own words is thus,
“Each year, The Pastry Box Project gathers 30 people who are each influential in their field and asks them to share thoughts regarding what they do. Those thoughts are then published every day throughout the year at a rate of one per day, starting January 1st and ending December 31st.”
I don’t read it every day but when I do I generally can’t stop. There may be a focus of some sorts but it generally seems random. I would call it a Chicken Soup for the Web Makers Soul. Most of the posts resonate and give unique perspectives to what we do. If you are looking for motivation or at times commiseration, I recommend you browse through some of the posts.