System Administration https://bryanruby.com/tags/system-administration en A final goodbye to CMS Report https://bryanruby.com/final-goodbye-cms-report-2006 <span property="schema:name">A final goodbye to CMS Report</span> <div class="field field--name-field-image field--type-image field--label-above"> <div class="field--label">Image</div> <div class="field--items"> <div class="field--item"> <img property="schema:image" src="/sites/default/files/field/image/CMSReportLite_1.PNG" width="955" height="759" alt="CMS Report Lite" typeof="foaf:Image" class="img-responsive" /> </div> </div> </div> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2017-12-01T01:23:23+00:00">Thu, 11/30/2017 - 19:23</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p><em>Effective immediately, CMS Report has been shutdown with socPub designated as the website's full replacement.</em></p> <p>Two months ago, I introduced <a href="/introducing-cms-report-lite-2002">CMS Report "Lite"</a> as a slimmed-down version of the original website. Since our rebranding from <a href="https://www.socpub.com/articles/cms-report-now-socpub-15375"><em>CMS Report</em> to <em>socPub</em></a> earlier this year, a number of content management professionals expressed the need to cite reputable CMSReport.com for their information and were uncomfortable with referencing an "unknown" website like socPub. With limited success since bringing this nostalgic website back online, I decided this it was time to: let the past go; redirect all remaining traffic from CMSReport.com to SocPub.com; and to shutdown the website for good.</p> <p>While I had hopes that mirroring the content would be a win-win for both website...the analytics showed otherwise. I was prepared to see a decrease of visitors at one website in favor of another but in reality most of my intended audience targeting North America, Europe, and Australia continued to view content their content at socPub. CMS Report on the other hand attracted less than 12% of my targeted audience with instead 85% of the audience coming from India in the form of bots trying to look for weaknesses in my content management system. </p> <img alt="Google Analytics Showing Location of CMS Report Site Visitors" data-entity-type="file" data-entity-uuid="da013d8d-553f-4e17-bdcb-50d0aef6c8e3" src="/sites/default/files/inline-images/CMSReportVisitors17.PNG" class="align-center" /><p>I want to be clear, India's citizens are always welcomed at my websites. I have a deep respect for content management and information technology professionals from India and some of our best article contributors have come from India. Unfortunately, it was not IT professionals from India that CMS Report was attracting but hackers and bots. Over 98% of the "users" that accessed CMS Report's login screen originated from India. While none of the login attempts breached the website's security...it's a little unsettling that CMSReport.com was being accessed not for it's content but as a target for hackers.</p> <p>With most of our previous CMS Report legitimate audience now visiting socPub, I see no reason to continue to support two websites with similar content. Once again, goodbye CMS Report and hello socPub.</p></div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/final-goodbye-cms-report-2006" st_title="A final goodbye to CMS Report" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/final-goodbye-cms-report-2006" st_title="A final goodbye to CMS Report" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/final-goodbye-cms-report-2006" st_title="A final goodbye to CMS Report" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/final-goodbye-cms-report-2006" st_title="A final goodbye to CMS Report" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/final-goodbye-cms-report-2006" st_title="A final goodbye to CMS Report" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=2006&amp;2=comment&amp;3=comment" token="X_GdBJQt1bKTDKsC6amj-3Rjms6bQoeK0jZ4KnWUn6w"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/deeds" property="schema:about" hreflang="en">Deeds</a></div> <div class="field--item"><a href="/tags/content-management" property="schema:about" hreflang="en">Content Management</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/seo" property="schema:about" hreflang="en">SEO</a></div> <div class="field--item"><a href="/tags/security" property="schema:about" hreflang="en">Security</a></div> </div> </div> Fri, 01 Dec 2017 01:23:23 +0000 Bryan Ruby 2006 at https://bryanruby.com Drupal 8.4 Available and Fixes Significant Database Caching Issues https://bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004 <span property="schema:name">Drupal 8.4 Available and Fixes Significant Database Caching Issues</span> <div class="field field--name-field-image field--type-image field--label-above"> <div class="field--label">Image</div> <div class="field--items"> <div class="field--item"> <img property="schema:image" src="/sites/default/files/field/image/druplicon-large.png" width="1180" height="1350" alt="Druplicon" typeof="foaf:Image" class="img-responsive" /> </div> </div> </div> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2017-10-15T01:58:06+00:00">Sat, 10/14/2017 - 20:58</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p><em>Your hosting account was found to be causing an overload of <strong>MySQL</strong> resources. What can you do? Upgrade your Drupal 8 website to Drupal 8.4 or higher.</em></p> <p>One of my goals in rebranding my website from <em>CMS Report</em> to <a href="https://www.socpub.com"><em>socPub</em></a> was to write diverse articles beyond the topic of content management systems. Yet, here we go again with another CMS related article. The Drupal open source project recently made available Drupal 8.4 and for me this version has been a long time coming as it addresses some long standing frustrations I've had with Drupal 8 from the perspective of a site administrator. While Drupal 8.4 adds some nice new features, I'm just as excited about the bug fixes and performance improvements delivered in this new version of Drupal.</p> <p>When Drupal 8 was introduced it made significant improvements in how it caches and renders pages. That's great news for websites that use Drupal's built-in caching to <a href="https://dri.es/making-drupal-8-fly">speed up delivery</a> of pages or page elements. But there was one unwanted side effect to the cache enhancements, excessive growth of cache tables with tens or hundreds of thousands of entries, and gigabytes in size. For my own website it is not too uncommon to see my database reach 4 GB in size. Let's put it this way, it was no fun to receive a letter from my hosting provider that they weren't too happy of my resource usage. Worse they threatened shutting down my website if I didn't manage the database size better. Just in the nick of time for you and me, Drupal 8.4 delivers a fix to the cache growth by introducing a new default limit of <a href="https://www.drupal.org/node/2526150" rel="nofollow">5000 rows per cache bin</a>.</p> <p>I'm still playing with this change and I haven't found a lot of documentation, but you can override the default row limit in Drupal's settings.php via the setting "<a href="https://www.drupal.org/node/2891281">database_cache_max_rows</a>". For my site, the following settings has helped me keep my MySQL database under half a Gigabyte:</p> <pre> $settings['database_cache_max_rows']['default'] = 5000; $settings['database_cache_max_rows']['bins']['page'] = 500; $settings['database_cache_max_rows']['bins']['dynamic_page_cache'] = 500; $settings['database_cache_max_rows']['bins']['render'] = 1000;</pre><p>For those of you that may not be ready to upgrade to Drupal 8.4 but still need to handle the oversized caching tables today, I had some luck with the <a href="https://www.drupal.org/project/slushi_cache">Slushi cache</a> module. An additional good summary of similar solutions for Drupal 8 versions prior to 8.4 can be found on <a href="https://www.jeffgeerling.com/blog/2017/dealing-drupal-8-and-giant-cacherender-table">Jeff Geerling's blog</a>.</p> <h2>Notable New Features in Drupal 8.4</h2> <p>Of course the purpose of Drupal 8.4 isn't just to address my pet peeve about Drupal caching but also to bring Drupal users a number of new features and improvements. Some of the more significant additions and changes in Drupal that affect me and possibly you include:</p> <h3>Datetime Range</h3> <p>For non-Drupal user I know this is going to sound odd, but despite a number of community approaches there never really been a standard format for expressing a range for date or time commonly used in event and planning calendars. Drupal 8.4 addresses this missing field type with the new core Datetime Range module to support contributed modules like Calendar and shares a consistent API with other Datetime fields. Future releases may improve Views support, usability, Datetime Range field validation, and REST support.</p> <p><img alt="Datetime Range User Interface" data-align="center" data-entity-type="file" data-entity-uuid="115be6a8-8ebb-4643-bc07-c4fb5ca8b4f4" height="395" src="/sites/default/files/inline-images/Drupal84DateTimeRange.png" width="626" /></p> <h3>Content Moderation and Workflow</h3> <p>Although I've been a longtime user of Drupal, for a two year period I managed my website on the Agility CMS. One of the benefits of Agility over Drupal were the workflow and moderation tools delivered "out of the box". The ability to moderate content becomes especially important in websites that have multiple authors and editors collaborating together and in need to mark whether the content is a draft, ready for review, in need of revision, ready to publish, etc. With Drupal 8.4 the Workflow modules is now stable and provides the framework to build additional modules such as the much anticipated Content Moderation module. Currently, the new core Content Moderation is considered experimental and beta stable so additional future changes should be expected. Content moderation workflows can now apply to any entity types that support revisions, and numerous usability issues and critical bugs are resolved in this release.</p> <h3>Media Handling</h3> <p>Another long standing issue for me has been how Drupal handles, displays, and allows you to reuses (it doesn't without outside help) those images. Over the years, there has been a host of solutions found via contributed modules but I've often found myself frustrated that support for these modules vary and often compatible versions are not made available until weeks or months after a new major version of Drupal has been released. The new core Media module wants to change this hurdle by providing an API for reusable media entities and references. It is based on the contributed <a href="https://drupal.org/project/media_entity">Media Entity</a> module which has become popular in recent years within Drupal's users.</p> <p>Unfortunately, the core Media module still needs work and is currently marked <strong>hidden</strong>. In other words Media by default will not appear in Drupal 8.4's module administration page. The module will be displayed to site builders normally once once related user experience issues are resolved in a future release. Although, if you elect to use a contributed module under development that depends on the core Media module it will enable Media automatically for you. Similarly, the REST API and normalizations for Media are not final and support for decoupled applications will be improved in a future release. So while the Media API in available in this version of Drupal, most of us non-developers will need to wait for additional development to see the benefits of this module. </p> <h3>Additional Information on Drupal 8.4</h3> <p>An overview of Drupal 8.4 can be found at <a href="https://www.drupal.org/blog/drupal-8-4-0">Drupal.org</a> but for a better list of the changes and fixes you'll want to check out the <a href="https://www.drupal.org/project/drupal/releases/8.4.0">release notes</a>. As always, links to the latest version of Drupal can be found on the <a href="https://www.drupal.org/project/drupal">project page</a>. I've seen a few strange errors in the logs since updating my site from Drupal 8.3 to 8.4 but nothing significant for me to recommend waiting to install Drupal 8.4. For those that are more cautious, the next bugfix release (8.4.1) is scheduled for November 1, 2017.</p> <p><em><a href="https://www.socpub.com/articles/drupal-84-available-and-fixes-huge-database-caching-issues-15669">Article</a> originally published at <a href="https://www.socpub.com/">socPub</a>.</em></p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004" st_title="Drupal 8.4 Available and Fixes Significant Database Caching Issues" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004" st_title="Drupal 8.4 Available and Fixes Significant Database Caching Issues" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004" st_title="Drupal 8.4 Available and Fixes Significant Database Caching Issues" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004" st_title="Drupal 8.4 Available and Fixes Significant Database Caching Issues" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004" st_title="Drupal 8.4 Available and Fixes Significant Database Caching Issues" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=2004&amp;2=comment&amp;3=comment" token="HWwwPy50wSMBbrnlrJPvG0w49CYbqmkKdYm4lfxzvts"></drupal-render-placeholder> </section> <div class="field field--name-field-disqus field--type-disqus-comment field--label-above"> <div class="field--label">Disqus</div> <div class="field--item"><drupal-render-placeholder callback="Drupal\disqus\Element\Disqus::displayDisqusComments" arguments="0=Drupal%208.4%20Available%20and%20Fixes%20Significant%20Database%20Caching%20Issues&amp;1=https%3A//bryanruby.com/drupal-84-available-and-fixes-significant-database-caching-issues-2004&amp;2=node/2004" token="pr_EQwWCi6f8ag5KA7NJhroVJnZq3kj6gc7gfxb50rk"></drupal-render-placeholder></div> </div> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/content-management" property="schema:about" hreflang="en">Content Management</a></div> <div class="field--item"><a href="/tags/drupal" property="schema:about" hreflang="en">Drupal</a></div> <div class="field--item"><a href="/tags/planet-drupal" property="schema:about" hreflang="en">Planet Drupal</a></div> <div class="field--item"><a href="/tags/open-source" property="schema:about" hreflang="en">Open Source</a></div> <div class="field--item"><a href="/tags/information-system" property="schema:about" hreflang="en">Information System</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/words" property="schema:about" hreflang="en">Words</a></div> </div> </div> Sun, 15 Oct 2017 01:58:06 +0000 Bryan Ruby 2004 at https://bryanruby.com Introducing CMS Report "Lite" https://bryanruby.com/introducing-cms-report-lite-2002 <span property="schema:name">Introducing CMS Report &quot;Lite&quot;</span> <div class="field field--name-field-image field--type-image field--label-above"> <div class="field--label">Image</div> <div class="field--items"> <div class="field--item"> <img property="schema:image" src="/sites/default/files/field/image/CMSReportLite.PNG" width="955" height="759" alt="Screenshot of the new CMS Report" typeof="foaf:Image" class="img-responsive" /> </div> </div> </div> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2017-09-24T22:19:09+00:00">Sun, 09/24/2017 - 17:19</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>Earlier this year I <a href="/introducing-socpubcom-1690">rebranded</a> the website C<em>MS Report</em> to this site, <em>socPub</em>. The website's new identity has allowed me, article contributors, and our readers to explore topics well outside the norm of conversations surrounding content management systems. Although we're going through a bit of growing pains with establishing a new identity under socPub, I'm fully committed to this new website. The change has been good for me and I'm once again inspired to write on topics that interest me.</p> <p>Nevertheless, there is a very loyal segment of longtime readers that want CMS Report back. While some readers want the old site returned for personal reasons, others have expressed a professional need to cite articles from reputable <a href="https://cmsreport.com/">CMSReport.com</a> for their information and are uncomfortable with referencing an "unknown" website like socPub. For this reason, I've decided to introduce a new slimmed-down version of CMS Report. Moving forward, all new <a href="https://www.socpub.com/content-management">content management</a> articles we publish at socPub will also be found at CMS Report.</p> <p>Within the next two weeks I plan to publish a follow-up article that talks about "lessons learned" from the rebrand. This article will also better explains how CMS Report fits in as a "channel" for socPub. If you have any questions, please feel free to ask them below in the comment section.</p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/introducing-cms-report-lite-2002" st_title="Introducing CMS Report &quot;Lite&quot;" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/introducing-cms-report-lite-2002" st_title="Introducing CMS Report &quot;Lite&quot;" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/introducing-cms-report-lite-2002" st_title="Introducing CMS Report &quot;Lite&quot;" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/introducing-cms-report-lite-2002" st_title="Introducing CMS Report &quot;Lite&quot;" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/introducing-cms-report-lite-2002" st_title="Introducing CMS Report &quot;Lite&quot;" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=2002&amp;2=comment&amp;3=comment" token="z4hlGKcBA8Ffd0JDPUNJJ-DLeVw10CKnpsdqX40042g"></drupal-render-placeholder> </section> <div class="field field--name-field-disqus field--type-disqus-comment field--label-above"> <div class="field--label">Disqus</div> <div class="field--item"><drupal-render-placeholder callback="Drupal\disqus\Element\Disqus::displayDisqusComments" arguments="0=Introducing%20CMS%20Report%20%22Lite%22&amp;1=https%3A//bryanruby.com/introducing-cms-report-lite-2002&amp;2=node/2002" token="EQ7jU9qcCUXQDZHlDazJwffqbj1K20lGz423VAgoqe4"></drupal-render-placeholder></div> </div> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/content-management" property="schema:about" hreflang="en">Content Management</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/content-strategy" property="schema:about" hreflang="en">Content Strategy</a></div> <div class="field--item"><a href="/tags/deeds" property="schema:about" hreflang="en">Deeds</a></div> </div> </div> Sun, 24 Sep 2017 22:19:09 +0000 Bryan Ruby 2002 at https://bryanruby.com My Personal Goodbye to CMS Report https://bryanruby.com/my-personal-goodbye-cms-report-1990 <span property="schema:name">My Personal Goodbye to CMS Report</span> <div class="field field--name-field-image field--type-image field--label-above"> <div class="field--label">Image</div> <div class="field--items"> <div class="field--item"> <img property="schema:image" src="/sites/default/files/field/image/cmsreport300x300.png" width="300" height="300" alt="CMS Report Logo" typeof="foaf:Image" class="img-responsive" /> </div> </div> </div> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2016-03-22T02:44:17+00:00">Mon, 03/21/2016 - 21:44</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>Over the years, I've told people that <a href="https://cmsreport.com">CMS Report</a> is a side business. While I would never become rich from this blog, I've been lucky enough to have been able to put a little extra cash in my wallet from this website's ad revenue. In truth, what has actually sustained <em>CMS Report</em> is not money but my passion for information systems. I absolutely love this magical process where people, hardware, software, and infrastructure come together to improve the business or organization. A decade ago, I could find no better example of information systems in the real world than the content management system. I decided to write about CMSs and created a blog and website to host those articles. After spending ten years as this site's founder, editor, and primary writer I've decided it is time for me to move on to some new challenges.</p> <p>What an amazing and crazy ride this has been for someone that started his career as a meteorologist and now works full time in government IT. This was supposed to be a one year exercise for feeding my hunger to learn more about CMSs. Instead, this became a ten year project that tapped into a community of developers, marketers, analysts, founders, executives, small business owners, and entrepreneurs. It has been a joy to have met so many creative, smart, and hardworking people through this website. I received more than I gave. But in the past few years, my passion to write only about CMS topics has diminished and I'm not happy that my articles lack the shine they once had. After considerable thought, I've decided it's time for me to pass the torch to another.</p> <h3>What are my plans after CMS Report?</h3> <p>In the short term, I would like to spend a few months away from blogging and minimize my computer time. I've done this <a href="blogging-still-matters-1945">before</a> and found it beneficial. Given that it is my nature to write, I suspect in my weaker moments I'll want to write about something and will use my personal website to post the articles. You're welcome to join me there.</p> <p>In the long term, I have some new projects that I'm trying to get off the ground. As far as websites go, I'd like to startup a website that reflects my broader interest in technology, social networks, and entrepreneurship. For the past few years, I've been holding close to my chest a domain that I've always thought would be perfect for a rebranding of CMS Report. If I do move forward with the project, the earliest I would bring the new website online is Fall 2016. I'm also not opposed to the idea of being a guest writer on another website. I may even allow myself to become available to do consulting/analyst work for those that need me. Again though, I'm not making myself available to do any of this until I've had time to take a break from it all.</p> <p>If looking back I find that CMS Report was the peak of my online success, I'm perfectly fine with this. I still have a gratefully busy work life as an Information Technology Officer in the National Weather Service. Prior to working in government IT, I was a meteorologist forecasting the weather, accessing a multimillion Doppler radar, and issuing countless lifesaving warnings in my weather career. Outside of work, my time with my family and my community is what I value most. I'm not even 50, yet I have already done things that people still dream about doing. So, you ask, what are my plans? To follow my passions wherever they lead me with absolutely no regrets.</p> <h3>What is to happen to CMS Report?</h3> <p><strong>Starting today, the cmsreport.com domain and/or website is for sale.</strong> If you're interested in making an offer, please let me know. If I do not get a reasonable offer for the domain, I have some other options including transferring the domain to someone I know would be a good steward for this website. I could also merge as a rebranding the traffic from this site to that "new project" I talked about earlier.</p> <p>Until further notice, we're going to put a hold on publishing new articles here at CMS Report. However, we will continue to actively manage our <a href="https://twitter.com/cmsreport">Twitter account</a>. With this Twitter account, I have a long history of advocating for the ideas, stories, people, and companies that do "good work" in the CMS industry and would like to continue to do so.</p> <p>As we put the website in "dry dock", our content will continue to remain available to read and source. Don't be surprised to see the presentation and layout of the website change even if we don't publish new articles. I just can't help myself trying new things out with the CMS that runs this website. Once a CMS enthusiast, always a CMS enthusiast. </p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/my-personal-goodbye-cms-report-1990" st_title="My Personal Goodbye to CMS Report" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/my-personal-goodbye-cms-report-1990" st_title="My Personal Goodbye to CMS Report" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/my-personal-goodbye-cms-report-1990" st_title="My Personal Goodbye to CMS Report" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/my-personal-goodbye-cms-report-1990" st_title="My Personal Goodbye to CMS Report" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/my-personal-goodbye-cms-report-1990" st_title="My Personal Goodbye to CMS Report" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1990&amp;2=comment&amp;3=comment" token="Q2Mms4yLFAD7yDHR-bdHrd861fFUjZupLxNZDjllRmY"></drupal-render-placeholder> </section> <div class="field field--name-field-disqus field--type-disqus-comment field--label-above"> <div class="field--label">Disqus</div> <div class="field--item"><drupal-render-placeholder callback="Drupal\disqus\Element\Disqus::displayDisqusComments" arguments="0=My%20Personal%20Goodbye%20to%20CMS%20Report&amp;1=https%3A//bryanruby.com/my-personal-goodbye-cms-report-1990&amp;2=node/1990" token="O3kBUKbaGJXLN1yK1ws916nu_75_3z3BwaJBO0NbQtw"></drupal-render-placeholder></div> </div> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/content-management" property="schema:about" hreflang="en">Content Management</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/information-system" property="schema:about" hreflang="en">Information System</a></div> <div class="field--item"><a href="/tags/business" property="schema:about" hreflang="en">Business</a></div> <div class="field--item"><a href="/tags/family" property="schema:about" hreflang="en">Family</a></div> <div class="field--item"><a href="/tags/vacation" property="schema:about" hreflang="en">Vacation</a></div> <div class="field--item"><a href="/tags/deeds" property="schema:about" hreflang="en">Deeds</a></div> </div> </div> Tue, 22 Mar 2016 02:44:17 +0000 Bryan Ruby 1990 at https://bryanruby.com The Most Important Feature To Require In Your Next CMS https://bryanruby.com/most-important-feature-require-your-next-cms-1987 <span property="schema:name">The Most Important Feature To Require In Your Next CMS</span> <div class="field field--name-field-image field--type-image field--label-above"> <div class="field--label">Image</div> <div class="field--items"> <div class="field--item"> <img property="schema:image" src="/sites/default/files/field/image/ScreenExport_Agility.PNG" width="382" height="158" alt="Agility CMS with Import and Export" typeof="foaf:Image" class="img-responsive" /> </div> </div> </div> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2016-02-29T04:05:36+00:00">Sun, 02/28/2016 - 22:05</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>When it comes to content management systems, these two questions are the ones that I get asked the most:</p> <ul><li>What is the best CMS out there?</li> <li>What features do I need to have in my CMS?</li> </ul><p>Over the years, I've tried answering that question in various forums. But inevitably my <em>initial</em> answers to the first question are almost always:</p> <ul><li>It depends on what you want to do.</li> <li>It depend on who you're willing to work with.</li> </ul><p>This leaves us with the second question. What features do you need to have in a CMS? The honest answer is I won't know until I better understand your business goals and current workflow. But I can tell you with a straight face what is the <strong>most important feature your new CMS needs to have:</strong></p> <ul><li>The ability to <strong>export</strong> your content <em>easily</em> out of your "new" CMS.</li> </ul><p>Too often, people worry only about importing their content into a new CMS from their old CMS. But what if in a year or two you find your new CMS fails to meet your needs? Before adopting a new CMS, you should have a clear exit stategy for the day your new CMS becomes your old CMS.</p> <p>With some CMSs, the process to leave from one platform to another is an easy one. We just did an Agility CMS to Drupal migration where Agility's software provided easy access to their export functionality. This didn't surprise me because three years ago I researched Agility well and confirmed they had export functionality readily available. Unfortunately, too many CMSs are not like Agility. CMS vendors don't always provide an easy method to leave their CMS and sometimes this is intentional (it's called <a href="https://en.wikipedia.org/wiki/Vendor_lock-in">vendor lock</a>). Website migrations even in the best of circumstances are already difficult and you definitely don't want a CMS where exporting content is made difficult by design.</p> <p>Over the years, I've stressed the importance of <a href="/blogging-still-matters-1945">content ownership</a>. At the end of the day, the only person that should ultimately be in control of your content is you. A number of CMS providers will tell you that data can be exported out of their CMS, but they won't tell you the how is <em>complicated</em>. That complication may include the need to pay a fee to retrieve your own data from their CMS or that the exported data is in an odd format that isn't so easily usable by another CMS. All this messiness is exactly why you should never migrate to a new CMS that doesn't allows you export your own content back out with just a few clicks. Anything more complicated isn't worth you taking the risk of migrating to that new CMS.</p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/most-important-feature-require-your-next-cms-1987" st_title="The Most Important Feature To Require In Your Next CMS" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/most-important-feature-require-your-next-cms-1987" st_title="The Most Important Feature To Require In Your Next CMS" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/most-important-feature-require-your-next-cms-1987" st_title="The Most Important Feature To Require In Your Next CMS" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/most-important-feature-require-your-next-cms-1987" st_title="The Most Important Feature To Require In Your Next CMS" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/most-important-feature-require-your-next-cms-1987" st_title="The Most Important Feature To Require In Your Next CMS" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1987&amp;2=comment&amp;3=comment" token="qvbQB165hA6fByzNwHws9VLEFYrhIz1O-3imcHDGcaE"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/content-management" property="schema:about" hreflang="en">Content Management</a></div> <div class="field--item"><a href="/tags/thoughts" property="schema:about" hreflang="en">Thoughts</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> </div> </div> Mon, 29 Feb 2016 04:05:36 +0000 Bryan Ruby 1987 at https://bryanruby.com Tuesday CMS Expo Panel: Getting Ahead in the Cloud https://bryanruby.com/tuesday-cms-expo-panel-getting-ahead-cloud-1907 <span property="schema:name">Tuesday CMS Expo Panel: Getting Ahead in the Cloud</span> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2013-05-13T06:30:00+00:00">Mon, 05/13/2013 - 01:30</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>At the <a href="http://cmsreport.com/articles/cms-expo-2013-coming-to-chicago-this-may-5304">2013 CMS Expo</a> Learning &amp; Business Conference I have the privilege of moderating a <a href="http://cmsexpo.net/sessions/2-262-Panel_Getting_Ahead_in_the_Cloud">panel focused on the Cloud</a>. That's actually a broad topic, but I think it's a topic that is increasingly becoming well understood by the CMS community. Last year, I moderated a <a href="node/1744">similar panel</a> and, in my opinion, we spent way too much time trying to define the Cloud. This year, I'm hoping we're past the "what is it" phase and spend much more time talking about real problems, real benefits, and the challenges the content management industry may be facing by moving toward a Cloud solution.</p> <p>Over the past few years we've seen the Cloud, like any new technology, move from hype to business reality. We're no longer asking how the cloud is defined. Instead we're asking, is the cloud for my business? We're also asking, how do I get there? This panel will look at how best to transition a business, organization, and development team to the cloud. Better yet, this panel is geared toward helping the audience better prepare for the challenges they will be facing once you are there.</p> <p>I say this with confidence that these type of questions and discussion will be provided in the panel session because of the industry leaders that will be on this panel. I'm very fortunate as a moderator to have the following people joining the panel:</p> <ul><li>Joni Klippert from Standing Cloud</li> <li>Ryan Thrash from MODX</li> <li>Michael Uzquiano from Cloud CMS</li> <li>Michael Assad from Agility CMS</li> </ul><p>If you're going to CMS Expo this week, I hope you join me and the panelists in our discussion. If you have known for sometime that you need to look into cloud solutions, the panelists in this session are there to help you. More importantly, if you have already taken those first steps into the cloud, we will also be talking about some of the frustrations and benefits you need to be aware of once you're there. This panel is scheduled for CMS Expo: Tuesday May 14, 2013 at 2:00 PM. </p> <p>If you're in the Chicago area and a procrastinator, my understanding is that it's not too late to register for CMS Expo. If that's true, try using the following super-secret discount code which you can use to get $100 off the Full Registration price: CMSX75130. I'm not sure if that discount code is still valid, but it's worth a try. By the way, the full registration price also includes breakfast, lunch, snacks, and an endless supply of soft drinks, coffee, and tea!</p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/tuesday-cms-expo-panel-getting-ahead-cloud-1907" st_title="Tuesday CMS Expo Panel: Getting Ahead in the Cloud" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/tuesday-cms-expo-panel-getting-ahead-cloud-1907" st_title="Tuesday CMS Expo Panel: Getting Ahead in the Cloud" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/tuesday-cms-expo-panel-getting-ahead-cloud-1907" st_title="Tuesday CMS Expo Panel: Getting Ahead in the Cloud" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/tuesday-cms-expo-panel-getting-ahead-cloud-1907" st_title="Tuesday CMS Expo Panel: Getting Ahead in the Cloud" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/tuesday-cms-expo-panel-getting-ahead-cloud-1907" st_title="Tuesday CMS Expo Panel: Getting Ahead in the Cloud" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1907&amp;2=comment&amp;3=comment" token="eUJ3mQsh5v8Nlbv9FWXKVU07No_b_JX83AoSiW8gv_w"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/deeds" property="schema:about" hreflang="en">Deeds</a></div> <div class="field--item"><a href="/tags/information-technology" property="schema:about" hreflang="en">Information Technology</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/conference" property="schema:about" hreflang="en">Conference</a></div> </div> </div> Mon, 13 May 2013 06:30:00 +0000 Bryan Ruby 1907 at https://bryanruby.com Hello World, Five Years Later https://bryanruby.com/hello-world-five-years-later-1714 <span property="schema:name">Hello World, Five Years Later</span> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2011-04-28T06:31:00+00:00">Thu, 04/28/2011 - 01:31</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>It was five years ago that I posted in programmer tradition at <em>CMS Report</em>, "hello world". At the time, I expected CMSReport.com to be around for only a couple years which was more than enough time for it to fulfill my purpose. At the time, I had an academic interest in <a href="http://en.wikipedia.org/wiki/Information_systems">information systems</a> and found that Web-based content management systems were a nice way to put theoretical ideas into practical know-how. This site focused on content management systems in hopes of meeting the <em>few</em> other people out there that shared my interests in CMS.</p> <p>In that first post, I actually wrote more than "hello world". The full title of the article was "<a href="http://cmsreport.com/articles/hello-world-new-version-4081">Hello World, New Version</a>". The phrase "new version" was in reference to CMSReport.com not being the first site I created to focus on the CMS.  A couple years earlier, I had tried to start up a website called <em>WebCMS Forum</em>. The online forum was intended to be a "place for those with a passion for web-based applications such as portals, blogs, and forums". I spent a lot of time and money on that site, but in the end few visitors joined in as members to talk about content management systems with me. If Twitter had existed back then I would have easily tweeted "WebCMS Forum RIP #failed".</p> <p>Looking back at it now, I'm convinced <em>CMS Report</em> is a success because of my experience from failing so miserably with <em>WebCMS Forum</em>. Previously, I had tried to build a site for <em>others</em> to express their passion and obsession for their favorite content management systems. Here at CMSReport.com, I took the opposite approach and built the site for the sole purpose to talk about <em>my</em> <em>passion</em> for content management systems. It was a crazy idea to put my opinions at the center of CMS discussions as even now I do not consider myself an expert in content management systems. It was only by circumstance that I later realized people are attracted to other passionate people that ask questions and are willing to go at great lengths to find the answers. If you're looking for the facts you go to Wikipedia but if you're also looking for great discussion from people asking the same questions as you are; it is the blogs you seek.</p> <!--break--><p>Most sites like <em>CMS Report</em> are around because the site is used as a gateway for selling a product such as consulting, training, and website development. I actually didn't know this to be the case when I started <em>CMS Report</em>. As corny as it sound, the only product that I've tried to sell you here is my passion and love for content management systems. Sure, I also sell a little bit of banner space for sponsors but revenue from those ads are mainly to cover expenses and the price tag for attending the occasional CMS related conference. It is my hope that my enthusiasm after five years running this site has shown this to be true because in the end it's all I really have to offer.</p> <p>Eventually, the realities of life will require me to <a href="http://cmsreport.com/articles/crossroads-determining-the-future-of-cmsreport-com-2792">decide the future</a> of CMSReport.com. Running this site on my own has demanded the greatest limited resource I currently have...my time. I want to spend more of that time toward my full time <em>day job</em> as well as becoming the best husband, father, and human being that I can be. No, I'm not saying that I'm ending <em>CMS Report</em>, but I am saying that perhaps it may be time to let this site evolve past me. However this is a discussion for another day. For now, I just want to look back and acknowledge the great five years I've had with CMS Report.</p> <p>What has made the past five years so much fun is getting to know all of you that visit this site. I have always been less impressed with my own writing and more impressed with the comments, emails, tweets, guest articles and friendships that have been sent my way. It's no fun to be obsessed about something like content management unless you can share that obsession with like-minded folks. That sharing of ideas and interests has always been the primary reason for <em>CMS Report</em> to exist as it does today.</p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/hello-world-five-years-later-1714" st_title="Hello World, Five Years Later" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/hello-world-five-years-later-1714" st_title="Hello World, Five Years Later" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/hello-world-five-years-later-1714" st_title="Hello World, Five Years Later" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/hello-world-five-years-later-1714" st_title="Hello World, Five Years Later" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/hello-world-five-years-later-1714" st_title="Hello World, Five Years Later" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1714&amp;2=comment&amp;3=comment" token="4oJMe4haer_d8XkMsnzVlqu2PUnZG_jJjxaIFqoR8EU"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/deeds" property="schema:about" hreflang="en">Deeds</a></div> <div class="field--item"><a href="/tags/business" property="schema:about" hreflang="en">Business</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> </div> </div> Thu, 28 Apr 2011 06:31:00 +0000 Bryan Ruby 1714 at https://bryanruby.com Denial of Service on an Apache server https://bryanruby.com/denial-service-apache-server-1701 <span property="schema:name">Denial of Service on an Apache server</span> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2010-07-06T07:20:00+00:00">Tue, 07/06/2010 - 02:20</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>Last week was a very frustrating time for me. For whatever reason, an unusually number of <a href="http://en.wikipedia.org/wiki/Botnet">botnets</a> decided to zero in on my Drupal site and created what I call an unintentional  <a href="http://en.wikipedia.org/wiki/Denial-of-service_attack">Denial of Service</a> attack (DOS). The attack was actually from spambots looking looking for script vulnerabilities found mainly in older versions of e107 and WordPress. Since the target of these spambots were non-Drupal pages, my Drupal site responded by delivering an unusually large number of "page not found" and "access denied" error pages. Eventually, these requests from a multitude of IPs were too many for my server to handle and for all intents and purposes the botnet attack caused a distributed denial of service that prevented me and my users from accessing the site.</p> <p>These type of attacks on Drupal sites and numerous other content management systems are nothing new. However, my search at Drupal.org as well as Google didn't really find a solution that completely addressed my problem. Trying to prevent a DDoS attack isn't easy to begin with and at first the answers alluded me.</p> <p>I originally looked at Drupal for the solution to my problems. While I've used Mollom for months, Mollom is designed to fight off comment spam while the bots attacking my sight were looking for script vulnerabilities that didn't exist. So with Mollom being the wrong tool to fight off this kind of attack, I decided to take a look at the Drupal contributed model <a href="http://drupal.org/project/badbehavior">Bad Behavior</a>. Bad Behavior is a set of PHP scripts which prevents spambots from accessing your site by analyzing their actual HTTP requests and comparing them to profiles from known spambots then blocks such access and logs their attempts. I actually installed an <a href="http://drupal.org/node/422974#comment-2834608">"unofficial" version</a> of the Bad Behavior module which packages the Bad Behavior 2.1 scripts and utilizes services from <a href="http://www.projecthoneypot.org/">Project Honey Pot</a>.</p> <p>As I had already suspected, looking for Drupal to solve this botnet attack wasn't the answer. Pretty much all Bad Behavior did for me was to take the time Drupal was spending delivering "page not found" error pages and use it to deliver "access denied" error pages. My Drupal site is likely safer with the Bad Behavior module installed, but it was the wrong tool to help me reduce the botnets from overtaxing Drupal running on my server. Ideally, you would like to prevent the attacks ever reaching your server by taking a look at such things as the firewall, router, and switches. However, since I didn't have access to the hardware, I decided it was time to look at my Apache configuration.</p> <!--break--><p>I host my sites on a VPS and use cPanel to help manage the site. While cPanel's defaults will give you a stable server there is definitely room to improve the default configuration. Despite all the places I searched for answers, the Apache documentation itself was the most helpful in helping me find which <a href="http://httpd.apache.org/docs/trunk/misc/security_tips.html#dos">Apache HTTP Server configuration</a> settings I should look when addressing DoS attacks.</p> <p>I eventually looked at two directives to help resolve my DoS attacks, <a href="http://httpd.apache.org/docs/trunk/mod/mpm_common.html#maxclients">MaxClients</a> and <a href="http://httpd.apache.org/docs/trunk/mod/core.html#timeout">TimeOut</a>. For whatever reason, cPanel chooses a default value of 150 for <strong>MaxClients </strong>even though Apache's default is actually 256. Knowing that whenever the MaxClients were reached, my server wasn't accessible to the client, this was the first httpd directive I wanted to change. Raising this number seemed to delay the effects of the botnet overwhelming my server but it didn't quite solve the problem. Now instead of 150 bot requests being capable of stalling out my server, I could process 256 bot requests. All MaxClients did was invite more disrespectful people to a party that was already getting out of hand.</p> <p>So I moved on to what was ultimately the solution in my case, I lowered the value given in the <strong>Timeout</strong> directive. The value configured for the Timeout directive is the amount of time the server will wait for certain events before failing a request. Apache gives the following security tips for how this can be configured to help prevent DoS attacks:</p> <blockquote><p>The <code class="directive"><a href="http://httpd.apache.org/docs/trunk/mod/core.html#timeout">TimeOut</a></code> directive should be lowered on sites that are subject to DoS attacks. Setting this to as low as a few seconds may be appropriate. As <code class="directive"><a href="http://httpd.apache.org/docs/trunk/mod/core.html#timeout">TimeOut</a></code> is currently used for several different operations, setting it to a low value introduces problems with long running CGI scripts.</p> </blockquote> <p>For whatever reason, this directive by default is set for 300 seconds. While I can see a number of reasons why you might need five minutes to run a process before failing the request, that's a value I would be more comfortable to have on an intranet server (fully protected by firewall from the wild wild Web) than on an Internet server. So I lowered the TimeOut directive from 300 seconds to 10 seconds. After the value change, the average requests being processed at any given time dropped from 256 down to around 40.  Most Drupal sites are going to need more processing time than 10 seconds, so you'll find out as I did that this number needs to be higher than 10. So far, I have found a value of 45 for the TimeOut directives allows my site to keep server performance high while handling all those requests from the bots without killing legitimate Drupal related processes.</p> <p>So in the end, if you find that the spambots are overwhelming your Drupal site and you have the ability to override the httpd configuration file, <strong>try lowering the value of your Timeout directive down to 45</strong> or some other low number. Doing this first might just solve your your problem and prevent the need for you to write a long winded blog post about your experience.</p> <p><em>This article first appeared on <a href="http://cmsreport.com/articles/denial-of-service-on-an-apache-server-2778">CMS Report</a>.</em></p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/denial-service-apache-server-1701" st_title="Denial of Service on an Apache server" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/denial-service-apache-server-1701" st_title="Denial of Service on an Apache server" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/denial-service-apache-server-1701" st_title="Denial of Service on an Apache server" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/denial-service-apache-server-1701" st_title="Denial of Service on an Apache server" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/denial-service-apache-server-1701" st_title="Denial of Service on an Apache server" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1701&amp;2=comment&amp;3=comment" token="-ZfZWSV2KUsyRgXlMUdBwzO0o37KPKgXx3qtltnP8ws"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/words" property="schema:about" hreflang="en">Words</a></div> <div class="field--item"><a href="/tags/drupal" property="schema:about" hreflang="en">Drupal</a></div> <div class="field--item"><a href="/tags/planet-drupal" property="schema:about" hreflang="en">Planet Drupal</a></div> <div class="field--item"><a href="/tags/spam" property="schema:about" hreflang="en">Spam</a></div> <div class="field--item"><a href="/tags/security" property="schema:about" hreflang="en">Security</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/information-technology" property="schema:about" hreflang="en">Information Technology</a></div> </div> </div> Tue, 06 Jul 2010 07:20:00 +0000 Bryan Ruby 1701 at https://bryanruby.com Serving a home for my Drupal site https://bryanruby.com/serving-home-my-drupal-site-1673 <span property="schema:name">Serving a home for my Drupal site</span> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2009-11-04T07:53:00+00:00">Wed, 11/04/2009 - 01:53</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>We lasted nine months. That's right, for nine months we hosted our <a href="http://drupal.org">Drupal</a> site with a shared hosting account. Last January, I knew we were taking a <a href="http://cmsreport.com/articles/drupal-on-a-budget-ii-2605">gamble</a> but the monthly cost savings for hosting the site was just too tempting. In this end though, <em>CMS Report</em> was too busy and exceeded the shared hosting provider's CPU usage policy.</p> <p>So, during the past few days I've been busy moving the site onto a <a class="ext" href="http://en.wikipedia.org/wiki/Vps">Virtual Private/Dedicated Server</a>. This time, I'm going with GoDaddy but as far as self-managed VPS/VDS goes there are a lot of good companies you can go with. Although I can do Web server administration in my sleep, I think I'm going to miss having someone else doing the server management for me. I know there are better hosting options for professional Drupal sites but I don't think I'm in need for a high-end hosting plan for this amateur site of mine.</p> <p>One of the common mistakes website owners make is not recognizing the growth of their site. We all try to do things as cheap as possible and often fail to recognize the increasing size of our content management system or the increasing popularity of our site. In the Fall of 2007 I made this <a href="http://cmsreport.com/articles/drupal-on-a-budget-no-more-2334">mistake</a>. The hosting provider locked access to my site and I spent a stressful week getting my database from the hosting company and placed onto a new server.</p> <p>This time around I'm happy to report that no disaster occurred. Although the shared hosting provider, AN Hosting/MidPhase, did lock my account out for a few hours they were professional and treated me professionally. Once contacted, in a matter of minutes they brought my site back online and trusted me to remedy the solution. After the second over CPU limit notice, I notified them that I would be taking my site off their server and they were very accommodating in helping me out while I transitioned onto the new server. I wish more shared hosting providers like AN Hosting recognized that just because their plans are cheap you don't have to treat your customers as such.</p> <p>I tend to look at the bright side when change is required. Now that I'm back to hosting my site on a VPS...I have room to try new things. Can anyone say Drupal 7? Just as I did <a href="http://cmsreport.com/articles/another-weekend-with-drupal-6-2459">with Drupal 6</a>, I plan to test Drupal 7 on CMSReport.com once it's the Beta / Release Candidate stage. When I say testing, I mean temporarily upgrading this site on the production server from Drupal 6 to Drupal 7. I'll of course do this on weekends and move back to Drupal 6 during the weekday. It's a nice way of showing the progress of Drupal 7 to others and one way to show how close Drupal 7 is ready for production.</p> <p><em>This article first appeared on <a href="http://cmsreport.com/articles/serving-a-home-for-my-drupal-site-2736">CMS Report</a>.</em></p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/serving-home-my-drupal-site-1673" st_title="Serving a home for my Drupal site" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/serving-home-my-drupal-site-1673" st_title="Serving a home for my Drupal site" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/serving-home-my-drupal-site-1673" st_title="Serving a home for my Drupal site" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/serving-home-my-drupal-site-1673" st_title="Serving a home for my Drupal site" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/serving-home-my-drupal-site-1673" st_title="Serving a home for my Drupal site" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1673&amp;2=comment&amp;3=comment" token="fZWc9wc1gVRWSgVSgFjr0JN9j9nA9Fe0nplP2AhSBoQ"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/words" property="schema:about" hreflang="en">Words</a></div> <div class="field--item"><a href="/tags/drupal" property="schema:about" hreflang="en">Drupal</a></div> <div class="field--item"><a href="/tags/planet-drupal" property="schema:about" hreflang="en">Planet Drupal</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> <div class="field--item"><a href="/tags/information-technology" property="schema:about" hreflang="en">Information Technology</a></div> </div> </div> Wed, 04 Nov 2009 07:53:00 +0000 Bryan Ruby 1673 at https://bryanruby.com Drupal on a Budget II https://bryanruby.com/drupal-budget-ii-1615 <span property="schema:name">Drupal on a Budget II</span> <span rel="schema:author"><span lang="" about="/users/bryan-ruby" typeof="schema:Person" property="schema:name" datatype="">Bryan Ruby</span></span> <span property="schema:dateCreated" content="2009-01-26T07:25:00+00:00">Mon, 01/26/2009 - 01:25</span> <div property="schema:text" class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>I have never had good luck <a href="http://cmsreport.com/articles/drupal-on-a-budget-2257">hosting my Drupal sites</a> on shared hosting plans.  My last venture into budget hosting was a <a href="http://cmsreport.com/articles/drupal-on-a-budget-no-more-2334">disaster</a> with the hosting company locking me out of my own account due to too many requests to the remote database.  The truth is that I've only been happy with running my personal Drupal sites on virtual private servers (VPS).  However, I'm having a difficult time justifying my yearly costs of using a VPS to host my sites. </p> <p>The problem is that I'm finally realizing one of the goals I set for 2007, a resolution to reduce my workload outside of work.  Specifically, I've spent the last year getting rid of most of my freelance work not related to my <em>day job</em> or <em>CMS Report</em>.  So now that I have less sites to host it has become less cost effective to run my remaining Drupal sites on the VPS.  With my yearly VPS contract up this month, I decided to give cheaper shared hosting another chance.</p> <p>A couple weeks ago, I moved CMSReport.com over to AN Hosting.  My choice of using AN Hosting for CMS Report is solely based on <a href="http://blamcast.net/articles/drupal-hosting">John Forsythe's recommendation</a> that AN Hosting provides a reliable Drupal hosting service.  <em>CMS Report</em> has only been on AN Hosting's plan for a couple weeks and so far the site seems to be running fine.  I am a little concerned during peak traffic hours my Drupal site may be to much for this shared hosting plan, but I'm hopeful that everything will be fine.  One of my <a href="http://cmsreport.com/articles/using-wordpress-city-saves-19-000-2604">posts</a> last week attracted quite a bit of attention and yet everything <em>appears</em> to be running smoothly.</p> <p>If I do run into problems with AN Hosting, I promise you this...John Forsythe will likely be the first person I talk to after I've recovered my site.</p> <p>For my remaining Drupal sites, they have been moved over to shared hosting at GoDaddy. I've also moved a few Wordpress sites over to this same plan.  My experience with GoDaddy's shared hosting plans for running non-Drupal sites such as Wordpress, Joomla!, osCommerce, and SMF have been positive.  I'm hoping for low traffic sites that GoDaddy is now ready for Drupal.  GoDaddy's shared hosting plans have improved greatly over the past couple years in terms of database privileges.  Even better yet, GoDaddy now offers secure shell in their higher shared hosting plans.</p> <p>So in a nutshell, besides using a VPS for your Drupal sites you might want to take another look at cheaper shared hosting plans.  Or then again, you may want to just watch <em>CMS Report</em> and see if we crash and burn once more.  I hope not... </p> <p><em>This article first appeared on <a href="http://cmsreport.com/articles/drupal-on-a-budget-ii-2605">CMS Report</a>.</em></p> </div> <div class="sharethis-wrapper"><span st_url="https://bryanruby.com/drupal-budget-ii-1615" st_title="Drupal on a Budget II" class="st_facebook_large" displayText="facebook"></span> <span st_url="https://bryanruby.com/drupal-budget-ii-1615" st_title="Drupal on a Budget II" class="st_twitter_large" st_via="MrBryanRuby" st_username="" displayText="twitter"></span> <span st_url="https://bryanruby.com/drupal-budget-ii-1615" st_title="Drupal on a Budget II" class="st_googleplus_large" displayText="googleplus"></span> <span st_url="https://bryanruby.com/drupal-budget-ii-1615" st_title="Drupal on a Budget II" class="st_linkedin_large" displayText="linkedin"></span> <span st_url="https://bryanruby.com/drupal-budget-ii-1615" st_title="Drupal on a Budget II" class="st_email_large" displayText="email"></span> </div><section rel="schema:comment"> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1615&amp;2=comment&amp;3=comment" token="PromnmL5xIFTESXF3_-rat6ywZdHA6ss90VHGlnKmCM"></drupal-render-placeholder> </section> <div class="field field--name-field-tags field--type-entity-reference field--label-above"> <div class="field--label">Tags</div> <div class="field--items"> <div class="field--item"><a href="/tags/words" property="schema:about" hreflang="en">Words</a></div> <div class="field--item"><a href="/tags/drupal" property="schema:about" hreflang="en">Drupal</a></div> <div class="field--item"><a href="/tags/planet-drupal" property="schema:about" hreflang="en">Planet Drupal</a></div> <div class="field--item"><a href="/tags/system-administration" property="schema:about" hreflang="en">System Administration</a></div> </div> </div> Mon, 26 Jan 2009 07:25:00 +0000 Bryan Ruby 1615 at https://bryanruby.com