Turnkey Linux

What!?! Another month (actually a month and a half) has gone by and we're only just announcing the next batch?! Well, I better get on with it then! Today I'm announcing 25 more appliances updated to v14.2. I'm also pleased to (finally) announce ... [More] that the new improved v14.2 OpenStack builds are available for all v14.2 appliances. The v14.2 OVA and VMDK builds have also been refactored and previous v14.2 builds re-released. As per always, the updated appliances (inc new OpenStack, OVA & VMDK) can be downloaded and/or launched on AWS from the Hub via their respective appliance pages. The 25 new ones are linked below, links to the others are in the previous release announcement. Alternatively all our images are available via our mirror network, many support rsync. Just look for 14.2! 25 (more) Updated Appliances Straight to the point; the freshly updated appliances (in alphabetical order) are: b2evolution Concrete5 Dokuwiki GitLab Joomla 3 Laravel LimeSurvey Mantis MoinMoin OpenLDAP osCommerce phpBB phpList SimpleInvoices SimpleMachines SITracker SuiteCRM Trac Tracks Ushahidi vTiger web2py XOOPS YiiFramework Tweaking the OVA manifest For what it's worth, the delay was caused by issues with OVAs from the first batch. The problems were reported by John Youssef and pbt39ppc (here and here respectively). The issues were introduced by our use of the latest version of VMware's OVFTool. The new OVFTool defaults to SHA256 checksums in the manifest file (inside the OVA). Older versions of VMware products aren't compatible with that, so it caused issues for some users. I rebuilt some test images using only SHA1 checksums in the manifest, and some testers confirmed that resolved the primary issue. Whilst relatively weak checksums (i.e. SHA1) could be seen as a security concern, we believe that is mitigated by the signed hash file (which includes SHA256 & SHA512 checksums) which we provide for the OVA itself. So those that are security conscious (and you all should be!) can use that, with the included manifest file just there as a secondary corruption check. Adjusting the OVF OS type However, another new issue popped up. It seems that the updated OVFTool is also better at working out the underlying OS. So for the v14.2 update, the internal OVF file (inside the OVA) included some more specific OS info. Namely that TurnKey is "Debian 8 64 bit". On face value that seemed pretty cool. I loved it during testing when my VBox test VM had the Debian logo as it's icon! Unfortunately again though, older versions of VMware products do not recognise "Debian 8 64 bit" as a valid OS. So that too has been reverted to our previous v14.x release default. I.e. "Other OS 64 bit". Refactoring the VM builds While I was digging around inside the code, I noticed that our VM builds (both OVA and VMDK) were actually still using a separate /boot partition (outside the LVM). That is no longer needed as grub2 can boot into LVM. We actually removed the separate boot partition from the ISO builds for v14.2 already. So it seemed appropriate for the VM build to be consistent. Extra special thanks to John Youssef and pbt39ppc for reporting the initial issue, as well as following up testing and feedback. Your help was invaluable to confirming and resolving the issues. Once again, the TurnKey community comes through with the goods! :) OpenStack... finaly! I'm so glad that we've finally caught up on v14.2 OpenStack builds. Tomas Vondra and Home at Cloud have been so patient. He contributed the code ages ago and it's only now accessible to the general public. Thanks again Tomas and your employer Home at Cloud for the great work. As noted above, they are available from the relevant appliance pages. Please be aware that only the v14.2 builds (version noted on each appliance page, or use the links on this page and the previous release blog) are in this new and improved format. The others are coming as fast as we can! :) Give us your feedback Please try them out and let us know what you think. We're especially interested in bug reports, suggested improvements (big and small) and any other constructive criticism you have for us. Please post in the comments below, or start a new thread in the forums. Bug reports and feature requests can be lodged directly to our issue tracker. And last, but certainly not least; thanks to the community for all you do about the place. You rock! Blog Tags:  news development debian community appliances release stable [Less]

What!?! Another month (actually a month and a half) has gone by and we're only just announcing the next batch?! Well, I better get on with it then! Today I'm announcing 25 more appliances updated to v14.2. I'm also pleased to (finally) announce ... [More] that the new improved v14.2 OpenStack builds are available for all v14.2 appliances. The v14.2 OVA and VMDK builds have also been refactored and previous v14.2 builds re-released. As per always, the updated appliances (inc new OpenStack, OVA & VMDK) can be downloaded and/or launched on AWS from the Hub via their respective appliance pages. The 25 new ones are linked below, links to the others are in the previous release announcement. Alternatively all our images are available via our mirror network, many support rsync. Just look for 14.2! 25 (more) Updated Appliances Straight to the point; the freshly updated appliances (in alphabetical order) are: b2evolution Concrete5 Dokuwiki GitLab Joomla 3 Laravel LimeSurvey Mantis MoinMoin OpenLDAP osCommerce phpBB phpList SimpleInvoices SimpleMachines SITracker SuiteCRM Trac Tracks Ushahidi vTiger web2py XOOPS YiiFramework Tweaking the OVA manifest For what it's worth, the delay was caused by issues with OVAs from the first batch. The problems were reported by John Youssef and pbt39ppc (here and here respectively). The issues were introduced by our use of the latest version of VMware's OVFTool. The new OVFTool defaults to SHA256 checksums in the manifest file (inside the OVA). Older versions of VMware products aren't compatible with that, so it caused issues for some users. I rebuilt some test images using only SHA1 checksums in the manifest, and some testers confirmed that resolved the primary issue. Whilst relatively weak checksums (i.e. SHA1) could be seen as a security concern, we believe that is mitigated by the signed hash file (which includes SHA256 & SHA512 checksums) which we provide for the OVA itself. So those that are security conscious (and you all should be!) can use that, with the included manifest file just there as a secondary corruption check. Adjusting the OVF OS type However, another new issue popped up. It seems that the updated OVFTool is also better at working out the underlying OS. So for the v14.2 update, the internal OVF file (inside the OVA) included some more specific OS info. Namely that TurnKey is "Debian 8 64 bit". On face value that seemed pretty cool. I loved it during testing when my VBox test VM had the Debian logo as it's icon! Unfortunately again though, older versions of VMware products do not recognise "Debian 8 64 bit" as a valid OS. So that too has been reverted to our previous v14.x release default. I.e. "Other OS 64 bit". Refactoring the VM builds While I was digging around inside the code, I noticed that our VM builds (both OVA and VMDK) were actually still using a separate /boot partition (outside the LVM). That is no longer needed as grub2 can boot into LVM. We actually removed the separate boot partition from the ISO builds for v14.2 already. So it seemed appropriate for the VM build to be consistent. Extra special thanks to John Youssef and pbt39ppc for reporting the initial issue, as well as following up testing and feedback. Your help was invaluable to confirming and resolving the issues. Once again, the TurnKey community comes through with the goods! :) OpenStack... finaly! I'm so glad that we've finally caught up on v14.2 OpenStack builds. Tomas Vondra and Home at Cloud have been so patient. He contributed the code ages ago and it's only now accessible to the general public. Thanks again Tomas and your employer Home at Cloud for the great work. As noted above, they are available from the relevant appliance pages. Please be aware that only the v14.2 builds (version noted on each appliance page, or use the links on this page and the previous release blog) are in this new and improved format. The others are coming as fast as we can! :) Give us your feedback Please try them out and let us know what you think. We're especially interested in bug reports, suggested improvements (big and small) and any other constructive criticism you have for us. Please post in the comments below, or start a new thread in the forums. Bug reports and feature requests can be lodged directly to our issue tracker. And last, but certainly not least; thanks to the community for all you do about the place. You rock! Blog Tags:  news development debian community appliances release stable [Less]

I can't believe it's been over 6 years since we announced v1.0. Even more shocking is the last hub tagged blog post was over 4 years ago, given that we haven't stopped developing, improving and adding features to the Hub during that time. ... [More] The below are just a few highlights that stood out while I was reviewing the git-log for the base application, though I'm sure I missed some... $ git diff --stat 68a14f27 HEAD 585 files changed, 54948 insertions(+), 15202 deletions(-) Review of notable changes since the last post On-boarding and support Improved account setup flow. Since the deployment of the new on-boarding flow, we've seen a 68.3% increase in users going from zero to a fully setup account. We continue to analyze where users are getting stuck, improve the flow, and remove friction where ever we can. We've been experimenting with integrated online chat and issue tracking. Obviously this has increased our support load, but the improved support we can offer users, and the insights we get are totally worth it. IAM Role support Mid 2014 we added support for IAM roles. IAM is AWS's Identity and Access Management system. An IAM role is the secure, recommended way to authorize apps to call the AWS API on your behalf. Before IAM roles, the only way to provide access was to share secret keys which could get stolen. Worse, there was no way to tell who was using those keys to access your account or what they were doing. With IAM roles, there are no keys to steal and it is possible to log access by role to keep track of all actions performed on your behalf by 3rd party apps. We believe in multi-layered security, so we also developed what we internally call the 'hub-vault', a separate system acting as the gatekeeper for performing 'assume-role' API calls against Amazon STS. Cloud deployment and management Completely redesigned dashboards (servers, domains, assets, etc.). Support for HVM instance types (bang-for-your-buck). Support for 'magical' VPC deployments (creates a VPC if needed, enables DNS attributes, creates and attaches an Internet Gateway, sets up VPC/Gateway routing, creates Subnets and associates routing tables). Improved launch page - inline usage fees, instance sizes tagged per generation, more advanced options (enable security notifications, availability zone selection). Currently supports 14.1 appliances, updated to 14.2 when released. Added support for multi-zones. Reserved instances now supports 3rd party offers. Server SSH fingerprints available in dashboard for OOB verification. TurnKey Backup and Migration (TKLBAM) Completely redesigned dashboard. Support for IAM role STS credentials, and vanilla Amazon S3. Reduced storage fees ($0.03/GB). Backups are now stored in regional buckets with unique prefixes. Due to supporting vanilla S3, the Hub now has a TKLBAM free plan. New billing system We now leverage Stripe to handle our billing, an industry leading payment processor who processes billions of dollars worth of transactions for thousands of companies. Integrated with end-to-end encryption from browser to Stripe, your credit card details never touch the Hub. The Hub now has stream-lined upgrade/downgrade functionality, with pro-rata support, as well as free trials. Previously the Hub leveraged Amazon DevPay for billing as well as TKLBAM storage. We've developed a migration mechanism to ease the move, as well as providing free-upgrades / discounts. Amazon marketplace integration Users who have instances deployed via the Amazon marketplace can now register them with the Hub, and get the standard TKLBAM plan as well as support enabled in their account. As usual, if you have feedback or ideas for improvement, please send it our way. The TurnKey Hub lives at: https://hub.turnkeylinux.org Blog Tags:  news aws backup ec2 cloud hub tklbam [Less]

I can't believe it's been over 6 years since we announced v1.0. Even more shocking is the last hub tagged blog post was over 4 years ago, given that we haven't stopped developing, improving and adding features to the Hub during that time. ... [More] The below are just a few highlights that stood out while I was reviewing the git-log for the base application, though I'm sure I missed some... $ git diff --stat 68a14f27 HEAD 585 files changed, 54948 insertions(+), 15202 deletions(-) Review of notable changes since the last post On-boarding and support Improved account setup flow. Since the deployment of the new on-boarding flow, we've seen a 68.3% increase in users going from zero to a fully setup account. We continue to analyze where users are getting stuck, improve the flow, and remove friction where ever we can. We've been experimenting with integrated online chat and issue tracking. Obviously this has increased our support load, but the improved support we can offer users, and the insights we get are totally worth it. IAM Role support Mid 2014 we added support for IAM roles. IAM is AWS's Identity and Access Management system. An IAM role is the secure, recommended way to authorize apps to call the AWS API on your behalf. Before IAM roles, the only way to provide access was to share secret keys which could get stolen. Worse, there was no way to tell who was using those keys to access your account or what they were doing. With IAM roles, there are no keys to steal and it is possible to log access by role to keep track of all actions performed on your behalf by 3rd party apps. We believe in multi-layered security, so we also developed what we internally call the 'hub-vault', a separate system acting as the gatekeeper for performing 'assume-role' API calls against Amazon STS. Cloud deployment and management Completely redesigned dashboards (servers, domains, assets, etc.). Support for HVM instance types (bang-for-your-buck). Support for 'magical' VPC deployments (creates a VPC if needed, enables DNS attributes, creates and attaches an Internet Gateway, sets up VPC/Gateway routing, creates Subnets and associates routing tables). Improved launch page - inline usage fees, instance sizes tagged per generation, more advanced options (enable security notifications, availability zone selection). Currently supports 14.1 appliances, updated to 14.2 when released. Added support for multi-zones. Reserved instances now supports 3rd party offers. Server SSH fingerprints available in dashboard for OOB verification. TurnKey Backup and Migration (TKLBAM) Completely redesigned dashboard. Support for IAM role STS credentials, and vanilla Amazon S3. Reduced storage fees ($0.03/GB). Backups are now stored in regional buckets with unique prefixes. Due to supporting vanilla S3, the Hub now has a TKLBAM free plan. New billing system We now leverage Stripe to handle our billing, an industry leading payment processor who processes billions of dollars worth of transactions for thousands of companies. Integrated with end-to-end encryption from browser to Stripe, your credit card details never touch the Hub. The Hub now has stream-lined upgrade/downgrade functionality, with pro-rata support, as well as free trials. Previously the Hub leveraged Amazon DevPay for billing as well as TKLBAM storage. We've developed a migration mechanism to ease the move, as well as providing free-upgrades / discounts. Amazon marketplace integration Users who have instances deployed via the Amazon marketplace can now register them with the Hub, and get the standard TKLBAM plan as well as support enabled in their account. As usual, if you have feedback or ideas for improvement, please send it our way. The TurnKey Hub lives at: https://hub.turnkeylinux.org Blog Tags:  news aws backup ec2 cloud hub tklbam [Less]

I can't believe it's been over 6 years since we announced v1.0. Even more shocking is the last hub tagged blog post was over 4 years ago, given that we haven't stopped developing, improving and adding features to the Hub during that time. ... [More] The below are just a few highlights that stood out while I was reviewing the git-log for the base application, though I'm sure I missed some... $ git diff --stat 68a14f27 HEAD 585 files changed, 54948 insertions(+), 15202 deletions(-) Review of notable changes since the last post On-boarding and support Improved account setup flow. Since the deployment of the new on-boarding flow, we've seen a 68.3% increase in users going from zero to a fully setup account. We continue to analyze where users are getting stuck, improve the flow, and remove friction where ever we can. We've been experimenting with integrated online chat and issue tracking. Obviously this has increased our support load, but the improved support we can offer users, and the insights we get are totally worth it. IAM Role support Mid 2014 we added support for IAM roles. IAM is AWS's Identity and Access Management system. An IAM role is the secure, recommended way to authorize apps to call the AWS API on your behalf. Before IAM roles, the only way to provide access was to share secret keys which could get stolen. Worse, there was no way to tell who was using those keys to access your account or what they were doing. With IAM roles, there are no keys to steal and it is possible to log access by role to keep track of all actions performed on your behalf by 3rd party apps. We believe in multi-layered security, so we also developed what we internally call the 'hub-vault', a separate system acting as the gatekeeper for performing 'assume-role' API calls against Amazon STS. Cloud deployment and management Completely redesigned dashboards (servers, domains, assets, etc.). Support for HVM instance types (bang-for-your-buck). Support for 'magical' VPC deployments (creates a VPC if needed, enables DNS attributes, creates and attaches an Internet Gateway, sets up VPC/Gateway routing, creates Subnets and associates routing tables). Improved launch page - inline usage fees, instance sizes tagged per generation, more advanced options (enable security notifications, availability zone selection). Currently supports 14.1 appliances, updated to 14.2 when released. Added support for multi-zones. Reserved instances now supports 3rd party offers. Server SSH fingerprints available in dashboard for OOB verification. TurnKey Backup and Migration (TKLBAM) Completely redesigned dashboard. Support for IAM role STS credentials, and vanilla Amazon S3. Reduced storage fees ($0.03/GB). Backups are now stored in regional buckets with unique prefixes. Due to supporting vanilla S3, the Hub now has a TKLBAM free plan. New billing system We now leverage Stripe to handle our billing, an industry leading payment processor who processes billions of dollars worth of transactions for thousands of companies. Integrated with end-to-end encryption from browser to Stripe, your credit card details never touch the Hub. The Hub now has stream-lined upgrade/downgrade functionality, with pro-rata support, as well as free trials. Previously the Hub leveraged Amazon DevPay for billing as well as TKLBAM storage. We've developed a migration mechanism to ease the move, as well as providing free-upgrades / discounts. Amazon marketplace integration Users who have instances deployed via the Amazon marketplace can now register them with the Hub, and get the standard TKLBAM plan as well as support enabled in their account. As usual, if you have feedback or ideas for improvement, please send it our way. The TurnKey Hub lives at: https://hub.turnkeylinux.org Blog Tags:  news aws backup ec2 cloud hub tklbam [Less]

I can't believe it's been over 6 years since we announced v1.0. Even more shocking is the last hub tagged blog post was over 4 years ago, given that we haven't stopped developing, improving and adding features to the Hub during that time. ... [More] The below are just a few highlights that stood out while I was reviewing the git-log for the base application, though I'm sure I missed some... $ git diff --stat 68a14f27 HEAD 585 files changed, 54948 insertions(+), 15202 deletions(-) Review of notable changes since the last post On-boarding and support Improved account setup flow. Since the deployment of the new on-boarding flow, we've seen a 68.3% increase in users going from zero to a fully setup account. We continue to analyze where users are getting stuck, improve the flow, and remove friction where ever we can. We've been experimenting with integrated online chat and issue tracking. Obviously this has increased our support load, but the improved support we can offer users, and the insights we get are totally worth it. IAM Role support Mid 2014 we added support for IAM roles. IAM is AWS's Identity and Access Management system. An IAM role is the secure, recommended way to authorize apps to call the AWS API on your behalf. Before IAM roles, the only way to provide access was to share secret keys which could get stolen. Worse, there was no way to tell who was using those keys to access your account or what they were doing. With IAM roles, there are no keys to steal and it is possible to log access by role to keep track of all actions performed on your behalf by 3rd party apps. We believe in multi-layered security, so we also developed what we internally call the 'hub-vault', a separate system acting as the gatekeeper for performing 'assume-role' API calls against Amazon STS. Cloud deployment and management Completely redesigned dashboards (servers, domains, assets, etc.). Support for HVM instance types (bang-for-your-buck). Support for 'magical' VPC deployments (creates a VPC if needed, enables DNS attributes, creates and attaches an Internet Gateway, sets up VPC/Gateway routing, creates Subnets and associates routing tables). Improved launch page - inline usage fees, instance sizes tagged per generation, more advanced options (enable security notifications, availability zone selection). Currently supports 14.1 appliances, updated to 14.2 when released. Added support for multi-zones. Reserved instances now supports 3rd party offers. Server SSH fingerprints available in dashboard for OOB verification. TurnKey Backup and Migration (TKLBAM) Completely redesigned dashboard. Support for IAM role STS credentials, and vanilla Amazon S3. Reduced storage fees ($0.03/GB). Backups are now stored in regional buckets with unique prefixes. Due to supporting vanilla S3, the Hub now has a TKLBAM free plan. New billing system We now leverage Stripe to handle our billing, an industry leading payment processor who processes billions of dollars worth of transactions for thousands of companies. Integrated with end-to-end encrypted from browser to Stripe, your credit card details never touch the Hub. The Hub now has stream-lined upgrade/downgrade functionality, with pro-rata support, as well as free trials. Previously the Hub leveraged Amazon DevPay for billing as well as TKLBAM storage. We've developed a migration mechanism to ease the move, as well as providing free-upgrades / discounts. Amazon marketplace integration Users who have instances deployed via the Amazon marketplace can now register them with the Hub, and get the standard TKLBAM plan as well as support enabled in their account. As usual, if you have feedback or ideas for improvement, please send it our way. The TurnKey Hub lives at: https://hub.turnkeylinux.org Blog Tags:  news aws backup ec2 cloud hub tklbam [Less]

Wow, has it really been almost a month since I announced v14.2 Core?! Looks like it has! Time flies when you're having fun I guess... :) I'm pleased to announce 27 new updated appliances that have are now on the mirror. As per usual, these ... [More] appliances are all available for download in a range of builds. Get them now via the appropriate links on the relevant appliance pages (specific appliance page links provided below). All the new appliances will launch by default from the Hub. Also there are some other news to share; including a newer version of Adminer, as well as a (somewhat minor) confconsole bug fix. Unfortunately, OpenStack builds are still a work in progress and the Marketplace images are still coming, but hopefully we'll get there soon. Without further ado, let's round up the first batch of new v14.2 appliances. 27 Updated Appliances All new v14.2 appliances have version 1.0.0 of Confconsole (which has a somewhat minor bug), as mentioned in the Core announcement. As well as the usual Debian package updates. All appliances also include the other v14.2 components, such as updated Webmin and TKLBAM. All appliances that include Adminer, now have a newer version included. Hopefully the newer version has better support for PostgreSQL users (a number of you have noted that the previous version was a little limited). Read more about that below. All appliances that install components from upstream source code (i.e. code direct from the original developers) have also been updated. Where ever possible we give LTS versions precedence over "the latest", but generally they should all now include a very recent, up to date stable release. Newer Version of Adminer Ninja Debian Developer, TurnKey friend and all round nice guy; Chris Lamb has kindly updated the version of Adminer in the Debian repositories. And TurnKey Community Legend; Ken Robinson (aka DocCyblade) stepped in and tweaked the code to add it to all the v14.2 LAMP/LAPP based appliances as well as for Lighty and Nginx (and a few others). As many of you may know, the specific version of any software in Debian stable is usually locked for the duration of the release. They do get security patches and bug fixes. But those are backported to the version of the software already included in stable. However, Debian also has what is called a "backports" repository. The Debian backports repository provides a pathway to have newer software included in a stable release. It isn't perfect, as backported packages don't have the same level of testing, support and attention as packages in the "main" repo. But we've been keeping our eye on Adminer for a while. It seems pretty well constructed and Chris has done a stellar job backporting it. So we think that any potential risks are outweighed by the gains. Adminer Background Story For those of you that are interested, I'd like to share a little of the background of this update. Late last year, it looked like Adminer was close to dropping out of the Debian repositories altogether. The previous maintainer was MIA and the package was already really old (v3.3.3). In a passing conversation, I mentioned my concerns to Chris (whom I'd only just met - via email). I didn't really think much more about it, but next thing I know, Chris had stepped in and taken over the maintenance of the Debian Adminer package. He'd packaged and uploaded the latest version (v4.2.5 at the time) to 'unstable' (where all Debian packages start out). After the obligatory wait, it migrated to testing and Chris developed a Jessie backport. Soon after the newer Adminer hit backports, TurnKey Community Power Dev; Ken Robinson jumped into gear and tweaked the TurnKey buildcode to include the newer Adminer version. Thanks tons to both of you guys! You rock! Congrats to Chris (a complete aside) As a complete aside, we'd also love to congratulate Chris on his recent success in being elected as the new Debian Project Leader. I must say that I found his platform appealing and if I were a Debian Developer, I wouldn't have hesitated to vote for him too! Nice work Chris! The Fresh Appliances To get back on track, the freshly updated appliances (in alphabetical order) are: Codeigniter Collabtive Drupal7 Drupal8 e107 Elgg LAMP LAPP LigHTTPd-PHP-FastCGI Mattermost Mediawiki Mibew Moodle MySQL Nginx-PHP-FastCGI Observium OrangeHRM PostgreSQL Processmaker PunBB Silverstripe SugarCRM Tomcat Tomcat-Apache Vanilla WordPress Zurmo Please spin one (or 2 or 3 or more) up and let us know what you think. We always love feedback, but particularly constructive criticism. Confconsole Bug Fix Soon after release, a bug in the new Confconsole Hostname plugin came to light. As noted on GitHub, this issue relates to the Postfix config not being updated with the new hostname. As such it will only effect users who have Confconsole version 1.0.0+4+g18aa7e6, use it to update their hostname and wish to send email. The fixed version of Confconsole is v1.0.1. Unfortunately, it only became apparent after we had already built this latest round of updated appliances. For a moment, we contemplated rebuilding them all. But seeing as we have a ton more appliances to get through, not to mention starting work on v15.0 (rebase on Debian Stretch), we thought better of it. So instead of spending precious time rebuilding affected appliances, we decided to just push on. It's far from ideal, but it seems to us to be the best bad option. Hopefully you'll agree. As hinted above, we have released a fixed package and users can update to it via apt. To check your version of Confconsole: apt-get update && apt-cache policy confconsole Users potentially affected by this bug will see: confconsole: Installed: 1.0.0+4+g18aa7e6 Candidate: 1.0.1 Version table: 1.0.1 0 999 http://archive.turnkeylinux.org/debian/ jessie/main amd64 Packages apt-cache *** 1.0.0+4+g18aa7e6 0 100 /var/lib/dpkg/status From this, we can see that the installed version is '1.0.0+4+g18aa7e6' but the "candidate" (version that will be installed with 'apt-get install') is v1.0.1. v14.0/14.1 users would expect to see '0.9.4+153+g10511f8' installed. If you see 0.9.4..., then this bug does not affect you (but perhaps you'll want to update). For users affected by this (i.e. anyone who has manually updated confconsole or anyone using Core v14.2 or any of these 27 new appliances), the fix is as simple as updating. Do that like this: apt-get update && apt-get install confconsole If you are using v14.0 or v14.1 and wish to update, please see the docs. More to Come With a library of around 100 appliances, that means we're close to a third of the way through. I'm hoping to have another batch of 10-20 ready by next week and get them all updated (bar perhaps a couple of the extra tricky ones) by the end of the month. We'll see how that goes... Regardless, I will keep plugging away until they're all up to date! So please try them out and let us know what you think. We're especially interested in bug reports, suggested improvements (big and small) and any other constructive criticism you have for us. Please post in the comments below, or start a new thread in the forums. Bug reports and feature requests can be lodged directly to our "Issue Tracker". Blog Tags:  news development debian community appliances release stable confconsole [Less]

Wow, has it really been almost a month since I announced v14.2 Core?! Looks like it has! Time flies when you're having fun I guess... :) I'm pleased to announce 27 new updated appliances that have are now on the mirror. As per usual, these ... [More] appliances are all available for download in a range of builds. Get them now via the appropriate links on the relevant appliance pages (specific appliance page links provided below). All the new appliances will launch by default from the Hub. Also there are some other news to share; including a newer version of Adminer, as well as a (somewhat minor) confconsole bug fix. Unfortunately, OpenStack builds are still a work in progress and the Marketplace images are still coming, but hopefully we'll get there soon. Without further ado, let's round up the first batch of new v14.2 appliances. 27 Updated Appliances All new v14.2 appliances have version 1.0.0 of Confconsole (which has a somewhat minor bug), as mentioned in the Core announcement. As well as the usual Debian package updates. All appliances also include the other v14.2 components, such as updated Webmin and TKLBAM. All appliances that include Adminer, now have a newer version included. Hopefully the newer version has better support for PostgreSQL users (a number of you have noted that the previous version was a little limited). Read more about that below. All appliances that install components from upstream source code (i.e. code direct from the original developers) have also been updated. Where ever possible we give LTS versions precedence over "the latest", but generally they should all now include a very recent, up to date stable release. Newer Version of Adminer Ninja Debian Developer, TurnKey friend and all round nice guy; Chris Lamb has kindly updated the version of Adminer in the Debian repositories. And TurnKey Community Legend; Ken Robinson (aka DocCyblade) stepped in and tweaked the code to add it to all the v14.2 LAMP/LAPP based appliances as well as for Lighty and Nginx (and a few others). As many of you may know, the specific version of any software in Debian stable is usually locked for the duration of the release. They do get security patches and bug fixes. But those are backported to the version of the software already included in stable. However, Debian also has what is called a "backports" repository. The Debian backports repository provides a pathway to have newer software included in a stable release. It isn't perfect, as backported packages don't have the same level of testing, support and attention as packages in the "main" repo. But we've been keeping our eye on Adminer for a while. It seems pretty well constructed and Chris has done a stellar job backporting it. So we think that any potential risks are outweighed by the gains. Adminer Background Story For those of you that are interested, I'd like to share a little of the background of this update. Late last year, it looked like Adminer was close to dropping out of the Debian repositories altogether. The previous maintainer was MIA and the package was already really old (v3.3.3). In a passing conversation, I mentioned my concerns to Chris (whom I'd only just met - via email). I didn't really think much more about it, but next thing I know, Chris had stepped in and taken over the maintenance of the Debian Adminer package. He'd packaged and uploaded the latest version (v4.2.5 at the time) to 'unstable' (where all Debian packages start out). After the obligatory wait, it migrated to testing and Chris developed a Jessie backport. Soon after the newer Adminer hit backports, TurnKey Community Power Dev; Ken Robinson jumped into gear and tweaked the TurnKey buildcode to include the newer Adminer version. Thanks tons to both of you guys! You rock! Congrats to Chris (a complete aside) As a complete aside, we'd also love to congratulate Chris on his recent success in being elected as the new Debian Project Leader. I must say that I found his platform appealing and if I were a Debian Developer, I wouldn't have hesitated to vote for him too! Nice work Chris! The Fresh Appliances To get back on track, the freshly updated appliances (in alphabetical order) are: Codeigniter Collabtive Drupal7 Drupal8 e107 Elgg LAMP LAPP LigHTTPd-PHP-FastCGI Mattermost Mediawiki Mibew Moodle MySQL Nginx-PHP-FastCGI Observium OrangeHRM PostgreSQL Processmaker PunBB Silverstripe SugarCRM Tomcat Tomcat-Apache Vanilla WordPress Zurmo Please spin one (or 2 or 3 or more) up and let us know what you think. We always love feedback, but particularly constructive criticism. Confconsole Bug Fix Soon after release, a bug in the new Confconsole Hostname plugin came to light. As noted on GitHub, this issue relates to the Postfix config not being updated with the new hostname. As such it will only effect users who have Confconsole version 1.0.0+4+g18aa7e6, use it to update their hostname and wish to send email. The fixed version of Confconsole is v1.0.1. Unfortunately, it only became apparent after we had already built this latest round of updated appliances. For a moment, we contemplated rebuilding them all. But seeing as we have a ton more appliances to get through, not to mention starting work on v15.0 (rebase on Debian Stretch), we thought better of it. So instead of spending precious time rebuilding affected appliances, we decided to just push on. It's far from ideal, but it seems to us to be the best bad option. Hopefully you'll agree. As hinted above, we have released a fixed package and users can update to it via apt. To check your version of Confconsole: apt-get update && apt-cache policy confconsole Users potentially affected by this bug will see: confconsole: Installed: 1.0.0+4+g18aa7e6 Candidate: 1.0.1 Version table: 1.0.1 0 999 http://archive.turnkeylinux.org/debian/ jessie/main amd64 Packages apt-cache *** 1.0.0+4+g18aa7e6 0 100 /var/lib/dpkg/status From this, we can see that the installed version is '1.0.0+4+g18aa7e6' but the "candidate" (version that will be installed with 'apt-get install') is v1.0.1. v14.0/14.1 users would expect to see '0.9.4+153+g10511f8' installed. If you see 0.9.4..., then this bug does not affect you (but perhaps you'll want to update). For users affected by this (i.e. anyone who has manually updated confconsole or anyone using Core v14.2 or any of these 27 new appliances), the fix is as simple as updating. Do that like this: apt-get update && apt-get install confconsole If you are using v14.0 or v14.1 and wish to update, please see the docs. More to Come With a library of around 100 appliances, that means we're close to a third of the way through. I'm hoping to have another batch of 10-20 ready by next week and get them all updated (bar perhaps a couple of the extra tricky ones) by the end of the month. We'll see how that goes... Regardless, I will keep plugging away until they're all up to date! So please try them out and let us know what you think. We're especially interested in bug reports, suggested improvements (big and small) and any other constructive criticism you have for us. Please post in the comments below, or start a new thread in the forums. Bug reports and feature requests can be lodged directly to our "Issue Tracker". Blog Tags:  news development debian community appliances release stable confconsole [Less]

Wow, has it really been almost a month since I announced v14.2 Core?! Looks like it has! Time flies when you're having fun I guess... :) I'm pleased to announce 27 new updated appliances that have are now on the mirror. As per usual, these ... [More] appliances are all available for download in a range of builds. Get them now via the appropriate links on the relevant appliance pages (specific appliance page links provided below). All the new appliances will launch by default from the Hub. Also there are some other news to share; including a newer version of Adminer, as well as a (somewhat minor) confconsole bug fix. Unfortunately, OpenStack builds are still a work in progress and the Marketplace images are still coming, but hopefully we'll get there soon. Without further ado, let's round up the first batch of new v14.2 appliances. 27 Updated Appliances All new v14.2 appliances have version 1.0.0 of Confconsole (which has a somewhat minor bug), as mentioned in the Core announcement. As well as the usual Debian package updates. All appliances also include the other v14.2 components, such as updated Webmin and TKLBAM. All appliances that include Adminer, now have a newer version included. Hopefully the newer version has better support for PostgreSQL users (a number of you have noted that the previous version was a little limited). Read more about that below. All appliances that install components from upstream source code (i.e. code direct from the original developers) have also been updated. Where ever possible we give LTS versions precedence over "the latest", but generally they should all now include a very recent, up to date stable release. Newer Version of Adminer Ninja Debian Developer, TurnKey friend and all round nice guy; Chris Lamb has kindly updated the version of Adminer in the Debian repositories. And TurnKey Community Legend; Ken Robinson (aka DocCyblade) stepped in and tweaked the code to add it to all the v14.2 LAMP/LAPP based appliances as well as for Lighty and Nginx (and a few others). As many of you may know, the specific version of any software in Debian stable is usually locked for the duration of the release. They do get security patches and bug fixes. But those are backported to the version of the software already included in stable. However, Debian also has what is called a "backports" repository. The Debian backports repository provides a pathway to have newer software included in a stable release. It isn't perfect, as backported packages don't have the same level of testing, support and attention as packages in the "main" repo. But we've been keeping our eye on Adminer for a while. It seems pretty well constructed and Chris has done a stellar job backporting it. So we think that any potential risks are outweighed by the gains. Adminer Background Story For those of you that are interested, I'd like to share a little of the background of this update. Late last year, it looked like Adminer was close to dropping out of the Debian repositories altogether. The previous maintainer was MIA and the package was already really old (v3.3.3). In a passing conversation, I mentioned my concerns to Chris (whom I'd only just met - via email). I didn't really think much more about it, but next thing I know, Chris had stepped in and taken over the maintenance of the Debian Adminer package. He'd packaged and uploaded the latest version (v4.2.5 at the time) to 'unstable' (where all Debian packages start out). After the obligatory wait, it migrated to testing and Chris developed a Jessie backport. Soon after the newer Adminer hit backports, TurnKey Community Power Dev; Ken Robinson jumped into gear and tweaked the TurnKey buildcode to include the newer Adminer version. Thanks tons to both of you guys! You rock! Congrats to Chris (a complete aside) As a complete aside, we'd also love to congratulate Chris on his recent success in being elected as the new Debian Project Leader. I must say that I found his platform appealing and if I were a Debian Developer, I wouldn't have hesitated to vote for him too! Nice work Chris! The Fresh Appliances To get back on track, the freshly updated appliances (in alphabetical order) are: Codeigniter Collabtive Drupal7 Drupal8 e107 Elgg LAMP LAPP LigHTTPd-PHP-FastCGI Mattermost Mediawiki Mibew Moodle MySQL Nginx-PHP-FastCGI Observium OrangeHRM PostgreSQL Processmaker PunBB Silverstripe SugarCRM Tomcat Tomcat-Apache Vanilla WordPress Zurmo Please spin one (or 2 or 3 or more) up and let us know what you think. We always love feedback, but particularly constructive criticism. Confconsole Bug Fix Soon after release, a bug in the new Confconsole Hostname plugin came to light. As noted on GitHub, this issue relates to the Postfix config not being updated with the new hostname. As such it will only affect users who have the affected version of Confconsole (1.0.0+4+g18aa7e6 aka v1.0.0), use it to update their hostname and wish to send email. The fixed version of Confconsole is v1.0.1. Unfortunately, it only became apparent after we had already built this latest round of updated appliances. For a moment, we contemplated rebuilding them all. But seeing as we have a ton more appliances to get through, not to mention starting work on v15.0 (rebase on Debian Stretch), we thought better of it. So instead of spending precious time rebuilding affected appliances, we decided to just push on. It's far from ideal, but it seems to us to be the best bad option. Hopefully you'll agree. As hinted above, we have released a fixed package and users can update to it via apt. To check your version of Confconsole: apt-get update && apt-cache policy confconsole Users potentially affected by this bug will see: confconsole: Installed: 1.0.0+4+g18aa7e6 Candidate: 1.0.1 Version table: 1.0.1 0 999 http://archive.turnkeylinux.org/debian/ jessie/main amd64 Packages apt-cache *** 1.0.0+4+g18aa7e6 0 100 /var/lib/dpkg/status From this, we can see that the installed version is '1.0.0+4+g18aa7e6' (aka "v1.0.0") but the "candidate" (version that will be installed with 'apt-get install') is v1.0.1. v14.0/14.1 users would expect to see '0.9.4+153+g10511f8' installed. If you see 0.9.4..., then this bug does not affect you (but perhaps you'll want to update). For users affected by this (i.e. anyone who has manually updated confconsole or anyone using Core v14.2 or any of these 27 new appliances), the fix is as simple as updating. Do that like this: apt-get update && apt-get install confconsole If you are using v14.0 or v14.1 and wish to update, please see the docs. More to Come With a library of around 100 appliances, that means we're close to a third of the way through. I'm hoping to have another batch of 10-20 ready by next week and get them all updated (bar perhaps a couple of the extra tricky ones) by the end of the month. We'll see how that goes... Regardless, I will keep plugging away until they're all up to date! So please try them out and let us know what you think. We're especially interested in bug reports, suggested improvements (big and small) and any other constructive criticism you have for us. Please post in the comments below, or start a new thread in the forums. Bug reports and feature requests can be lodged directly to our "Issue Tracker". Blog Tags:  news development debian community appliances release stable confconsole [Less]

Just shy of a year since our v14.1 release I am relieved to announce that Core v14.2 is finally ready for prime time! It's been a while in the making, but v14.2 Core is now available for immediate launch in the cloud via the Hub. Amazon MarketPlace ... [More] builds are on the way too, although no ETA at present. (Almost) all of the other builds (e.g. ISO, OVA, Xen, Proxmox etc.) can also be downloaded from the Core appliance page. Alternatively, all the currently appliance builds are available for direct download from one of our mirrors. The highlights for this release include, a significant confconsole update, as well as new versions of TKLBAM and Webmin. It will also include a new OpenStack build courtesy of Tomas (from 'Home at Cloud'). Why just Core? Unlike our last release, this one will be staged. We are releasing v14.2 Core independently, with others coming soon. The other appliances will be released in batches, as they are ready. I am hoping to release the first batch within weeks. I can't promise anything, but if you have a specific appliance that you'd really love to see a new version of, please comment below and I'll do my best to prioritise it's update and release. The more specific you can be about what you want/need, the better. Confconsole - new and improved v1.0.0 Beyond, the staged nature of this release, the other most significant change in v14.2 is a major revamp of Confconsole (including some reasonable docs too). You can read all about Confconsole and the new v1.0.0 features in the docs here, but I have noted some highlights below. The latest development has primarily been done by Anton Pyrogovsky and Stefan Davis. I had a fair bit of involvement in the Let's Encrypt component. But it wouldn't have been the same without community powerhouse; Ken Robinson. Ken kindly devoted a ton of time and effort to testing and feedback. Thanks to all of you, but especially you Ken! You rock man! :) Confconsole v1.0.0 highlights Let's Encrypt integration: You've been asking for it for ages, now here it is! We've finally integrated an easy way to get free Let's Encrypt SSL certificates and bundled it with TurnKey OOTB. Just fire up Confconsole from the commandline and look for it in the "Advanced" menu. Full docs are here. Mail relay configuration: Another feature that has been asked for, is easy email SMTP relay configuration. Actually we've done one better. We have researched the available third party options and have concluded that SendinBlue are currently providing the best mix of features and value for money. So we've made SendinBlue config super simple! Just sign up for a free SendinBlue account and after a few keystrokes in Confconsole, and you're away! On the other hand, we don't like to lock anyone in, so alternate custom SMTP relay configuration is also straight forward. Again, look for it in the Confconsole "Advanced" menu. Full docs are here. Other highlights: There's quite a bit of other added functionality, but particular highlights for me are the Blog Tags:  news development debian community appliances release stable confconsole [Less]