The perfect gun is a flower, beaten by the rough fever of the wind.
A guide from Insomniac's Mike Acton: "Congratulations! You're a lead. Now what? In general, whatever skills you've demonstrated that got you to this point aren't the same things you'll be doing from here on out." ...
The Quiz module is a sophisticated and flexible way to create quizzes in Drupal.
To get started with Quiz, you need to install and enable the 2 core Quiz modules from http://drupal.org/project/quiz:
During our weekly developers meeting I spoke about my approach to contributing to Drupal core, sharing some tips and tricks I've learnt along the way
This is a preview of a proposed session for DrupalSouth Melbourne 2015
In support of my mission to make local development easier and faster, I've released boxes for four of the most popular Linux distributions I use and see used for Drupal sites: CentOS 6/7 and Ubuntu 12.04/14.04.
Originally published at: http://diehardgamefan.com/2014/10/21/tabletop-review-book-of-the-wyrm-werewolf-the-apocalypse-20th-anniversary-edition/
Onyx Path Publishing has come a long way with their Kickstarter efforts. Book of the Wyrm is actually their 11th Kickstarter campaign (The 12th, Deluxe Vampire: The Dark Ages 20th Anniversary Edition is going on now!) and the third for Werewolf: The Apocalypse 20th Anniversary Edition. What makes Book of the Wyrm so interesting is not that the entire book is about the Wyrm, its troops and what it looks to accomplish in bringing about the Apocalypse, but the fact that it came out in October of 2014, three months before the original listed delivery date. This make Book of the Wyrm one of the rare Kickstarter projects to not only come out on time, but beat the delivery date. That’s pretty impressive, and it shows that OPP really has mastered crowdfunding better than any other publisher out there.
Before we get into the Introduction, four chapters and the Appendices, I do want to take a moment to applaud the amazing artwork in this book. Unlike a lot of art we have seen in the 20AE line, the art in Book of the Wyrm is extremely horrific. It’s really well done. I can’t say beautiful, since much of the new art has gore, tentacles and tumours, but it’s really impressive and high quality. At times the art reminds me of something you’d see in Lamentations of the Flame Princess or the old Black Dog label White Wolf used to have for releases like HoL and Clanbook: Tzimisce. This is rather appropriate, as Black Dog Game Factory is actually IN Book of the Wyrm as one of the corporate subsidiaries of Pentex, the main corporate empire of the Wyrm. So the art is not for the faint of heart or young children, but anyone even THINKING of buying Book of the Wyrm is a longtime fan of Werewolf: The Apocalypse and will know that going in to this. Still, just a warning for those of you reading this review who are unfamiliar with the brand. Fantastic art, but very creepy and/or squick-y.
“The Wyrm’s Call” is the Introduction for Book of the Wyrm and right off the bat, you should realize this is not going to be newcomer friendly. It references previous W:tA and W20 releases and makes no attempt to explain mechanics or specific game terminology/jargon. Of course, it shouldn’t have to. It’s clearly a sourcebook, not a core rulebook. You will need W20 in order to make sense of Book of the Wyrm if you’re not already familiar with Werewolf: the Apocalypse, so go read (or preferably purchase) the 20AE already. It’s exceptionally well done, and Book of the Wyrm will make a lot more sense after you flip through the hundreds of pages that will explain the Garou, gifts, and mechanics.
“The Wyrm’s Call” makes it clear that this book is all about the evil, chaotic, psychotic and monstrous nature of the Wyrm. This is not a happy book to read. It’s a book about what how the bad guys of Werewolf: the Apoclaypse think, plan, breed and plot. There are a lot of potential triggers in here, from cannibalism to necrophilia. Child abuse? Rape? Extreme violence and gore? Expect that and more from Book of the Wyrm. That’s why the Introduction pretty much is the equivalent of someone jumping up and down with their arms waving saying, “Hey! Don’t come over here unless you have a cast iron stomach.” The OPP team is perhaps the most PC group of writers and developers in the tabletop industry right now, which means as much as they enjoy tackling the sadistic and horrific nature of the Wyrm in extreme detail, they also don’t want their customers to have traumatic flashbacks to something that might have happened to them, or even feel uncomfortable reading their book. Hence the warnings. So now you’re warned by me too. If you are easily offended, grossed out or have things that can really make you feel uncomfortable, know you’re probably not the target audience for Book of the Wyrm. Also, if you are able to enjoy Book of the Wyrm for what it is and want to use it in your Werewolf: The Apocalypse game, don’t be a dick and throw in bits you know your players will be uncomfortable with by using, “Well it’s canon in this book” as an excuse. Don’t drive people away from our hobby. Anyway, kudos to OPP for include some warnings about the book’s material and for using the Introduction to highlight what each chapter of the book will be about.
Chapter One: Lore of the Wyrm gives you an overview of how the conflict between the Wyrm, Weaver and Wyld began. You see how the Wyrm went insane and became the source of corruption, pollution and chaos in our world. Once there was balance between the Triat. Now there is only war. Like Warhammer 40K, if all the Space Marines were Space Wolves. Anyway, Chapter One not only gives you a look at the history of the conflict, but how the Wyrm itself has broken apart and created a twisted hierarchy within its remnants as well as dark mirror version of the Triat. Yes, the book continually uses Triat instead of Triad. It’s a specific W:TA term, not a repeated misspelling, for those new to the game. You’ll learn about the three core pieces of the Wyrm in its new Triat: Beast-of-War, Eater-of-Souls and the Defiler. There’s also a long list of Urge Wyrms (Negative Emotions) and their Avatars, the four Elemental Wyrms (Smog, Toxin, Sludge and Balefire) and how the Wyrm interacts with the Spirit Realm of the Umbra. The chapter ends with an extremely long in-depth look at the pemi-plane of Malfeas, which is the realm which the Wyrm calls home. It’s eleven pages of pure description, showcasing different duchies the land is divided into, along with showcasing how extremely messed up Malfeas is. Definitely worth reading, and it will really give you a great idea of how the Wyrm is actually quite orderly in its chaos and corruption. Well done.
“Chapter Two: Pawns and Puppets” is exactly what you expect it to be. Here you get a look at the corporations, factions, allies, servants and unwitting dupes of the Wyrm. This chapter primarily focuses on Pentex, which is perhaps the most common way that PCs encounter the Wyrm in a game of W:TA. You get a look at Pentex’s structure, how it weathered the recent economic downturn, a whole list of subsidiaries and crazy products they put out and, of course, the people that run the corporation. It’s a fascinating and fun look, because Pentex has always been where OPP (and White Wolf before them) have let their imaginations run wild with dark satiric material. There are looks at the Occupy effort and how the Wyrm corrupted that, how Pentex influences video games, movies, fast food, and even the World of Darkness’ version of Anonymous. Perhaps the most entertaining part is the entry for Black Dog, where OPP mocks its own product line as well as the entire tabletop industry as a whole. World of Darkness products aren’t usually known for being laugh out loud funny, but you’ll definitely do so here. However, once the mirth has died down, you realize what a source of horror and pure eeeeevil (Indeed!) these bits of comedy relief can be when taken seriously in the actual game world. Still, it’s nice to see that the OGL of the 3.0 era is given a wonderful send-up as pure malevolence here.
Besides Black Dog, you’ll also see companies like Endron Oil, Magadon Pharmaceuticals and Sunburst Computers. Really though, a lot of readers, especially Kickstarter backers, will be reading this chapter for a look at the Board of Directors. Part of the crowd funding effort involves nominating and voting for new board members, and here you get to see the result. You’ll learn about the core board members and the specific machinations and goals they have in place. Each one is a work of art, if you consider art a toxic waste dump where your soul once used to reside. Truly, it is a lot of fun to see the Board of Directors given names, backgrounds and history. It helps a Storyteller make better use of them, as well as let them come to life in his or her Chronicle. The look at the new board members and the entire election process is a lot of fun too. More than any other book in the 20AE line for the Classic World of Darkness, you can really see and feel how much fun the authors had putting the Book of the Wyrm together.
Of course, the chapter isn’t ALL Pentex. You also get a list of cults devoted to the Wyrm, along with who is in them and what their particular goals are. These cults range from a twisted take on P.E.T.A. to a small town’s city council. Everything in this chapter highlights how diverse and cutting edge the Wyrm is compared to the Garou, which are small in number and are often more anachronistic than some ancient Kindred. By the time you are done chapter two, you really do see how the odds are overwhelmingly in favor of the Garou losing. It might fill you with a bit of sadness and hopelessness… which is exactly what the Wyrm wants you to feel.
“Chapter Three: The Never-Ending Dance” is all about the Black Spiral Dancers. You might want to read this chapter in conjunction with Clanbook: White Howlers just so you can see the complete history of the Wyrm’s werewolves and how they turned into the servants of corruption that they once fought so valiantly against. You see firsthand why the White Howlers went down into the Black Spiral, how they changed and why they now serve the Wyrm willingly. You see the war from the Black Spiral Dancers’ perspective and how they’ve already won. They’re just trying to prove to the Garou (which they really hate) that the war has been over for a long time and that they just refuse to accept their crushing defeat. It’s an interesting read, and it really lets you see the perverse mindset of a tribe that lies to themselves constantly in order to keep the tiniest bit of sanity that still remains within them.
You’ll get a look at the BSD’s twisted version of the Garou litany, see how the tribe treats and raises its Kinfolk and even how packs are organized. There are lists of dens and specific BSD’s of note that you can throw into your Chronicle if you are an enterprising sort of Storyteller. Perhaps most interesting is the section that shows what the Black Spiral Dancers think of each specific tribe – who is the most dangerous, the most easy to corrupt, their greatest enemies and what they feel to be each group’s weaknesses. Even better, there is a piece showcasing how the BSD and Wyrm corrupt Garou from each tribe to get them to fall and dance the Spiral themselves. Great stuff. The chapter concludes with lists of Gifts, Rites and Totems specific to the Black Spiral Dancers.
“Chapter Four: Feeling the Touch” covers everything else. As it takes up a fourth of the book with fifty-plus pages of content and art, you might find this is where you will spend most of your time when using Book of the Wyrm in an actual game. Within this chapter you’ll get a good long look at various breed of Fomori, and even what happens when they try to possess supernatural creatures like vampires, Garou, mages and Changelings. There is also a section on Banes and another on truly bizarre Wyrm spawnings. Perhaps the most interesting section in this chapter are what happens when other Changing Breeds such as Wererats, Werespiders, Weresharks and the like fall to the Wyrm and become its servants. Each Changing Breed gets several pages devoted to their Wyrm counterpart, and each one is extremely twisted. There are also several “Mockery Breeds” which are Pentex’s scientific experiment attempts to create its own wereanimals. There are the War Wolves, Anurana (toads), Samsa (Cockroaches that are all but impossible to kill but also terrified of everything and extremely paranoid) Kersai (Rhinos) and Yeren (great white apes). Each tribe is as screwed up as you can imagine, but the Samsa and Anurana seem like they can be potential converts to Gaia. Perhaps in your campaign they will!
Besides all these potential antagonists and cannon fodder, the chapter ends with a small section on Taints. How one becomes Tainted, the difference between physical and mental Taints, along with information on the Path of Corruption. It’s worth noting that this chapter ends with “Redemption for the Corrupted,” which means the book itself ends with a light at the end of a long tunnel of darkness. It’s this same little gasp of hope that will lead the reader to believe the Wyrm is not as all-powerful and unstoppable as it (and this book) would like to believe, as well as mirrors that bit of hope that keeps the Garou fighting for Gaia, even in the face of certain defeat. Perhaps this wasn’t intentional, but the critic in me likes the analogous poetry in it.
The last few pages of the book are the Appendix. Entitled, “Rotten Baubles,” this is a potpourri of various odds and ends. Fetishes and Equipment? It’s here. Some example Tainted products, like Lycanthrope: The Rapture 17th Anniversary Edition? It’s in here. Some Tainted alcohol or especially evil vehicles? Here you go. After that, it’s THIRTEEN PAGES of Kickstarter backer thank yous and the book is done. Huzzah!
So there you go. Book of the Wyrm is easily the best release for W20 besides the core rulebook so far, and it’s also the best release by Onyx Path Publishing this year. I loved nearly every page of the book and was thoroughly impressed by the time I was done with it. If you’re a fan of Werewolf: The Apocalypse or the Classic World of Darkness in general, this is a definite must-buy when it becomes available to the general public. It’s fantastic.
Description available on GitHub: http://github.com/farmier/farm_livestock
Will be moved here soon.
After a very successful drush code-sprint at BADCamp 2014, drush make now supports YAML format!
Instead of the old INI formatapi = 2 ; Set contrib directory. defaults[projects][subdir] = "contrib" core = "7.x" projects[drupal][type] = "core" projects[drupal][version] = "7.32" ; Remove scary ajax error when autocomplete terminates: https://www.drupal.org/node/1232416#comment-8748879 projects[drupal][patch] = "https://www.drupal.org/files/issues/D7-fix_autocomplete_terminated_error-1232416-179-do-not-test.patch" ; Ensure plain text fields evaluate line breaks. projects[drupal][patch] = "http://drupal.org/files/text-plain-1152216-24.patch" projects[addressfield][version] = "1.0-beta5" projects[addressfield_tokens][version] = "1.4" projects[admin_views][version] = "1.3" projects[field_collection][version] = "1.0-beta7" ; Field collections are ownerless https://drupal.org/node/1954124 projects[field_collection][patch] = "https://drupal.org/files/issues/field_collection-ownerless_fields-1954124-23.patch" ; Fixes fatal error in migrate code: https://www.drupal.org/node/2315921#comment-9028779 projects[field_collection][patch] = "https://www.drupal.org/files/issues/migrate-fatal-error-2315921-01.patch"
YAML can be used with the latest version of Drush 7:api: 2 # Set contrib directory. defaults: projects: subdir: "contrib" core: "7.x" projects: drupal: type: "core" version: "7.33" patch: # Remove scary ajax error when autocomplete terminates: https://www.drupal.org/node/1232416#comment-8748879 - "https://www.drupal.org/files/issues/D7-fix_autocomplete_terminated_error-1232416-179-do-not-test.patch" # Ensure plain text fields evaluate line breaks. - "http://drupal.org/files/text-plain-1152216-24.patch" addressfield: "1.0-beta5" addressfield_tokens: "1.4" admin_views: "1.3" field_collection: version: "1.0-beta7" patch: # Field collections are ownerless https://drupal.org/node/1954124 - "https://drupal.org/files/issues/field_collection-ownerless_fields-1954124-23.patch" # Fixes fatal error in migrate code: https://www.drupal.org/node/2315921#comment-9028779 - "https://www.drupal.org/files/issues/migrate-fatal-error-2315921-01.patch"
Included .make files whether local, or discovered recursively within downloaded projects, can be in either YAML of INI format.
In order to use the newly-supported YAML format, simply name files with a .yml extension, such as my_project.make.yml.
The best part? This can be used now! Even though YAML files are mostly a new concept for Drupal 8, drush make will parse YAML make files for Drupal 7, and even Drupal 6. Want to learn more about DRUSH make files? Check out Joe Turgeon’s “Getting Started With Grunt Drupal Tasks“
In the spirit of the computer video game Doom and its skill levels, we’ll review a few ways you can improve your Drupal speed performance and optimize for better results and server response time. These tips that we’ll cover may be at times specific to Drupal 6 versions, although you can always learn the best practices from these examples and apply them on your own code base.
Doom skill levels: (easiest first)
1. I’m too young to die
2. Hey, not too rough
3. Hurt me plenty
This post is rated “I’m too young too die” difficulty level.
If you’re using a Drupal distribution which is great for kick-starting a project with many features built-in, you should still review added modules which are managed through the installation profile as they might prove un-necessary for your product as time goes and your product evolves and matures. Remember that even if you’re not using a distribution, you might have added some modules to meet a functionality, which you no longer use and you disabled through CSS, through the menus, through the theme, but you forgot all about removing the actual module. These un-used modules account for memory footprint as they are loaded through PHP and they can also account for Drupal hooks, which is even worse in terms of performance for you.
Remember to review your installed modules base on Drupal and remove any un-used functionality:
One of the best ways to learn useful tricks at the command line is to sit with someone and watch what they do. Due to the distributed nature of the Drupal community, we don't do nearly enough pair programming. Too often we work in isolation and then push our work on others when we finish. In this article I invite you to sit down beside me and watch over my shoulder as I explore Drupal 8 from the command line.Navigating Drupal in the Bash Shell
The instructions in this article will work for OSX, and Linux systems, such as Ubuntu, but not Windows.
When reading command line instructions, there are two important characters we need to know about: $ and #. When applied to the beginning of a line, these refer to the prompt. We don't type these characters when issuing our command. $ signifies the command should be run as a regular user; # signifies the command is run as the administrative user (“root”).
As a themer, the first thing I want to explore is, of course, the themes. Let's begin by navigating to our Drupal folder. I start by opening up a terminal application. At the command line, I type cd, and then, using Finder, locate my Drupal folder. I then drag this folder onto the terminal application. It will automatically paste the path to the Drupal folder into my bash prompt. I press return, and bingo – we have navigated to the Drupal folder!
Let's take a peek inside the core folder of themes: we’ll navigate to the folder core/themes and then list (or ls) all files.$ cd core/themes $ ls
There should be four things listed. See them all?
I've had a couple of questions related to Association finances lately in various communications channels. I know that most of you are not finance professionals for a living, so rather than answering in several different silos, I thought I might write up this post about how the Association financials are structured and how you can read them. You know, for when you need a break from your other Drupal work! So if you're into this sort of thing (and I am not judging here, because I am WAY INTO this sort of thing), read on!What are financial statements?
A financial statement is a formal record of the financial activities of the Drupal Association. The financial statements present information in a structured way that should make it easy to understand what is happening with the organization's finances. In other words, financial statements should tell a story about what is happening with the Association's money. Generally, financial statements include three standard reports:
- Income Statement (or Profit & Loss): This report shows the revenue that is recognized as received and spent during a given period. It is tempting to compare the income statement to your checkbook register, but it's not quite that simple. The catch is that the income statement shows RECOGNIZED income and expense. One of the US accounting rules, for example, is that we can not recognize revenue for a DrupalCon ticket until the month in which the event happens. So, if you buy your DrupalCon Barcelona ticket in June, and the event is in September, your ticket revenue will not show up until our September income statement. Until then, that revenue sits on our Balance Sheet. So, the income statement alone does not give you a full picture of the organiztion's financial position. It simply represents the movement of recognized revenue in a specific time period. The income statement also represents some non-cash changes, such as depreciation.
- Balance Sheet: The balance sheet shows us the assets and liabilities for the organization for that given time period. Reading the balance sheet, you can get a better understanding of how much money is in the bank, and where we owe, or might possibly owe, money. These things are not reflected in the income statement. Going back to our DrupalCon Barcelona example, prior to the Con, any revenue from sponsorship, ticket sales, or training sales would be held on the balance sheet in two ways. First, it will simply be reflected as cash in our bank account. Secondly, it is reflected as a liability, broken out specifically as sponsorship or ticket revenue. It's a liability because if we cancel the Con, we have to give you your money back! When preparing the September financials, we move the ticket revenue from the balance sheet liabilities session to the Income Statement, where it is treated as recognized revenue.
- Cash Summary: The cash summary (or cash flow) is the report that simply shows the movement of money into and out of our accounts. It does not account for depreciation or other non-cash accounting.
Those three reports are the standard set that organizations issue when reporting their financials. The Association, however, issues additional reports to add clarity and transparency around the programs that you care most about.About the Drupal Association Financial Statements
The Drupal Association financials are created on a monthly basis, and then are reviewed by the Finance Comittee of the board. On a quarterly basis, the Finance Committee presents the financials to the Board in executive session, which, if there are no serious questions, approves the financials. At that point, we publish the three months of financials to the community. They are promoted in a blog post about the meeting, and are also always available on the board materials page on the Association site.
As I mentioned above, the Association financial statements go above and beyond the standard reports. In addition to the main three, our monthly financials also include the following:
- "PL All Classes:" This is an income statement report, showing recognized revenue and expenses for the month, but it is broken out by program area. This gives you the opportunity to see, for that month, the recognized revenue and expense for the upcoming Cons, or Drupal.org, or our Drupal Product Marketing efforts, for example. This report is for the month only, so keep that in mind. If you are looking at the May financial statements, the numbers in this report are for May only.
- "Revenue:" This report was designed to show how our various revenue lines are performing. One of our board mandates is to diversify revenue so that DrupalCons are not our primary source of income. Taking this pressure off the Cons to perform financially will allow us to make different kinds of choices for the Cons, and it provides us more stability as an organization. This report helps us monitor progress for those revenue lines.
- "PL DC ConName:" We create one of these report for each of the Cons we are working on. They are income statements for those Cons, year to date (YTD). YTD means that the report reflects all income and expense for that year, not just the current month. In these reports, you can see detailed information about expenses, with revenue generally not recognized on the report until the month of the Con.
And, keep in mind that all Association financial statements are reported in US Dollars.How to Read the Financial Statements
A goal of financial statements is that they are supposed to make financial information easier to understand. However, the truth is that it is difficult for mere mortals to read financial statements. It takes both training and practice. However, let's see if I can walk you through some details. I'll use the March 2014 financial statements in this example.Income Statement
The Income Statement presents the income and expenses for both the month of the report (in this case, March) as well as the year to date, or YTD, amounts (in this case, 1 January through 31 March 2014). So the top of the report looks like this:
Here's what what the columns represent:
- Actual: Amounts for the month the financials report represents. In this case, March 2014.
- Budget: The budgeted amount for the month the financial report represents. In this case, the amount we budgeted for March 2014.
- YTD Actual: Total amount for the year, through the month the financial report represents. In this case, 1 January through 31 March 2014.
- YTD Budget: Total budgeted amount for the year, through the month the financial report represents. In this case, the amount we budgeted for 1 January through 31 March 2014.
- Var %: The percent difference between the YTD Actual and YTD Budget. This gives you a sense of how good a job we did at budgeting. Variance can occur because we receieved or spent money faster than we anticipated, or our models were off entirely. Remember that the Association only began budgeting and reporting in these formats 18 months ago, so we're still learning about what our cycles of revenue and expense are, so we expect the variance to decrease overall throughout the next few years as we get better at this.
The Balance Sheet presents the assets and liabilities as of the month of the report, which is March 2014 in this example. The balance sheet almost always also shows a comparative period - the same period the year prior, which is March 2013 for this example. This gives you the opportunity to see how things have changed in the last year. The report looks like this:Cash Summary
The Cash Summary report shows the flow of money into and out of the organization in the given period. For compartive purposes, it also includes a Year to Date (YTD) column that shows all cash movement for the year, which is 1 January through 31 March in this example. The Cash Summary looks like this:What our Financial Statements do not show
Simply put, our financial statements do not show a lot of information. The point of statements is to take complex and copious amounts of data and distill it into something digestable. We do not, for example, show each of the tickets sold for a DrupalCon and who they were sold to. We don't show each invoice that was received for Association software as a service subscriptions. We have the data, and I'm not oppposed to sharing it (as long as I check that we are not violating any privacy or other laws - you never know). However, it does not make sense for us to publish this level of detail on a monthly basis.
That said, if there is something our financial statements do not show you, you can always ask. If it's not published here, it's not because we don't want to share the information. It's because we want to share information that can be meaningfully understood.Summary
That should help you get through some of our financial statements a little better. I am not an accountant, but I am always happy to field any questions you have about these documents, and our amazing Operation Team of Kris and Leslie love to help. Just drop me a line via email or go ahead and post in a public channel like Twitter or a forum. Give me a heads up and I will get back to you.
Flickr photo: Doug88888
Storm8 game design chief Dan Scheidegger is coming to GDC 2015 to run down exactly what worked -- and what didn't -- during development of Restaurant Story 2. ...
I was recently working on a Drupal project that had some internal DNS managed via hosts file. Tell me about it. Having no publicly accessible DNS or IP creates a challenge when your SaaS based Jenkins runs the tests.
The solution for this is a little custom work in your FeatureContext constructor and a BeforeScenario method.
And a little glue in the behat.yml to pass the custom hostHeader variable to the FeatureContext. Make sure that you're also setting the IP of the server for base_url and you're all set.
You can use this same pattern to pass around other variables from behat.yml to your FeatureContext.Tags:
From your local machine ..
1. Create your keysssh-keygen -t rsa
2. Upload to your serverscp ~/.ssh/paulbooker.pub firstname.lastname@example.org:/tmp/paulbooker.pub
From your server ..
1. Install Gitolite.apt-get install gitolite
2. Create a user for Gitolite.adduser \ --system \ --shell /bin/bash \ --gecos 'git version control' \ --group \ --disabled-password \ --home /home/gitolite \ gitolite Adding system user `gitolite' (UID 103) ... Adding new group `gitolite' (GID 105) ... Adding new user `gitolite' (UID 103) with group `gitolite' ... Creating home directory `/home/gitolite' ...
3. Setup Gitolitesu - gitolite gl-setup /tmp/paulbooker.pub The default settings in the rc file (/home/gitolite/.gitolite.rc) are fine for most people but if you wish to make any changes, you can do so now. hit enter... /usr/bin/select-editor: 1: /usr/bin/select-editor: gettext: not found 'select-editor'. /usr/bin/select-editor: 1: /usr/bin/select-editor: gettext: not found 1. /bin/nano <---- 2. /usr/bin/emacs23 3. /usr/bin/vim.tiny /usr/bin/select-editor: 1: /usr/bin/select-editor: gettext: not found 1-3 : 1 creating gitolite-admin... Initialized empty Git repository in /home/gitolite/repositories/gitolite-admin.git/ creating testing... Initialized empty Git repository in /home/gitolite/repositories/testing.git/ [master (root-commit) 7e358c3] start 2 files changed, 6 insertions(+) create mode 100644 conf/gitolite.conf create mode 100644 keydir/paulbooker.pub
4. Add the Gitolite user to your SSH configuration file.nano /etc/ssh/sshd_config PermitRootLogin yes #without-password PasswordAuthentication no AllowUsers root gitolite #no commas service ssh reload # /etc/init.d/ssh reload .. Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service ssh reload
On your local machine.nano ~/.ssh/config Host Git user git hostname 126.96.36.199 port 22 identityfile ~/.ssh/git Host * user paul hostname * port 22 identityfile ~/.ssh/paulbooker
1. Clone your gitolite repository
$ git clone email@example.com:gitolite-adminCloning into 'gitolite-admin'... remote: Counting objects: 6, done. remote: Compressing objects: 100% (4/4), done. remote: Total 6 (delta 0), reused 0 (delta 0) Receiving objects: 100% (6/6), done.
2. Add a test repositorycd gitolite-admin vi conf/gitolite.conf git commit -a -m "Add a test repository" [master ee674e9] Add a test repository 1 file changed, 3 insertions(+) git push Counting objects: 7, done. Delta compression using up to 2 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (4/4), 399 bytes, done. Total 4 (delta 0), reused 0 (delta 0) remote: creating test... remote: Initialized empty Git repository in /home/gitolite/repositories/test.git/
7e358c3..ee674e9 master -> master
3. Clone the test repository.git clone firstname.lastname@example.org:test Cloning into 'test'... warning: You appear to have cloned an empty repository. cd test echo "test" > README git add . git commit -m "Initial commit" [master (root-commit) 21e352e] Initial commit 1 file changed, 1 insertion(+) create mode 100644 README git push origin master Counting objects: 3, done. Writing objects: 100% (3/3), 224 bytes, done. Total 3 (delta 0), reused 0 (delta 0) To email@example.com:test * [new branch] master -> master
4. Add committer to the repository.
Add public key to the gitolite-admin key directory and edit the gitolite configuration file gitolite.confrepo gitolite-admin RW+ = git repo testing RW+ = @all repo repo1 RW+ = git = paulbooker paul$ git add -A Paul-Bookers-Mac-mini:Git paul$ git commit -m "Updated configuration" [master 511d9af] Updated configuration 2 files changed, 5 insertions(+) create mode 100644 keydir/paulbooker.pub Paul-Bookers-Mac-mini:Git paul$ git push Counting objects: 10, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (6/6), 1012 bytes, done. Total 6 (delta 0), reused 0 (delta 0) remote: creating repo1... remote: Initialized empty Git repository in /home/git/repositories/repo1.git/ To firstname.lastname@example.org:gitolite-admin 05c16f3..511d9af master -> master 5. Commit and push changes to the server. git commit -m "Initial commit to repo1" git remote add origin email@example.com:repo1.git git push origin master Tags: Tweet
In my last post we went over the new Drupal 8 plugin system as it concerns blocks. Today, we're going to take this idea a bit further and create a simple next/previous navigation.
First thing's first, you're going to want to create another new file at modules/YOURMODULE/src/Plugin/Block/YOURBLOCKNAME.php
In my case, this file looks like this:
There is a saying that "All good things come to those who wait".
Ukrainian Drupal community with an active support of InternetDevels team has actually invented completely unique kind of Drupal event, which makes the whole community go wow! So, ladies and gentlemen, we proudly present you Drupal Tour! The main point of the event is in it’s dynamics and velocity — we’re not going to stop just on one location, but would travel all around the country to involve even larger amount of audience, interested in Drupal development.Read more