Displaying 1 - 20 of 129
β¦ and the final version number is applied and a matching git tag is created. Then the CI system looks up the deployment β¦ addresses turn into links automatically. Allowed HTML tags: <a href hreflang> <em> <strong> <blockquote cite> β¦ and the final version number is applied and a matching git tag is created. Then the CI system looks up the deployment β¦
β¦ Fred Hutchinson Cancer Research Center eagle-i Integration FHCRC Shared Resources About Fred Hutchinson β¦ module... β¦ Fred Hutchinson Cancer Research Center eagle-i Integration β¦
β¦ engagement features -- forums, voting, subscriptions Client/Vendor extranets, protected portals Membership β¦ engagement features -- forums, voting, subscriptions Client/Vendor extranets, protected portals Membership β¦
β¦ this is pretty much a solved problem -- you deploy a "Continuous Integration" (CI) server like Jenkins, and set it to β¦
β¦ git repositories, configuration management tools, continuous integration tools, project management systems, and β¦
β¦ on master is if we have to roll back to a previous release tag, if something truly went wrong. Staging is where things β¦ most of the deployment scenarios we run across. And while I can go into a lot of detail about why we've adopted this β¦
β¦ to your site! This is not a plug-and-play module -- it integrates pretty deeply into your site's information β¦ to your site! This is not a plug-and-play module -- it integrates pretty deeply into your site's information β¦
β¦ from 0.9 to 22, smart phones, tablets, and more. Within business, we've seen web sites evolve from static brochures β¦ and prevention of all data loss are critical to your business, and you'll need to spend a lot more. So here are β¦ agile, anticipating and helping you leverage your changing business environment. So there are a couple crucial questions β¦
β¦ addresses turn into links automatically. Allowed HTML tags: <a href hreflang> <em> <strong> <blockquote cite> β¦
β¦ 8 site was being developed, to keep content fresh for continuous design and development work. We identified the β¦ placement throughout the site, and better social media integration. We were able to get them a lot of what they β¦ 8 site was being developed, to keep content fresh for continuous design and development work. We identified the β¦
β¦ available, and sometimes hit bugs in Dojo itself. So as I mentioned in a previous post, I often find myself teetering β¦ files for security reasons. Switching between trunk and a tag So far so good. We have the basics of an application set β¦ Simple. Just check it out: cd public_html/dojo git tag # shows you a list of available tags git checkout β¦
β¦ that were no longer where they used to be Consolidating tags into our current set we want to make a bit cleaner Customer payment profiles, to continue charging our clients who auto-pay their bills as β¦ content and brought it forward, fixing the issues so it continues to look ok (actually better than it ever has β¦
β¦ How much testing do we need before we make a change to the production site? What data could we lose, from the production site? What might go wrong with this deployment β¦
β¦ I would summarize these as follows: Much better integration, more consistent interface for managing both β¦ But let me back them up with some specifics. Better Integration Add-ons to Drupal integrate much deeper in the β¦
β¦ Ask Freelock: Build, embed, or integrate SaaS with Drupal? Submitted by John Locke β¦ users seem to grab widgets from all over the place, and embed stuff from all sorts of Software as a Service β¦
β¦ you need them, including: Multiple page articles Quantcast integration, for demographic tracking Apture integration, for highlighted balloons of related content β¦ you need them, including: Multiple page articles Quantcast integration, for demographic tracking Apture integration, for β¦
β¦ to a new point release of Drupal means merging the new tag into our branch. Then we've written a script to update β¦ and the development copy on develop. And it created a git tag for the particular release. On production, we have β¦ back to development and re-roll the release. git log/git tag -- identify the current state of the code base -- should β¦
β¦ package. The main things missing are payroll and integration with other business systems. LedgerSMB is a true β¦ device, including many PDAs. We can provide the integration with other systems, custom reports for your β¦ package. The main things missing are payroll and integration with other business systems. LedgerSMB is a true β¦
β¦ Once the dev site is updated, we create a new release tag and push it into our central git repository, where β¦ regular backups of the files. We do a final snapshot/tag of the production code base, then pull down the new β¦ Once the dev site is updated, we create a new release tag and push it into our central git repository, where β¦
β¦ pages are linked correctly, pictures and pages have been βtaggedβ with information about them, and the site can be β¦ world of SEO, they cannot just put terms on their page and tag pictures and be done with itβthey have to walk a mile in β¦ addresses turn into links automatically. Allowed HTML tags: <a href hreflang> <em> <strong> <blockquote cite> β¦