How to be productive in linux shell?

I gave those articles a (very) quick read, but how do I actually get my code and whatnot? Exclude it from docker and pull it from GitHub whenever I'm on a new machine? Or keep it together with my docker image? Also, what are the limitations of this approach?

This is autistic and the opposite of productive.

You'd literally need to know the ins and out of every application before you can wrap it successfully, or go through dozens of trial and error cycles where the application just fails.

If your set of tools never changes and grows then you might be fine, but noone using 10 year old tools is going to be considered productive.

Also if you need to re-construct a system, you literally just need to copy data directories (/home/ and whatever else you care to keep around), generate a diff of your /etc directory, and apt-mark showmanual > packages.txt to be restored on the clone system by apt install $(cat packages.txt).

If you need to ditch all of your application settings regularly for whatever reason, then you can start giving a fuck about the state of your home directory and cherry-picking files to preserve.

>And all your colleagues (if you have some) will literally be in awe in front of your workflow.
Right, earlier this week, I awed someone with little more than talking about what someone who can into text editing (like him) might do to efficiently duplicate a line in a typical editor, from a starting position somewhere near the middle of the line (e.g., home, shift-end, ctrl-c, end, return, ctrl-v) - followed by demonstrating yyp in Vim.

In most text editors you can just Ctrl+C then Ctrl+V from anywhere on the line. Just sayin

Anyone who has used a computer for a significant amount of time will be able to execute that combination of keystrokes in about a second, and its transferable across all applications.

It'll take the special snowflake vimfag longer on average to remember the unintuitive and arcane sequence of keys to achieve a single specific action; or at least never save enough time to justify the initial investment.

I bet they were in awe at how much fucking time you wasted memorizing a secondary set of keyboard controls for a single app just to be able to do what they do in the exact same amount of time.

>* vim : Honestly, best investment I've made in years. It will feel painful at first, but practice it like you would practice a musical instrument and text editing will become a second nature for you. Use plugins for templates and snippets.

But what about

EMACS

I could make a tutorial to show you guys how my stack works. I will, if I find the time to.
You indeed keep it together with your docker image, your Dockerfile more precisely.

Learn the basics of Docker first with a tutorial.
It all begins with a file called 'Dockerfile' where you write your Docker image (what you want to get inside of your Docker images, and the all the commands you want to run on it).
Use the 'COPY' directive to copy your code inside of it. Those files are in the same folder.

Also advise you to put all of your file under version control.
Create an account on Gitlab or Bitbucket and upload your repository there.

So when you (re)install your stack, you just have to clone your git repository from there, and run the install command.
Limitations I experienced :
It’s hard to make some GUI softwares work inside Docker. Wasn’t really made for this in the first place. But works like a charm if your workflow is CLI based like mine.
As said, You'd need to know the ins and out of every application. My approach is extremely powerful, only if you are a quite advanced Linux (power) user.

> … set of tools never changes and grows, using 10 year old tools is going to be considered productive.
That’s why I cron’d a Jenkins job building it every hour. I also tag the version of every software.
I just revise my Dockerfile regularly, so I don’t have any bad surprise, and my tools are always up to date.
Here is an extract of my Dockerfile :

ARG JPEGOPTIM_VERSION=1.4.6-r0
ARG OPTIPNG_VERSION=0.7.7-r0
…
RUN apk add --no-cache jpegoptim=${JPEGOPTIM_VERSION}
RUN apk add --no-cache optipng=${OPTIPNG_VERSION}

Yes, we could also use this approach, but it’s much harder to test (that’s why I use a Jenkins building my Dockerfile), and because of the updates of your OS at the time of your next reinstallation, you won’t obtain the same exact environment

Attached: 56614179_454841241953973_8255198457407682071_n.jpg (480x480, 28K)

Thank you from the bottom of my heart.
Best posts I have seen in recent months.
Glad to see that there are still smart people left on this board.

I'd just like to interject for a moment. What you're referring to as Linux, is in fact, GNU/Linux, or as I've recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.

Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called "Linux", and many of its users are not aware that it is basically the GNU system, developed by the GNU Project.

There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called "Linux" distributions are really distributions of GNU/Linux.

Attached: 1491967755198.jpg (516x461, 44K)

He's talking about a Linux shell, dumbass

Nice. Please, make a video of your workstation.

A tutorial format might be a little lost in the noise, but any co tent you'd like to produce would be helpful to me too.
I am a hobby programmer without much time for diving deep into things, but I've had it on my to-do list to automate the building of my workspace as well. Having just jumped into docker after avoiding it these last few years, I would say that my problem around their docs is that the information there isn't super discoverable, which has slowed my work down with all the context switching that life brings.

> RUN apk add ...
Alpine gang. Amazing distro.

Also excellent replies.

>not GNU/Screen

Attached: 1339550542691.jpg (1024x768, 294K)

printf \\ec && neofetch --ascii "$(fortune | cowsay -W 40)"

can your gui wm works over ssh easily?