dallen

joined 2 years ago
[–] dallen@programming.dev 10 points 2 years ago

If the open source release is adequate then you can just continue using it… Or fork for your needs.

[–] dallen@programming.dev 1 points 2 years ago

Sadly, still dual boot for rhino, in a VM I’m just not getting enough performance out of my aging pc.

A Linux version would be a dream come true.

[–] dallen@programming.dev 6 points 2 years ago (2 children)

I like to require access to 22 via IP whitelist and all services on SSL behind a reverse proxy. Doesn’t leave much surface to attack.

[–] dallen@programming.dev 1 points 2 years ago (4 children)

Are you sure?

This was in the linked article:

  • Caching for offline use
[–] dallen@programming.dev 8 points 2 years ago

Same! Debian with gnome on my desktop and work laptop. Raspbian on my Pi4. Headless Debian in the cloud…

[–] dallen@programming.dev 5 points 2 years ago (1 children)

I’m also a gnome shell convert. Down with the taskbar!

[–] dallen@programming.dev 4 points 2 years ago (2 children)

You can always set watchtower to blindly pull for you. If it’s going to be broken anyways, might as well automate the process.

[–] dallen@programming.dev 8 points 2 years ago

As a 4 day tech worker, 1 day community gardener, I can vouch for the therapeutic nature!

[–] dallen@programming.dev 16 points 2 years ago

#! brings back some good memories :)

[–] dallen@programming.dev 2 points 2 years ago (5 children)

Am I understanding correctly that you are building the image by copying in key elements from the host machine’s functioning nginx installation?

This is creative but not common approach to docker.

Normally software is installed following the officially documented procedure (imagine installing using apt or a shell script via RUN). Sometimes software documentation has specific recommendations to follow for containerized installs.

It’s common to have the version defined as a variable where a change in value invalidates the docker layer cache. To me it’s unclear how caching would work with your dockerfile, for example, in the event of a upgrade. You could also see how a breaking change (such as one in the paths you are copying) could run into issues with your hardcoded approach.

In the case of software like nginx, I would use the official image, mount config/cert files instead of copying, and extend in my own dockerfile if needed.

[–] dallen@programming.dev 2 points 2 years ago

What I love about Debian is there are always instructions regardless of whatever random package I want to use or Linux thing I’m trying to do.

view more: ‹ prev next ›