[Citadel Development] Re: [SCM] Configuration for building a Citadel container in Docker branch master updated. 8bf0b0986137cdbd091b89fc74fba597acca8f47
So, I seem to remember that you use Ubuntu to develop Citadel; Then... Should I use a VM with Ubuntu server to use Docker + Citadel? I don't really know which is the right distribution for Docker. 2021 https://kuberty.io/blog/best-os-for-docker/ 2021 https://medium.com/nerd-for-tech/look-docker-no-distro-5dc87d4deb00 <- This gives me shivers, I only read it a little bit. 2017 https://containerjournal.com/features/os-best-docker-heres-decide/ Year before I tried a little with Ubuntu; and a little using Synology which allows using Docker. But I'm more interested in using a dedicated VM for Citadel. Regards On 8/4/21 11:12 PM, IGnatius T Foobar wrote: Lots of great progress tonight on the Docker container. As expected, much of the work that went into the AppImage was reusable in Docker, and the Docker version is running quite well already. It doesn't feel as "fragile" as the AppImage did, and I think it's going to serve us better in the long term.
[Citadel Development] (null)
This is sad news. AppImage seemed like the solution for so many problems. I never had much luck, and I've had a lot of other fires burning so didn't get to test as much as I'd like to. But I've wanted to play around with docker. Maybe this will be my chance.
[Citadel Development] Re: [SCM] Configuration for building a Citadel container in Docker branch master updated. 8bf0b0986137cdbd091b89fc74fba597acca8f47
Lots of great progress tonight on the Docker container. As expected, much of the work that went into the AppImage was reusable in Docker, and the Docker version is running quite well already. It doesn't feel as "fragile" as the AppImage did, and I think it's going to serve us better in the long term.
[Citadel Development] [SCM] Citadel Server, WebCit, utilities branch master updated. Release_902-676-gb4fbfa534
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Citadel Server, WebCit, utilities". The branch, master has been updated via b4fbfa534369c2cc497031b715430bcd5ceb1348 (commit) from 3e3e503f9464c61bf8cefcb0551d42123db9fbf4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://code.citadel.org/?p=citadel.git=commit=b4fbfa534369c2cc497031b715430bcd5ceb1348 commit b4fbfa534369c2cc497031b715430bcd5ceb1348 Author: Art Cancro Date: Thu Aug 5 01:10:16 2021 -0400 Abandoned the AppImage --- Summary of changes: appimage/.gitignore | 2 - appimage/README.txt | 42 - appimage/build_appimage.sh | 110 appimage/citadel.AppDir/.DirIcon| 1 - appimage/citadel.AppDir/AppRun | 258 appimage/citadel.AppDir/citadel.desktop | 8 - appimage/citadel.AppDir/citadel.png | Bin 926 -> 0 bytes appimage/ctdlvisor.c| 286 appimage/excludelist| 225 - 9 files changed, 932 deletions(-) delete mode 100644 appimage/.gitignore delete mode 100644 appimage/README.txt delete mode 100755 appimage/build_appimage.sh delete mode 12 appimage/citadel.AppDir/.DirIcon delete mode 100755 appimage/citadel.AppDir/AppRun delete mode 100644 appimage/citadel.AppDir/citadel.desktop delete mode 100644 appimage/citadel.AppDir/citadel.png delete mode 100644 appimage/ctdlvisor.c delete mode 100644 appimage/excludelist hooks/post-receive -- Citadel Server, WebCit, utilities
[Citadel Development] [SCM] Configuration for building a Citadel container in Docker branch master updated. 8bf0b0986137cdbd091b89fc74fba597acca8f47
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Configuration for building a Citadel container in Docker". The branch, master has been updated via 8bf0b0986137cdbd091b89fc74fba597acca8f47 (commit) from 2e8ed5d4963ca9cc2d86e70024543eabb99b238f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 8bf0b0986137cdbd091b89fc74fba597acca8f47 Author: Art Cancro Date: Thu Aug 5 01:09:37 2021 -0400 Revived this old project to run Citadel in a Docker container. It uses 'ctdlvisor' from the ill-fated AppImage project, and appears to be running well now. --- Summary of changes: Dockerfile| 14 +-- README.txt| 2 +- citadel-docker-startup.sh | 18 --- ctdlvisor.c | 288 ++ run-citadel.sh| 25 +++- supervisor.conf | 18 --- 6 files changed, 316 insertions(+), 49 deletions(-) delete mode 100755 citadel-docker-startup.sh create mode 100644 ctdlvisor.c delete mode 100644 supervisor.conf hooks/post-receive -- Configuration for building a Citadel container in Docker
[Citadel Development] Re: [SCM] Citadel Server, WebCit, utilities branch master updated. Release_902-675-g3e3e503f9
>So, do I stop my tests with the AppImage and wait for the thingy* in Docker? Let's put it on hold for now. The goal is the same, but the package format is different. We've learned a lot over the last few months, and in developing the AppImage we solved a LOT of problems that were making Docker problematic for us. To be sure, I don't want to end up in a place where you have to become a Docker expert to run Citadel. The goal is to *hide* the complexity, not to add more.
[Citadel Development] Re: [SCM] Citadel Server, WebCit, utilities branch master updated. Release_902-675-g3e3e503f9
So, do I stop my tests with the AppImage and wait for the thingy* in Docker? *No disrespect intended. On 8/3/21 4:29 PM, noreply wrote: This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Citadel Server, WebCit, utilities". The branch, master has been updated via 3e3e503f9464c61bf8cefcb0551d42123db9fbf4 (commit) from 993d83d05304da06680a5c731533c6944f3d6fe9 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://code.citadel.org/?p=citadel.git=commit=3e3e503f9464c61bf8cefcb0551d42123db9fbf4 commit 3e3e503f9464c61bf8cefcb0551d42123db9fbf4 Author: Art Cancro Date: Tue Aug 3 18:29:09 2021 -0400 This completes the server portion of the Global Alias table. --- Summary of changes: citadel/internet_addressing.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) hooks/post-receive
[Citadel Development] Re: PIVOT
The "series of messages" leads to a sad unraveling. Well, to a more complex one, I had stopped studying Docker as soon as I saw the AppImage, I will have to resume its study and use it. To date, I had barely played with Docker; and like a good Alzheimer's trainee, I forgot about it in a matter of weeks. On 8/3/21 1:28 PM, IGnatius T Foobar wrote: So far, it seems that the distribution of Citadel as an AppImage has been a complete flop. I had high hopes for a universal binary to work but it doesn't seem to want to work on any computer that isn't mine. This is not to say that all the work wasn't worth it. We've phased out the LFHS build, we've removed a lot of legacy code, and for the AppImage we built "ctdlvisor" which can do a controlled run of all Citadel components. That means it would now be FAR easier to build a Docker version of Citadel than it was the last time I tried it, 22 months ago. I am considering a pivot towards that strategy.
[Citadel Development] Re: [SCM] Citadel Server, WebCit, utilities branch master updated. Release_902-666-g60b2f3fa4
The only good thing about not seeing your emails for 3 weeks is that I am binge reading them. WOW! On 7/28/21 3:56 PM, IGnatius T Foobar wrote: s3cr3to: this is all towards your use case, so hold tight, it'll be ready soon!
