archive-nl.com » NL » L » LIMOENGROEN.NL

Total: 242

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Drupal | LimoenGroen
    step further and demands explicit consent read more 09 Oct 11 Pro actieve monitoring op uw websites LimoenGroen heeft niet voor niets degelijkheid als één van haar pijlers Toch kan het gebeuren dat een ontwikkelde website om wat voor reden dan ook tijdelijk of voor langere tijd niet beschikbaar is Vervelend voor de eigenaar van de website maar ook voor ons Om niet voor verrassingen te worden gesteld richt LimoenGroen

    Original URL path: https://www.limoengroen.nl/en/topics/drupal?page=2 (2016-01-27)
    Open archived version from archive


  • The power of sharing | LimoenGroen
    a project we could fix this locally and continue with our work our problem is resolved However we won t We always make sure that the solution flows back into the community That can be done in several ways Contribute a patch Can we solve the problem Great We create a new issue in the issue queue of the relevant module and deliver the code change as a patch Example of Martijn https www drupal org node 1783678 Describe the problem Are we unable to fix it ourselves Then at least create an issue and describe how the issue can be reproduced This helps another developer to fix this or recognize them their own problem quickly Example of Dominique https www drupal org node 907504 Launch a new module Did we write a separate piece of code that might be interesting for others We ll then try to offer this as a separate project The extra time it takes to make a piece of client code generic and configurable is not an issue knowing that the community as a whole can now help to improve and maintain the code for us Example of myself commissioned by the European Space Agency https www drupal org project commons hashtags Featured Drupal Provider By sharing so much code we became one of the 4 Featured Drupal Providers in the Netherlands Taking equals giving At LimoenGroen Lime Green everyone gets 10 community time every other week our employees have a full Friday to do what they think is important They experiment with new technology write a blog or open source customer code To make sure that the client agrees we add the following boilerplate text to any quote that we write Drupal is developed under an open source software license All in the context

    Original URL path: https://www.limoengroen.nl/en/comment/3 (2016-01-27)
    Open archived version from archive

  • Baris Wanschers | LimoenGroen
    maandag is Blogs by Baris Wanschers 30 Oct 15 Drupal voor Gemeenten Venlo nl De gemeente Venlo heeft LimoenGroen gevraagd om hun nieuwe website te realiseren op basis van de Drupal distributie Drupal voor Gemeenten Samen met ontwerpbureau Freshheads uit Tilburg is de nieuwe website succesvol gerealiseerd Over Drupal voor Gemeenten DvG De DvG distributie is vorig jaar gelanceerd als resultaat van de nieuwe vught nl website Vught de gemeente die is gestart is met read more 11 Aug 15 Een nieuwe website voor VIA Water VIA Water gaf ons de volgende uitdaging realiseer een gebruikersvriendelijk Drupal platform waarin kennisuitwisseling centraal staat Samen met onze partner Puurpxl gingen we deze uitdaging graag aan read more 30 Jun 15 Rijkshuisstijl sprint groot succes Voor de tweede keer organiseerde LimoenGroen een zogenaame code sprint een samenkomst van ontwikkelaars om samen te werken aan Drupal code Deze sprint stond in het teken van het verbeteren van het Drupal Rijkshuisstijl theme dat wij samen met andere bedrijven hebben ontwikkeld en gedeeld hebben met de Drupal community In 2013 organiseerden wij ook al eens een RIjkshuisstijl sprint Daar read more 10 Jun 15 Drupal keert terug in de Brakke Grond Amsterdam 10 juni 2015 De nieuwe website van Vlaams Cultuurhuis De Brakke Grond staat live Samen met onze partner Puurpxl realiseerde LimoenGroen de nieuwe website in het Drupal CMS Het is een bijzonder moment want Drupal keert na tien jaar terug in de Brakke Grond Terug in de tijd Dat Drupal is gekozen als CMS is een niet geheel toevallige keuze Tien jaar geleden in 2005 was De read more 17 Dec 14 LimoenGroen wint Drupal Splash award Vrijdag 12 december werden in Amsterdam de Splash Awards uitgereikt een onderscheiding voor de beste Drupal websites contributies van het jaar LimoenGroen sleepte daarbij de Splash Award

    Original URL path: https://www.limoengroen.nl/en/node/9 (2016-01-27)
    Open archived version from archive

  • Open Source | LimoenGroen
    air where you could also explain power as read more 04 Jul 14 De kracht van het delen Scientia potentia est Francis Bacon 1597 Napoleon won jarenlang keer op keer van zijn tegenstanders ondanks zijn veel kleinere legers Zijn kennis van oorlogsvoering en informatie over de legers van zijn tegenpartij maakten dat hij steeds als winnaar overbleef en zo uiteindelijk Europa wist te domineren Kennis is macht Delen is macht

    Original URL path: https://www.limoengroen.nl/en/topics/open-source (2016-01-27)
    Open archived version from archive

  • Sharing | LimoenGroen
    armies of his opponents made him win the wars every time and ultimately he was able to dominate Europe Knowledge is power Sharing is power The phrase Knowledge is power does not come out of thin air where you could also explain power as read more Blog menu Show navigation Hide navigation Homepage Blog Drupal Give Latest blogs Automatically generated subdomains in Drupal The power of sharing Continuous Integration Drupal

    Original URL path: https://www.limoengroen.nl/en/topics/sharing (2016-01-27)
    Open archived version from archive

  • Knowledge | LimoenGroen
    armies of his opponents made him win the wars every time and ultimately he was able to dominate Europe Knowledge is power Sharing is power The phrase Knowledge is power does not come out of thin air where you could also explain power as read more Blog menu Show navigation Hide navigation Homepage Blog Drupal Give Latest blogs Automatically generated subdomains in Drupal The power of sharing Continuous Integration Drupal

    Original URL path: https://www.limoengroen.nl/en/topics/knowledge (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    the current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering

    Original URL path: https://www.limoengroen.nl/en/comment/6 (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    the current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering

    Original URL path: https://www.limoengroen.nl/en/comment/48 (2016-01-27)
    Open archived version from archive



  •