How to clean up local git branches matching a name

Jérémie Veillet — 

If you are like me, and you are in an project using git, you probably create or use a LOT of branches. There can be times when it’s hard to keep track of all of them and they pile up in your project’s folder until you see 100 of them. A word of caution: Deleting branches is a definitive act, you cannot go back, especially if the branches hadn’t been pushed to some kind of remote repository (e.g Github, BitBucket, etc..). Navigate through your project and list the branches, you probably already know that * represent your current default branch: $ cd myProject $ git branch Another_thing_to_do_aside Fix_another_fix Fix_some_kind_of_task Fix_urgent_task_to_change JIRA-10_End_task_yes_the_real JIRA-1_One_task JIRA-2_Another_task JIRA-3_Task_3 JIRA-4_TEST_task JIRA-5_Great_Task JIRA-6_No_task JIRA-7_Foo_task JIRA-8_Bar_Task JIRA-9_Bazz_task * master As you can see, you could have a whole bunch of branches of every name. Now, git gives you the possibility of listing the branches that has been...

Read more...

Introducing first draft of the Styleguide

Jérémie Veillet — 

A new section is up in the Menu: The Styleduide! A Styleguide to rule them all When you work in a team, it’s always great to have a common place to share the visual aspect and design of a project. The difficulty here is getting a common resource for all the visual elements of the website, and provide guidance on how to implement them, so that everything looks consistent on every page, without sacrificing people creativity. It should help implementing modularity, so that updating a component does not cause a shitstorm in your application. There is a lot of techniques and methodologies this days to help you achieve that goal, to name a few BEM, ITCSS, OOCSS, SMACSS, you can also read the great Brad Frost’s blog about Atomic Design, which was a great inspiration. How ? Demain·il·pleut has been build around that philosophy. I designed everything in the browser,...

Read more...

Dealing with the MongoDB error /data/db not found in OSX

Jérémie Veillet — 

Disclaimer if you landed somehow on this article, you have probably miss something in the install process of MongoDB. What the.. ? When trying to launch mongodb in your Terminal, I guess you have met with this kind of error message: $ mac:app jeremie$ mongod 2015-10-09T12:06:37.396+0200 I STORAGE [initandlisten] exception in initAndListen: 29 Data directory /data/db not found., terminating Basically, the output is pretty clear, you do not have the data directory, and its db subdirectory created in your root folder, which are essential to run the mongodb instance. So let’s go ahead and fix that, and create that directory. $ mkdir -p /data/db If you try to launch the mongod command again after that, it will fail with something like the above: $ mac:app jeremie$ mongod 2015-10-09T12:10:17.370+0200 I STORAGE [initandlisten] exception in initAndListen: 98 Unable to create/open lock file: /data/db/mongod.lock errno:13 Permission denied Is a mongod instance already running?,...

Read more...

Enabling any text editor with git

Jérémie Veillet — 

I’m joining the party a little late, but I’ve started working with git and GitHub, both for this website, and coincidently at work for my current project.This is a quick article about using your favorite editor to write your commit messages. State of the art If you happen to work with git (if not, you should download and it and play with it, it’s marvellous), you probably need to enter a commit message at some point. When you first setup your environment, no default editor is configured (on OSX, if git is installed with XCode, it might use vim as the default editor). Checking out what is configured, it is as easy as invoking this line in the Terminal: $ git config core.editor vim Chances are, you will get an empty line as nothing is probably set. Change the editor Let’s say you want to use SublimeText 3. This software...

Read more...

A new day

Jérémie Veillet — 

Hello and welcome for the grand opening! You are probably here out of hazard, but that’s totally fine. This is a big step for me, it has been two years since I’ve started to build this website, and I have been postponing over and over the launch. Something was always not ready, not perfect, I found many excuses and never released anything. My goal was to start an english speaking blog and talk about everything code or design related, that I found on my day to day job or my personal researches, as a developer. Sharing what I’ve learned may not be useful for everyone, but I do it in hope it helps at least one person (starting with me). There is still a lot of work to do, I tried to focus on a very simple and light layout, no ads, no social networks buttons, no comments, everything here...

Read more...