I am proud to announce that I was able to port the latest v17 turnkey system to the raspberry pi 4. I was able to port the following preliminary images if you want to start testing:
General question for anybody who knows how the TKL Let's Encrypt cert request / renewal works. Sure I could read the docs but I would kind of play with this idea and get feedback.
I have a goal of developing "glue code" such that a TKL appliance can be hosted behind a NAT, and set up a reverse proxy to another system with a public-facing IP. In plain English, so that people can host TKL boxes at home (for example) and proxy all traffic thru a $3/mo VPS with a public IP (for example).
Hello Jeremy, I have been testing Zentyal on our proxmox server and if you are interested this is definitely ready for prime time as a mail, file server and active directory domain controller. It would be a good candidate for an appliance. This currently runs on Ubuntu so I don't know if it's too much work.
Regards
Paul
Has anybody ever done a desktop build using Turnkey?
I'm interested in being able to churn out customized .iso builds of Bunsenlabs[1] with my own suite of installed apps, custom desktop environment settings, and the like, using TKLdev.
Just curious if this has been done before and not been a disaster! :D
What is Turnkeys and its usesrs thoughts on using update scripts for the TKLs that don't update from a repo?
Is there a reason that nothing has been done for updates in these TKLs?
For example: Gitea
To update Gitea it is just downloading the new binary and moving it in place and restarting the service, that seems like something that can easily be scripted and set as a cron job?
