I’ve just started my Linux journey earlier this year. As a goal to learn how to self-host applications and services that will allow me to take back some control of my data. Immich instead of Google Photos, for example.

I have a local server running Unraid and 22 docker containers now. And then a VPS (Ubuntu 20.04 LTS) running two apps. I’ve learned a ton but one thing I can’t seem to wrap my brain around is navigation through the file structure using only terminal. My crutch has been to open a SFTP session in Cyberduck to the same device I’m SSH’d to and try to figure things out that way. I know enough to change directories, make directories, using Tree to show the file structure at different levels of depth. But I feel like I’m missing some efficient way to find my way to files and folders I need to get to. Or are y’all just memorizing it and know where everything is by now?

I come from a Windows background and even then I sometimes catch myself checking via explorer where a directory is instead of using CMD or PowerShell to find it.

I’d love to hear any tips or tricks!

EDIT: I’ve been using Termius because they have a great Android client, but I wasn’t about to pay $5/mo for sync. Especially to sync to someone else’s cloud. Which led me to Tabby, which I understand has quite a large footprint resource-wise. But I guess I either don’t know enough yet to be mad about it or it hasn’t impacted any of my systems negatively yet. No Android client though, but you can bring your own sync solution and it has a handy little shortcut to SFTP to the current directory you’re in. Between that and stuff like ranger, it’s made it so much easier to learn my way around!

  • tvcvt@lemmy.ml
    1·
    1 year ago

    I think it’s just a matter of getting used to it. I had the same issue at first and the more I used the command line, the more I started to prefer it to GUI apps for certain tasks.

    A couple things that I use all the time:

    • tab completion is incredible
    • cd - goes back to the last directory you were in (useful for bouncing back and forth between locations)
    • !$ means the last argument. So if you ls ~/Downloads and then decide you want to go there, you can cd !$.
    • :h removes the last piece of a path. So I can do vim /etc/network/interfaces and then cd !$:h will take me to /etc/network.
  • DrOps@feddit.de
    0·
    1 year ago

    I did 4 things, that helped me a lot:

    1. Make aliases for the most visited directories

    alias cem=’cd /home/drops/.config/emacs’

    1. Make aliases for moving up the tree tree:

    alias. .=’cd. . && ls’

    Three points for two levels up, etc…

    1. Name all directories lowercase, 3-5 letters long, and try to avoid directories with the same starting letter as siblings That way you can use tab completion with just a single letter

    2. Use the option to jump to subdirectories of /home/user from everywhere.

  • Euphoma@lemmy.mlEnglish
    0·
    1 year ago

    I just type ls everytime I cd into something. It’s not that efficient honestly but I usually remember where I want to go after going there a couple times. Also if you hit tab twice after typing cd and a space, it shows all of the files in the directory.

    • Father_Redbeard@lemmy.mlOP
      0·
      1 year ago

      That’s where I’m at now. And it does work. But I knew there had to be something out in the wild that folks use to traverse or at least understand where they are better. I do like Tree for a more in depth ls though. I don’t recall the options you can throw at the end of tree off the top of my head but you can specify how many layers you want to go down to see a visual of the file structure.

      • Knusper@feddit.de
        0·
        1 year ago

        Problem with most tips and tricks is that they require customizations to the OS. Many people who use Linux in a more advanced fashion, tend to also use lots of different systems, e.g. because they’re a system administrator. And you don’t want to have to make customizations to every system just to be able to get around. So, you learn to work with the lowest common denominator (mostly POSIX commands).

        Many of us do still choose to make some customizations to our most used systems, but yeah, we try to keep it lightweight and mostly just utilize tools that aid in using the POSIX commands, not replace them.