I use the linuxserver images for Nextcloud. Have worked pretty well for me over the past few years.
I use the linuxserver images for Nextcloud. Have worked pretty well for me over the past few years.
I find it commendable that you wrote code so horrible other libraries started throwing more errors wondering what the hell you were doing.
> Do you like what you've build?
Inspirational or condescending? [i/C] █
This isn’t the new generation of devs. This is just new devs. Some people refuse to grow out of this stage.
Yeah, that thing is honestly impressive. If I didn’t already have a full network manager wg setup I’d just use that.
Reformatting that compose for people:
version: "2.1" services:
wireguard:
image: linuxserver/wireguard
container_name: wireguard
cap_add:
- NET_ADMIN
- SYS_MODULE
environment:
- PUID=1000
- PGID=1000
- TZ=Asia/Singapore
- SERVERURL=auto #optional
- SERVERPORT=51820 #optional
- PEERS=1 #optional
- PEERDNS=auto #optional
- INTERNAL_SUBNET=10.13.13.0 #optional
volumes:
- ./config:/config
- /lib/modules:/lib/modules
ports:
- 51820:51820/udp
sysctls:
- net.ipv4.ip_forward=1
- net.ipv4.conf.all.src_valid_mark=1
restart: unless-stopped
Sounds like you didn’t read the extended manual: https://github.com/linuxserver/docker-wireguard
There are a lot of other configs for that container that must be provided before startup. It’s just a generic runner. If you want it to run as a server you need to follow this section: https://github.com/linuxserver/docker-wireguard?tab=readme-ov-file#server-mode
Are you at getting the handshake in the app? If so, you’re probably just missing the dispatch commands for traffic masquerading.
Eaton is your best bet for compatibility in the consumer market.
What am I missing here?
That shoddy code rots when you update the compiler. (And occasionally good code, depending on what rules the compiler wants to start enforcing)
These types of changes are inevitable.
To be fair, C predates dependency hell. It was either there or it wasn’t. C++ has less of an excuse, but it was just object oriented concepts taped to C so it’s no surprise it was also missing dependency management.
Now with cmake, gnu-make, meson, gradel, and the world of metabuild systems that wrap those, nothing will change. It it does, it might as well kick start world war 3.
Yo, they added full page copies now? Gotta give it a spin again
Well, assuming you meant type specifier, at least not before C99. After that it is required. C23 explicitly states that a type specifier is required for all declarations.
If you actually meant type qualifier, then no. That was never required.
But also, sorting big endian automatically groups elements associated with common functions making search, completions, and snippets easier (if you use them). I’m torn
To me on the security side of things caddy has a feature I have yet to see anywhere else: default reverse proxy headers.
Got something you want to lock down remote js loading on unless it explicitly requests an override? Default the variable to a locked value. The application can override it with it’s own header as necessary.
deleted by creator
I wish nginx had the concept of default header values for reverse proxies…
I mean, you can kind of do it with macros but man…
I mean, you shouldn’t really parse any language (markup, script or otherwise) with regex. The point is there are other tools for the job that get you closer to what the actual interpreter is expecting to see. It’s really easy to botch a regex and accidentally create new syntax matches.
Regex is fine for noncritical parsing. You’ll often see it used for text editor / IDE language syntax highlighting, but you should also have noticed by now how often that tends to break down with more extreme combinations of syntax.
I do agree that lexers should still be preferred for manual manipulation of existing langues, but do whatever you want. It’s not like any of us can stop you.
If you’re just looking for RSS -> Push take a look at feedpushr
I use it with gotify without too many issues.
For those who don’t want to click the link for context: