That works too. But the offer is always there if you need access to hardware you dont have that i do.
And i think i offered to send you a Jetson if we really needed some beefier hardware. If not, i meant to. ( not a NX :) )
Not to worry ... I have just received word that a Pi 4 is being contributed by a generous donor, so if I want to, I can keep doing 32-bit builds on the Pi 3 that PD contributed, and 64-bit on the Pi 4.
I looked for the definitive listing of Linux flavors supported and never found it. on the Appimage website it shows the linux brand "icons" for the major flavors. Deb, Red, Ubuntu etc... but no "written" listing with references to the popular derived flavors i.e. raspberry pi OS, raspian, Mint, and the myriad others...
oh wait, that's normal in the linux environment.
That works too. But the offer is always there if you need access to hardware you dont have that i do.
And i think i offered to send you a Jetson if we really needed some beefier hardware. If not, i meant to. ( not a NX :) )
Not to worry ... I have just received word that a Pi 4 is being contributed by a generous donor, so if I want to, I can keep doing 32-bit builds on the Pi 3 that PD contributed, and 64-bit on the Pi 4.
That works too. But the offer is always there if you need access to
hardware you dont have that i do.
You can totally help by downloading the appimage and trying it out on your ARM board. From what I understand, if you're running Armbian then that means you have something other than a Raspberry Pi.
I looked for the definitive listing of Linux flavors supported and never
found it. on the Appimage website it shows the linux brand "icons" forthe
That kind of misses the point. An appimage is supposed to work on *any* flavor of Linux as long as it's running the same CPU as the one it was built on (such as 64-bit x86). If you are running an uncommon distribution then please try it and let us know if it worked!
On the agenda for this weekend. Now that the jeep is mostly done ill have spare time.
That works too. But the offer is always there if you need access to
hardware you dont have that i do.
You can totally help by downloading the appimage and trying it out on your ARM board. From what I understand, if you're running Armbian then that means you have something other than a Raspberry Pi.
I didnt think about the 32/64 bit issue. All my ARM boards i 'use' are 64bit. I do have a Banana PI M3 in the closet. Ill have to dig it out later today and load it with Armbian Bullseye. Its a 32bit chip.
Updated releases of the Citadel AppImage are here [https://www.citadel.org/appimage.html] as of today, July 11. We are currently supporting 64-bit AMD/Intel and 32-bit ARM (Raspberry Pi) because those are the systems people actually seem to want ro run Citadel on.
We'll call these "late stage beta". If they run at all, they will likely run well. We believe we have most compatibility issues worked out, on the two target platforms. We may put off the 64-bit ARM image for a while since most ARM users want to run Raspberry Pi with the standard Pi OS, which is 32-bit. Users of other boards can still run Easy Install.
The final stage of development, unless compatibility issues are discovered, will focus on utilities, client, and ease of installation.
Subject: General Availability of the Citadel AppImage
I am pleased to announce that the AppImage distribution of the Citadel System has now been released, beginning with version 932 of the system. These images are available for 64-bit AMD/Intel and for 32-bit ARM (Raspberry Pi).
These are binary images comprised of a single file which unpacks at runtime and contains the entire system. You can test it with a single command without installing it. You can install it with a single command as well.
As a super bonusfest, you can also migrate from Easy Install to AppImage in-place. It will require removing some of the old pieces and just keeping your data directory. As long as you're moving from like-to-like architecture, it should work great.
The AppImage distribution also includes a migrate mode, allowing you to move a Citadel installation from one machine to another automatically, as long as both sides are running the same version of Citadel. (If not, sorry, you'll have to upgrade the source system first.)
All of this is now available at www.citadel.org. Share and Enjoy.
I plan on giving this a shot later this week or weekend on the Pi400+.
You should be able to run the 32 bit image on a 64 bit board. In fact, I would love it if you could try that.
Please be advised that after a very poor reception, the AppImage version of Citadel has been discontinued.
We will be releasing Docker images soon. So far, it looks like it's working much better.
Subject: Docker container of Citadel is now ready to download
Docker images are ready for testing :)
Go to https://www.citadel.org/docker.html to learn more. So far, this is working way better than the AppImage distribution was, and most of the work we did on that has translated very nicely to the container. It's extremely stable and should be compatible with any host system on which Docker will run.
We have 64-bit AMD/Intel and 32-bit ARM containers available.
It is currently considered a test build, but our intention is to make it the primary way people run the Citadel system, both on your own hardware and in the cloud.
Subject: Re: Docker container of Citadel is now ready to download
MUCH better so far..
Other than the expected complaint about 32bit image on a 64 bit OS, it loaded and ran without crashing on my 64bit ARM board. Admin account worked and was able to create a new user and get in. Will do more testing tomorow.
Subject: Re: Docker container of Citadel is now ready to download
Sat Aug 21 2021 19:08:24 EDT from IGnatius T Foobar Subject: Docker container of Citadel is now ready to download
Docker images are ready for testing :)
Go to https://www.citadel.org/docker.html to learn more. So far, this is working way better than the AppImage distribution was, and most of the work we did on that has translated very nicely to the container. It's extremely stable and should be compatible with any host system on which Docker will run.
We have 64-bit AMD/Intel and 32-bit ARM containers available.
It is currently considered a test build, but our intention is to make it the primary way people run the Citadel system, both on your own hardware and in the cloud.
hi, i posted a couple of messages in the support forum, re the docker images.
the download site did not mension it was for testing only, or maybe it was not obvious.
i have no prob running on test release if it works though so moving on.....
im now running the docker image as my home system, and its very stable, only thing that did not work, and whats not
obvious , a way to fix was the generation of the keys.
im running it on rocky linux 8, essentialy centos/redhat.
i ran the three openssl commands to generatev the 3 keys for webcit and citadel in the citadel-data directory, and restarted
but i still cant enable non strict ssl or starttls on thunderbird or access webcit through https, whereas i could on my old citadel 8 rpm version.
any pointers?
regards peter
Subject: Important change to mailing list behavior in Citadel 940
There's an important change to the behavior of mailing lists in Citadel 940, which has just been released.
Previously, anyone could send email to a room if that option was enabled.
Due to abuse of this feature, we have changed the behavior so that it only accepts incoming mail from email addresses that are subscribed to the list.
This is typical behavior for mailing list software so we hope that it does not cause any disruption.
To all Citadel site operators: we hope that this improves the security and experience of your sites. As always, please get in touch if you find that anything has been disrupted.
To the chinese spammer who abused our list and got citadel.org blocked by gmail: please die painfully and immediately, you miserable waste of protoplasm.
Subject: Another change to mailing list behavior -- Citadel 942
As part of a continued effort to not run afoul of recipient DKIM parsers when we deliver to mailing lists, we have made another change ... which those of you receiving this list on gmail will never find out about because goolag is still blocking our domain (seriously ... y'all are Citadel fans ... why are you still using gmail?)
Effective with server version 942, we will now set both the Reply-to: and From: headers to the address of the room rather than the address of the mailing list participant who mailed into the room. We were already doing Reply-to: but now we do From: as well.
The "display name" of the original user will be retained, regardless of whether the message originated as a remote email or as a post directly to Citadel. For example:
IGnatius T Foobar <room_my_mailing_list@frobozz.citadel.org>
We hope that this will help mailing lists to work better.
Subject: Citadel 942 released -- big changes to encryption
All right folks, as our Christmas (Jesus, not Santa) gift to all of you, Citadel 942 has been released, and is available through all of the usual methods -- Easy Install, Docker, and the good old source code download. There are a couple of important changes in this update, so read closely before you upgrade:
* WebCit must now run on the same host as Citadel Server. This is probably how 100% of you were running it anyway. When we made it network transparent 25 years ago, we didn't know what the resource requirements would be for larger systems, which we're pleased to report has never been a problem. Anyway, WebCit no longer accepts the host/port of Citadel Server on the command line, but it will accept the name of a directory where Citadel Server is running.
In most cases you won't need to specify anything at all because it defaults to /usr/local/citadel.
* Keys and Certificates are no longer kept in separate directories for WebCit and Citadel Server.
WebCit will use the keys/ directory from Citadel Server, so you only have to install a certificate in ONE place. Now you see the real reason we made the previous change. Since we can now guarantee that WebCit is running on the same host, and knows what directory Citadel Server is running in, it can just grab the key and certificate.
* If the key and/or certificate are replaced or modified, both WebCit and Citadel Server will detect this change, and immediately begin serving them without requiring a restart.
* WebCit is now compatible with the HTTP-01 Challenge of the ACME certificate enrollment protocol.
Put it all together and the reason for all these changes ought to be obvious: you can now use the Let's Encrypt certificate authority with Citadel, and it's really really easy. Read https://www.citadel.org/sslcertificates.html to get more detailed instructions.
Subject: Re: Citadel 942 released -- big changes to encryption
* WebCit must now run on the same host as Citadel Server. This is
probably how 100% of you were running it anyway. When we made it
network transparent 25 years ago, we didn't know what the resource
requirements would be for larger systems, which we're pleased to report
A lot has changed since the early aughts. Machines are now available with more processor cores than would ever be required by an any hobbyist citadel or even a midsize corporate installation, so scale-up is easier than scale-out. Storage is redundant and self-snapshotting. Hardware can be reprovisioned so quickly that "single point of failure" is not as scary as it used to be.
Subject: Re: Citadel 942 released -- big changes to encryption
That's the same reason we chose to build a Docker container with the *entire* Citadel System instead of putting each component in its own container. The kind of people who run Citadel want the ease of deployment that comes with a container, not the ability to build a system that can handle a million concurrent users.
And yes, filesystems with built-in snapshotting are an insanely great blessing.