~/git
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
~/dev/
, with project/org subdirectories
Admittedly, that irks me slightly just because of the shared name with the devices folder in root, but do what works for you.
I actually have my whole home directory like that for that reason haha
bin - executables
dev - development, git projects
doc - documents
etc - symlinks to all the local user configs
med - pictures, music, videos
mnt - usb/sd mountpoints
nfs - nfs mountpoints
smb - smb mountpoints
src - external source code
tmp - desktop
This is pure insanity. Chaos.
Same. Short and sweet.
~/src/
Simple, effective, doesn't make my home folder any more of a mess than I already left it as.
Like others, I have a folder in my home directory called "Code." Most operating systems encourage you to organize digital files by category (documents, photos, music, videos). Anything that doesn't fit into those categories gets its own new directory. This is especially important for me, as all my folders except Code are synced to NextCloud.
~/Projects
~/git/vendor//
and
~/git////
Examples:
~/git/vendor/EnigmaCurry/d.rymcg.tech
~/git/mike/forgejo/mikew/myproject
~/git/mike/github/johndoe/otherProject
~/projects
for things I made
~/git
for things other people made
Same, but by language, e.g. Development/Python
.
What if a project uses multiple languages?
Symlink each individual file, obviously.
Me waiting for tagging filesystems to become the standard
Thinking of the projects I work on, I don't understand the value in categorizing by language, rather than theme (~/Development/Web/
, ~/Development/Games/
) or just the project folders right there.
Yeah, everyone has to find their own way of organising, I guess. For me, there are too many different little projects that it would get messy throwing them all in one folder. And they’re so varied that I couldn’t think of one single “theme” or topic for most of them. Nothing I would remember a week later anyways.
I tend to follow this structure:
Projects
├── personal
│ └── project-name
│ ├── code
│ ├── designs
│ └── wiki
└── work
└── project-name
├── code
├── designs
└── wiki
Is "code", "designs" and "wiki" here just some example files in the repo or are those sub-folders, and you only have the repo underneath code
?
They are the project's subfolders (outside of the Git repo):
code
contains the source code; version-controlled with Git.wiki
contains documentation and also version-controlled.designs
contains GIMP, Inkscape or Krita save files.
This structure works for me since software projects involve more things than just the code, and you can add more subfolders according to your liking such as notes
, pkgbuild
(for Arch Linux), or releases
.
Ah, interesting. In my current setup, I dump the auxilliary files into a folder above the repo, but it can certainly make it a bit messy to find the repo in there then...
I maintain a rule that all files above the repo must be inside a folder, with one exception: a README file. Including the code
folder, this typically results in no more than 5 folders; the project folder itself is kept organized and uncluttered.
Most of my code and some non-code is under ~/src
, but I have repos scattered all around for other things.
~/Projects/$TOPIC_OR_LANGUAGE/$PROJECT_NAME
ie.
~/Projects/Web/passport.ink
for a web dev project~/Projects/Minecraft/synthetic_ascension
for a Minecraft mod~/Projects/C++/journalpp
for a C++ library
~/git, for projects I cloned from the web because I don't know how to code :(
${HOME}/repos
~/repo for code I write and ~/src for code I didnt.
~/code/git//
Mostly a holdover from when I regularly pulled svn
/hg
/cvs
repos and needed reminding what tool to use for which project.
No idea why I still do it.
~/Git
~/workspace/git
That way I can also keep other stuff in the same "workspace" directory and keep everything else clean
I have a Code, simulations, ECAD, and FreeCAD folder in the workspace folder where projects or 1-offs are stored and when I want to bring them to git, I copy them over, play around in the project folders again, then copy changes over when I am ready to commit.
I could better use branching and checking out in git, but large mechanical assemblies work badly on git.
/dev/null
~/code
for everything I want to change/look at the source code.
~/.local/src
for stuff I want to install locally from source.
I used to use ~/dev
but for years now I use ~/Workspace
becaue Eclipse made me do it
Same here!
Usually ~/devel/
On my work laptop I have separate subdirs for each project and basically try to mirror the Gitlab group/project structure because some fucktards like to split every project into 20 repos.
~/Code
for coding/dev stuff and ~/gitclone
for things that i random clone for some reason. =D
For a project called "Potato Peeler", I'll put it into a structure like this:
~/Projects/Tools/Potato-Peeler/potato-peeler/
Tools/
is just a rough category. Other categories are, for example, Games/
and Music/
, because I also do gamedev and composing occasionally.
Then the capitalized Potato-Peeler/
folder, that's for me to drop in all kinds of project-related files, which I don't want to check into the repo.
And the lower-case potato-peeler/
folder is the repo then. Seeing other people's structures, maybe I'll rename that folder to repo/
, and if I have multiple relevant repos for the Project, then make it repo-something
.
I also have a folder like ~/Projects/Tools/zzz/
where I'll move dormant projects. The "zzz" sorts nicely to the bottom of the list.
~/code/$LANGUAGE/$REPONAME
~/.projects
Similar, but I’m not ashamed of having my projects on display, so it’s just ~/projects
for me.
C:\repos
or ~/repos
Personal?
~
My homedir is a HUGE MESS.
Work?
~/src///
i.e. ~/src/github/mirantis/docker (not real I don't imagine, just an example)
~/src/bitbucket/INTERNALPROJECTCODE/coolrepo
~/projs
I like ~/w or ~/p options
~/Sources for stuff I'm only building from sources and no immediate intention to contribute to
~/Projects for stuff I'm involved in, with a following structure:
Projects
- Personal
- - Art
- - Music
- - Code
- - - Ideas
- - - In progress
- - - Deployed
- - - Scripts
- - - Abandoned
- [Company name]
- - [Project name]
- Interviews
- - [Company name]
The last part grouping project by companies has worked great for me, especially with freelance and outsource work. Sorting personal projects into types and stages feels like a mistake, as every time I have to navigate it, I can't help but think of limitations of hierarchical file systems, as some of them are multiple types simultaneously, and also moving projects between stages feels dumb.
In ~/src Mostly because I'm too lazy to type "source".
/mnt/shared/Development or E:\Development depending on which operating system is running.
Not in home mainly because I use the same directory in windows and Linux.
Putting one directly under the home directory feels like a psychopathic move, so I stay by XDG and put them under a subdirectory of xdg-documents