36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
# OKAY NERDS LISTEN UP
|
|
|
|
I had to make some fucking compromises okay?
|
|
|
|
## What this Repo is For?
|
|
|
|
`base` defines a developer environment. It packages up Git and Neovim into a quick-and-easy docker image.
|
|
|
|
Then you extend upon it to create environments for different purposes. The `flutter` example provided shows how you can maintain the same cozy environment while also being able to test GUI application. This is thanks to two things; x application forwarding and xwayland.
|
|
|
|
## What are the compromises
|
|
|
|
I can't make it a one-stop-shop thing. You have to mount a few cheeky locations, and it all depends on your configuration, because all of us fucking Linux users have more opinions on sysconf than windows users have spyware.
|
|
|
|
I had to draw some bloody boundaries, okay?
|
|
|
|
- Base now only installs ssh/git/yay/nvim and configures nvim
|
|
- I expect that you're adhering to XDG shit for ssh socks. IE /run/user/some/shit
|
|
- I expect that you have xhost installed.
|
|
- I expect that if this throws errors that you figure your own shit out
|
|
- I expect that you have ~/.gitconfig configured on your host
|
|
- I expect that your ~/.gitconfig just looks at ~/.config/git like it should from fucking factory
|
|
- You're welcome to map ~/.config/nvim I dont care.
|
|
- Other shit. Read run.sh.
|
|
|
|
## What's nice?
|
|
|
|
It does seem to kind-of "just work".
|
|
|
|
If you're using SSH agent properly on your host then the docker container just kinda
|
|
shares that love. Adding keys in container also adds in host because of volume maps
|
|
|
|
So this whole thing is kinda chill. The only annoying thing is that sometimes
|
|
the text in container is blue, sometimes it's white. Depends on your TERM and
|
|
COLORTERM variables. I try to set sane variables but I think mapping ~/.bashrc breaks
|
|
that.
|