Linux

1257 readers

46 users here now

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

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Where Do You Guys Throw Your Local Git Repos? (startrek.website)

submitted 1 week ago by data1701d@startrek.website to c/linux@lemmy.ml

62 comments fedilink hide all child comments

Personally, to keep my documents like Inkscape files or LibreOffice documents separate from my code, I add a directory under my home directory called Development. There, I can do git clones to my heart's content

What do you all do?

you are viewing a single comment's thread
view the rest of the comments

[–] foster@lemmy.fosterhangdaan.com 6 points 1 week ago (1 children)

I tend to follow this structure:

Projects
├── personal
│   └── project-name
│       ├── code
│       ├── designs
│       └── wiki
└── work
    └── project-name
        ├── code
        ├── designs
        └── wiki

[–] Ephera@lemmy.ml 1 points 1 week ago (1 children)

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?

[–] foster@lemmy.fosterhangdaan.com 2 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] Ephera@lemmy.ml 2 points 1 week ago (1 children)

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...

[–] foster@lemmy.fosterhangdaan.com 2 points 1 week ago* (last edited 1 week ago)

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.