TurnKey v14.0 RC1 is LIVE! (aka we need YOU!)

I'm not sure where we will be up to by the time your free, but even if we are close to a release anything that you can contribute would be super awesome! Besides I doubt we'll be so close to release that we couldn't hold off if you have something extra good for us! :)

The WordPress appliance has received a lot of love from a savy community member so the new version will be a big improvement anyway! But if you have more good ideas then that would be great!

Going forward: Assuming that I can successfully get this release out the door (which the signs are looking quite good so far...). Then I will be in charge of future releases too. I am hoping that that will result in more regular releases and a more responsive TurnKey (in the sense of TurnKey being more responsive to community input). Not that Alon hasn't done a great job with previous releases but he has a ton of stuff on his plate and I think that more pure programming (including developments such as the Hub) are more his passion. So I am hoping the end result will be a win-win all round! :)

Thanks Jeremy...I'm sure the release will be a success in your deft hands.

I've got about 3 weeks of client work and tax backlog to get through and then I plan on investing time in TKLDEV and the LAMP appliance. I build multi-site WordPress appliances based on the LAMP stack. If things go smoothly I'll try to kick in on the WordPress appliance as well even if it's just to allocate a day to do testing.

would it help in finding issues if we tested in place upgrades?

if so then is there a jessie sources list for turnkey/jessie ?  or should we test with out that.

Adminer itself is on https://<lamp-ip>:12322/ as per previous phpMyAdmin default.

Is Adminer Editor going to be pre-installed as well?

Whilst we understand that many TKL users will miss phpMyAdmin, we believe that now is a good time to change. Liraz suggested this change almost a year ago and with the Jessie issue (linked above) now seemed like a good time to switch. Adminer is also much lighter weight and works lightening fast!

Hopefully users will adjust to this change and worst case you can always install phpMyAdmin (easiest is from Debian repos).

The current LAMP and LAPP appliances will very soon have Adminer included (when built with TKLDev v14). My fork of the code (which I will be issuing a pull request for shortly) builds successfully and has passed preliminary testing. Hopefully by tomorrow you will all be able to test it yourselves! :)

"use full disk" solution solves it for me for now.  Can't do an LVM install in Jessie on my side.  Not focused on that just commenting.

But then I noticed that during my install it installed grub to sda (I'm using default IDE vHDD) whereas yours is vda (I assume virtio?).

So I ran thorough it again and I can reproduce your issue but only with a virtio vHDD; with an IDE one it works fine... So whilst there is obviously a bug somewhere; its a weird one...!

It might be worth trying installing to an IDE vHDD and then when you reboot (or sometime later) reconnect it as virtio and see if that works. It should work AFAIK but I've never done it with a Linux machine - have done it with Win VMs & works fine so long as you preload the drivers; which shouldn't be an issue with Linux.

Or are you using the manual installer?

Like falling off a bike, you don't really forget! Thanks for the quick refresher! I hope to have some time this weekend to fiddle around. Think I'll test a few builds then work on RT

Jeremy and Team fixed the main core files so if you just install TKLDEV (from the JESSIE RC1 Link at the HEADER of this POST !) then run tkldev-setup (following this flow below) and you should be good to go.

My flow notes:

After App Install (VM)

then login via SSH  (I recomend BitVise SSH Client)

then Run TKLDEV-SETUP with these lines.

cd /usr/local/sbin

wget https://raw.githubusercontent.com/turnkeylinux-apps/tkldev/master/overlay/usr/local/sbin/tkldev-setup

chmod +x tkldev-setup

./tkldev-setup

Then get out of "/usr/" and go to "/turnkey/"
 

cd /turnkey/fab

dir

verify you have Common (directory) there (if it is there then tkldev-setup seems to have worked)

cd products

dir

(Core should be there from tkldev-setup)

Then pull your Git into Products

IE, LAPP if you want to test the system  (the following will lay a LAPP directory next to CORE

git-clone https://github.com/turnkeylinux-apps/lapp.git

If you are testing, then clean your Git records just because you don't need them as you are not developing in this mode to my understanding (I suppose you can though)

cd (app folder name)
rm -rf .git

If you are developing however keep your Git (dont run the rm command above)

then just build it.  

make

If you changed something in your folder then to run a new Make use this command (per Jeremy)

make clean && make

I recomend coffee and time if it is a big package.

Worked so far for me anyway.

yeah was hoping RT would have been a good pick for work and I could marry the two. I'll still finish it. Will be a good refresher in app building.

FYI, as your suggested I posted an issue on the tracker. https://github.com/turnkeylinux/tracker/issues/376

TBH I did wonder what happened to you. You were very active and then dropped off the radar... I know what it's like sometimes with open source dev... It sometimes feels like you are shouting into the void; like you are all on your own! It's a little disappointing that you didn't even get any feedback, especially when there were people asking for the appliance...

I haven't tested your code or ISO but I just had a quick look at your code on GitHub. Seeing as you went with the package management version it should be pretty easy to update. The only thing I would do is remove the backports bit and add those packages (now we're on Jessie they should be the same or similar in the main repo) to plan/main and you should (in theory) be good to go! If I'm right then perhaps it's not too much work to get it ready to add it to the library!? What do you think? If you want to go that path, please post a new issue on the tracker regarding RT and I'll tag it appropriately. Actually if you'd like do that regardless. Even if we don't get it in this time, you've done most of the heavy lifting already so perhaps someone else might step up even if you've had enough of it...

And/or if you want to help with other updates to appliances then we'd be more than happy to have some help! :) We have actually done a lot of the appliances but if you want me to allocate one or 2 then I'm more than happy to. Otherwise if you have a pet appliance that you'd like to work on then please let me know.

I did start RT 4.0 (https://github.com/DocCyblade/TKL-RT40) months back hoping that my work would step up and use some open source software. They went in another direction. I may update the code to use v14 of TKLDev once it's released. I was thinking I would have some others that would have jumped in and helped but looks like not dice, however according to source forge there was 50 some downloads so it did see some lookers, but no feed back :-(   

Most my builds are just custom templates I use for customers in my side biz. I take the standard LAMP/LAPP and tweak it a bit so it has all my customization I do for every build, save some typing. I am looking at creating a custom database server with both MySQL and PostgeSQL for my own uses. 

I will have some time over the next 3-4 weeks and would like to pitch in where I can. Whats the game plan for updating the apps etc....

Has the the core devs updated the TKLDev docs for the v14 release? I need to re-read over the build processes. I think I read there was some changes to chroot etc..

Have you built anything that you'd like to share? Maybe we can squeeze it in this release if you're up for it?!

Hope to give this a spin in the next view weeks! I use TKLDev to create custom Linux builds for myself.

I recall it being 98% good.  Seemed it needed one very small manual tweak after Make.

I have not looked in a while but can do so.  I expect Joomla has moved forward a bit.  Good system for sure and need to have TKL offer a 3x version.

Will try a Jessie Make and see what comes of it.

I just posted on the other Odoo thread that you can email me your SF info (if you have an account) and I can add you to the 'TKL Community' SF project so you can upload your ISO there... (if you want?)

Also I noticed in your GitHub that you made a start on Joomla a while back. How far did you get? Is it worth building on or should we just start again?

Quite excited.  Clean install except one notice (brief of Postgresql restart) at inithook.  Modifiied from Carlos's V's excellent effort last Sept.  (Thank you Carlos for the very strong start!)

Working really well between various host situations.  Most Importantly running in SSL by default.  Toggled index.php to port 12325.  Carlos had dropped fileserver/samba in as well and seems to be running clean.  Will explore the benefits there.

Want to integrate Odoo Package rather than Git Clone as the install is quite a big one and any new Make takes quite a while.  But ISO built.

GitHub says I did 76 commits on this one.  There were some test abandonments before for sure.

If anyone would like to try I'll bet I could post to DropBox or somewhere else.  

Next I want to work on Connectors to Magento.  Should be a lot easier to integrate now that the base install is there.

To keep my forked copy up-to-date, I had to add one line...

git checkout master
git pull upstream master
git push origin master
git checkout ssl-hardening
git merge master

So something like this:

cd common
git remote rename origin upstream
git remote add origin <your-github-common-fork-url>
git branch ssl-hardening <or-similar>
git checkout branch ssl-hardening

Then hack away... :)

I recommend committing often (although you're not new to git so you probably get that already)

git add .
git commit -m "just committing some code"

Or shortcut:

gc -am "just committing some code"

Note though that the '-a' switch won't track new files, only updated ones; you still need to

git add /path/to/new/file

git add .

Hint: You may already know this but to save you a little typing when renaming a file, instead of

mv old/filename new/filename
git add new/filename
git rm ;old/filename

instead you can just do

git mv old/filename new/filename

Anyway, once you are ready to push your code to your GitHub account

git push origin ssl-hardening

Then when you have tested and are happy with your code, then log into GitHub and do your pull request

There may be some conflicts with changes going on in common but often they can be resolved by merging upstream with your branch. Personally I try to keep my local master branch up to date with upstream (then merge with any branches that I'm actively working on). So regularly do something like this (make sure that any changes are committed or stashed, otherwise they will come with you)...

git checkout master
git pull upstream master
git checkout ssl-hardening
git merge master

This week I became aware of Logjam, yet another attack on SSL.  https://weakdh.org/  Fortunately, I've been hardening my servers using information from Ivan Ristic's book Bulletproof SSL and TLS.

Now would be a good time to implement the suggestions recommended here https://weakdh.org/sysadmin.html for all the appliances using the affected applications.  Changes that affect multiple appliances should be made to common, rather than to each specific appliance.

What is the best way to setup my TKLDev 14.0 development server so that changes made to the common folders can be submitted to the developers via pull request?

Anyway, let's hope someone steps up... Or perhaps you could have a go yourself! :)

Its actually fun building these things.  I encourage others also to try.

Linux from the outside does seem daunting.  A bit like tennis just swing the racket and swing again and it comes.

We should build a Linux-Windows Dictionary to get the parrallelism.  Same for Mac etc.

Small aside to begin with:  realize that in TKLLinux you don't normally need to type the intro common in other systems of "sudo". though if you want to change user presence (say from root) you would say "su - otheruser"...  then proceed.  "exit" seems to return you to root user presence.

Not intended to scare you.  I have only done this in one situation, where there is by standard practice a dedicated "odoesque" User right running the Odoo system.  Historically was "su-ing" in to start the Odoo server within TKL".

Apache does similar and user rights are normally in the form of "www-data" in the webspace of TKL etc.

You will see this when you browse around in File Manager (at present IE and Firefox will get you in that way) which is more or less a Web Browser Java based GUI interface to look at your files.  When that doesn't work (like in TKLDEV where it is turned off) use a SSH Client.  I like "Bitvise SSH Client".  Has a built in SFTP File Exchange window that runs along side.  Free for homies.

Learning isn't bad.  Pretty much learned what I know through TKL.  Triping up once and a while is part of the process.

Have a look and provide feedback on the blog post here.

And of course thanks for joining the party! :)

Thought I'd have a go at joining this party. With the guided install on VMWARE I got a fatal error 'Unable to install grub /dev/sda5' others have mentioned this too on other VMs.

Simple solution was 'No' to the install which then prompts for a path, I just left blank an it installed OK to the default /dev/sda

I'll try to keep updating it as often as possible, but if you have any updates (appliances that build, or ones you've tested that work) please let me know.

If you find any bugs, please post on the tracker

To start with though we are just making the ISOs... Once we have the library updated then we'll release them all in all the build formats.

Hi congrats with the new release!

I see no docker build on the webpage? The v13 was available on docker too, which was great!

Can you please add docker as well, as it would be pity if you miss out this important platform.

Thank you very much!

As for MariaDB, I think that would be a good idea at some point. However as MySQL still works fine and Debian still use it as their default SQL DB M in LAMP I'm not in any real rush... It seems like a bit of work for no real obvious gain at this point. Please feel free to educate me though if there is something I've missed...

PS please excuse this delayed response I wrote this ages ago but forgot to hit post...

Using the core version now for testing, and it seems very stable.

The systemd is working very nicely (not expecting this).

Perhaps in some builds the MariaDB should be used now instead of the MySql version... 

It's probably not relevant to you and LXC but FWIW all the code that provides all the different builds is on GitHub, it's called buildtasks.

Openvz  14RC1 core version

Is it possible to get a TKL 14RC1 Core for openvz.  Or is someone busy with it ?

--- Update:

I got now a LXC  TKL14RC1 core running using the tkl-patch tool.  Now trying to clean it up.

Anyone got some ideas about the systemd services that needs to be running inside openvz or lxc container :

root@core ~# systemctl list-units -t service
UNIT                               LOAD   ACTIVE SUB     DESCRIPTION
console-getty.service              loaded active running Console Getty
cron.service                       loaded active running Regular background program processing daemon
getty-static.service               loaded active exited  getty on tty2-tty6 if dbus and logind are not available
hubdns.service                     loaded active exited  LSB: HubDNS startup and shutdown init script
kbd.service                        loaded active exited  LSB: Prepare console
networking.service                 loaded active exited  LSB: Raise network interfaces.
rc-local.service                   loaded active exited  /etc/rc.local Compatibility
resolvconf.service                 loaded active exited  Nameserver information manager
shellinabox.service                loaded active running LSB: Shell In A Box Daemon
ssh.service                        loaded active running OpenBSD Secure Shell server
stunnel4.service                   loaded active running LSB: Start or stop stunnel 4.x (SSL tunnel for network daemons)
syslog-ng.service                  loaded active running System Logger Daemon
systemd-journald.service           loaded active running Journal Service
systemd-modules-load.service       loaded active exited  Load Kernel Modules
systemd-random-seed.service        loaded active exited  Load/Save Random Seed
systemd-remount-fs.service         loaded active exited  Remount Root and Kernel File Systems
systemd-setup-dgram-qlen.service   loaded active exited  Increase datagram queue length
systemd-sysctl.service             loaded active exited  Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service     loaded active exited  Create Volatile Files and Directories
systemd-udev-trigger.service       loaded active exited  udev Coldplug all Devices
systemd-udevd.service              loaded active running udev Kernel Device Manager
systemd-update-utmp.service        loaded active exited  Update UTMP about System Boot/Shutdown
systemd-user-sessions.service      loaded active exited  Permit User Sessions
udev-finish.service                loaded active exited  Copy rules generated while the root was ro
webmin.service                     loaded active running LSB: Webmin

But it seems to be running smoothly in a  LXC container

As for the changes; configuring the admin account is already a feature request. However I think that your comment adds a lot of additional weight to the idea. I am going to update the feature request (to include enabling addons) and link to this comment of yours... :)

using tkdev etherpad iso builds.

using the iso I made a kvm using proxmox.

test pads work.

Next addons - there are many -  over 100 -  many with recent changes. It looks like some very competent coders are working on them.

To use those two things had to be changed.

1- add admin account.  [ this is from tk forum ] 

edit /opt/etherpad-lite/settings.json
insert after
    "database": "etherpad"
  },

  "users": {
    "admin": {
      "password": "changeme",
      "is_admin": true
    },
    "user": {
      "password": "changeme",
      "is_admin": false
    }
  },

2- user nodejs  needs to be able to write to etherpad-lite/node_modules .  by default can not.

chgrp nodejs etherpad-lite/node_modules
chmod 775 etherpad-lite/node_modules

Etherpad addons should be enabled by default .  There are must have ones like  list pads and  delete pads.  And over 100 others I've not tried. 

I do not yet know how to check the code and put suggested changes to git in order to help get that done.

Please note that some of the updates were done prior to the V14.0 TKLDev so were actually only tested against Wheezy. I'm pretty sure that I have made the required changes to make most of them build, but haven't actually tested them all. Please let us know if you have trouble building any of them; especially ones that are "completed_needs_review" or "completed_ready_for_qa".