Ask HN: How do you organise your codebase on your private machine?
1–7 of 7 posts
Re: Ask HN: How do you organise your codebase on your private machine?
#2Re: Ask HN: How do you organise your codebase on your private machine?
#3Edit: for anyone who doesn't quite read shell expansion, it looks like this:
~
+ Projects
+ My Company Name
+ Clients
+ Client 1
+ Project Foo
+ Client 2
+ Project Bar
+ Internal
+ Project BazRe: Ask HN: How do you organise your codebase on your private machine?
#4~/Projects/$MyCoName/{Clients/$ClientName,Internal}/$ProjectName Edit: for anyone who doesn't quite read shell expansion, it looks like this: ~ + Projects + My Company Name + Clients + Client 1 + Project Foo + Client 2 + Project Bar + Internal + Project Baz
Re: Ask HN: How do you organise your codebase on your private machine?
#5Re: Ask HN: How do you organise your codebase on your private machine?
#6~/Projects/$MyCoName/{Clients/$ClientName,Internal}/$ProjectName Edit: for anyone who doesn't quite read shell expansion, it looks like this: ~ + Projects + My Company Name + Clients + Client 1 + Project Foo + Client 2 + Project Bar + Internal + Project Baz
Yea I do something similar. I like the {$ClientName, Internal} though. I had issues with that before.
FYI the {} is shell expansion braces (which split on the comma), I've edited my comment with a literal tree of how it looks
Edit dos: and I see that you probably knew that!
Re: Ask HN: How do you organise your codebase on your private machine?
#7Earlier quoted context omitted.
Yea I do something similar. I like the {$ClientName, Internal} though. I had issues with that before.
What issues did you have? FYI the {} is shell expansion braces (which split on the comma), I've edited my comment with a literal tree of how it looks Edit dos: and I see that you probably knew that!