Search results

You're probably thinking of MacProxy Plus. https://github.com/hunterirving/macproxy_plus The fork of my fork of the original macproxy python flask script. :)

@mactjaap Just in case you didn't notice: a new feature as of netatalk v4.2.1 is the bundling of Thomas Kaiser's pap backend for CUPS. You can enable it with "-Dwith-cups-pap-backend=true" in the build system. I believe you're currently bundling the same backend script yourself, so up to you...

To make a long story short, we all moved on to other projects. One of the former devs (Uwe) is now maintaining his own fork called scsi2pi (which doesn't come with its own GUI but rather is compatible with, and rely on the piscsi Web UI. So packaging scsi2pi with the piscsi Web UI could actually...

@mactjaap On this topic, have you considered bundling piscsi (or scsi2pi) and the piscsi Web UI with your distribution? The piscsi app itself is very light-weight so it shouldn't be much of an overhead for the RPi on top of the other software that you're bundling. Particularly relevant...

Speaking about hostname, once you upgrade to netatalk 4.2 you get access to the new "server name" option that allows you to set the name of the AFP server independent of hostname. (This was a feature of netatalk 2.x but fell off in 3.x...) May come in handy for you all.

In addition to the containerized webmin discussed in the netatalk 2.4 thread, I also got the mysql CNID backend up and running in containers a few days ago. The original intention was for testing purposes: to test the mysql backend in continuous integration and stop me from breaking it (again.)...

A solution to this issue has been merged into the main branch now. I introduced a dynamic module option that hides away the "service actions" that expect the netatalk daemons to be locally available. This option gets enabled by default when building the webmin module via the Dockerfile. So now...

Being stuck at home over the Easter weekend fighting off a cold, I had the inspiration/time to work on this. Over at the feature request ticket that you raised, I have explained the solution at a high level. In the end, I settled on the config file polling option. Hopefully it won't have too...

@Mk.558 at risk of going off topic, have you by any chance serviced the floppy drive in your SE/30 in recent years? In my experience from refurbishing dozens of Mac floppy drives, more than 90% of drives of that era that I worked on were restored to full functionality after being stripped down...

My macproxy fork has been effectively obsoleted by macproxy plus: https://github.com/hunterirving/macproxy_plus You may want to use this one instead!

In my experience it's surprisingly consistent. I test nonstop on 12 different platforms. :)

@Mk.558 Thanks for the solid feedback, as always! I restructured the Quick Start page and put the list of requirements in the middle, as part of a more natural flow of operations. To your point, it might be worth experimenting with splitting the list so that only mandatory requirements come in...

I've been tinkering with the organization of the documentation lately, since I was able to lift it all into Markdown in the last release cycle which makes it much easier to work with. Right now my thinking is that the entry point is the documentation page on the website...

This is such an amazing reference resource. Thanks for your heroic push to overhaul it!

Do you already have a bridge between your LocalTalk and Ethernet networks (where the RPi sits)? If so, connecting your ImageWriter to the LocalTalk network should be enough to make it accessible from the RPi that's running netatalk / pap. Note that in general, you want to avoid routing...

Quick poll: of you netatalk users here, is anyone relying on the "include = /path/to/extra_afp.conf" directive in afp.conf? For context, this is a directive that allows you to dynamically load and nest a secondary afp.conf file. However this relied on local hacks to the iniparser library. I am...

This developer is I. Haha. @NJRoadfan and I discussed this topic a few months ago when working towards the v4 release. We didn’t have a concrete reason to change it at the time. But the use case at hand is a fair reason. No promises, but I’ll tinker with this and see how feasible it is to...

It's best to start the daemon directly rather than using systemd, to get more helpful output. I.e. run "papd -d" from the terminal.

Yep, "ad" is your friend. See the man page for usage notes: https://netatalk.io/stable/htmldocs/ad.1 Note that netatalk has to be running to use ad, because it relies on access to the CNID daemon to carry out the metadata update.

This might be the ideal stress test scenario for these code changes! To explain what I'm up to: I want to proactively shore up security and memory safety in 4.2, leveraging SonarQube static analysis. So far, I was able to resolve all security bugs – the outstanding ones had to do with PAM...