TKLDEV Setup and Note taking

TKLDEV is the build system for TurnkeyLinux applications.  It is very capable and somewhat easy to work with. 

I am wanting to build some more capabilities into TKLDEV and so today I have started again with the process of working with it and shold be able to proceed with modifying it.

To do so,  I installed from the TurnkeyLinux Hub, a TKLDEV Micro instance.  As the name holds, it is a pretty small build.  1 GB ram,  10gb of HD space.  Cost is not low:  About $12 per month, but it can be killed pretty easily and built again.

First Task:

Working through the lack of documentation with TurnkeyLinux.

This can be quite problematic.  However, if you read, and reread, forum entries, look at github documentation, and test and try things, things can work out.

There are several steps required for actually getting BuildTasks to start working.  (Somewhat dated now). 

I just removed the VMWARE OVF Tool and will put in a separate notation.  It is not working as of March 2021Interpret the correct Syntax inorder to get various BT-s working

    1. Hint:  actually type "./" where instructed to do so.
    2. ie: "./bt-iso"  or "./bt-vm"
    3. Interpret the correct Syntax inorder to get various BT-s working
        1. Hint:  actually type "./" where instructed to do so.
        2. ie: "./bt-iso"  or "./bt-vm"

Issues:

Interpret the correct Syntax inorder to get various BT-s working

    1. Hint:  actually type "./" where instructed to do so.
    2. ie: "./bt-iso"  or "./bt-vm"


Verification of ISO's 

(best done by also downloading the hash file that is stored with the mirror, and which should be generated also by tkldev upon ISO build)

Building from TurnKey ISOcd 

Note that if there isn't already a Core ISO and matching hash file in /mnt/isos buildtasks will download it from the TurnKey mirror.

When that's finished, you should find an official Core TurnKey ISO (and matching hash file) in /mnt/isos/ and a Core container build in /mnt/builds/container/

Turnkey Mirrors are sometimes downloaded rather than ISO simply generated  (see note 2 lines above)

Building from your own ISO

cd buildtasks/
./bt-iso new-app


Once that runs, simply run the relevant bt script. Don't forget to install the relevant dependencies.

./bt-vm new-app-14.2-jessie-amd64

ToDo's:

  • Get Git Working
  • Make Variations to build scripts
  • Practice, Practice Practice
  • Get Shortlist of "New App Setup"

 

Turnkey Mirror Links

 

Assorted Links of note:  

 

 

Issues at hand:  

  • Cloning
  • Making New Code
  • Using the new code
  • Integrating into the repository or simply using the repository as a base, but using local changes

Update Note 10-22-2019

  • I have gone through the OVFTOOLS notations above to be clear as to process.
    FKIT has made a good video here:  https://www.youtube.com/watch?v=vseorvzwu-k
  • I have started forking my own repositories and working on new builds.  Doing one for Joomla3 right now.  Forking TKLDEV and Buildtasks and bringing them in to see if they work with few changes.  First MAKE is running now.
  • Did also upgrade my Putty Application to 64BIT and current.
  • Waiting for the build as we speak.  Takes a while on a small server.
  • Once build it is important to look into the /mnt folder for names created, but also to understand the bt-vm command above for the first build.

 

Posted in Open Source Notations

Print Email

Wildnet Blog Accordion

Recent Work with a VPN router

Recent Work with a VPN router

Sometimes a small project is not so small.  For some reason my Odoo Server does not pass through my Comcast Home system at all well.  Solution was to put a dedicated PC into my office... but, I didn't want to just have RDC available for all comers (who sure came fast).

I remembered that I had a VPN equipped router.  I won't say the model.  Anywy, the company who made it was aquired and the aquiring company, as they are want to do, killed most support links about the router.  Turns out there were several other routers that used the same software for access, and yes, I got it too work.  Honestly, I think it is just a small step in security, not a big one.

In the end I was able to get the correct VPN client by simply downloading the off of a link to a later, still supported router from the company.  The client is no where as nice as OPENVPN for granularity, but it does work.  

I also found that "NOIP"  (https://noip.com) provides a functional way to address a dynamically assigned IP address.  There are a few other ways but this was the most direct and within the budget.

Things are working for now despite the EOL from the router builders new owner.  

I had mentioned in the earlier version of this post that it might be interesting to rewirte the firmware to the Router, and get it working as a OPENVPN router.  That remains interesting but likely easier to do that with some other hardware and software.

EOL is one of the LEAST SUSTAINABLE parts of IT and I do not like the planned obsolesence which rules the industry.

Read more

Systems under the skin of TKL

Systems under the skin of TKL

Dissecting and understanding a build process is complicated.  It is very nice to be able to look under the skin from time to tim.

At present I am needing to adjust approaches as past ways of adapting have been left by the road (not by me).  Studying a bit about what takes place in alternative builds that I may adapt to is an approach that I need to take.

Turnkeylinux is built from 2 sets os structures.  What goes out, their "apps" are prebuilt systems.
Inside of each app though are many and various components.

https://github.com/turnkeylinux-apps/

https://github.com/turnkeylinux/fab  (the component sets)

consists of 68 Repositories at present, including...

https://github.com/turnkeylinux/fab

https://github.com/turnkeylinux/buildtasks

https://github.com/turnkeylinux/inithooks

https://github.com/turnkeylinux/buildroot

https://github.com/turnkeylinux/turnkey-paths

and many more.

TKLDEV is a good way to start to understand the process as TKLDEV will build new APPS and the process can be tracked.  Still following it is complicated.

This is left here as a study note to come back to.

A good entry point to Turnkeylinux is of on their "Help Sought" page"

Read more

MageBridge removed as well

MageBridge removed as well

Looking back at my notes, I started working with Magebridge (from Yireo) in at least 2013 and perhaps earlier.

It was a great idea fraught with difficulties.  Its purpose was to bridge Magento into Joomla

Magebridge discontinued by Yireo a few years ago now, but on my side I just disabled it.  Yireo discontinued because of the forthcoming Magento 2 and all the changes there.  I am not convinced it could not have been brought forward, but I think the greater issue was the extreme complication the program was itself.

Today, I gave it one last try.  Nope...  no go.  And now I am free.

Everything has been removed (uninstalled yes) including Compnents, Plugins, Packages, Libraries, Menu Items, Modules etc etc etc.  As the attempt also disabled the Magento server I also have a full restore running there as well (to last night's state).  I will likely kill the Magento server next.  Also not worth the hassle.

The site is fast.  I did resurrect for the time being Dynamic404 from Yireo (Yireo has gone away from all things Joomla).  It seems to have some good rerouting and be able to redirect what it cannot find in the overt redirection tables (lets see how that goes).

This is not, of course, big news, but it is news about Old and New.  I have long wanted everything to stay functioning, but sometimes we have to clear the decks...  They are clear now and we won't try that again.  (I log that I spent almost 4 hours on this attempt this morning).

And so it goes.

Read more

Magento Sunset

Magento Sunset

I have been running Magento since about 2012 with 1.3x in my memory bank. Up to 1.9x now and really just using Magento as a repository now.

Magento 2.x (2.3x to be precise) is here.  It does not work, at present, with this CMS system so I have a linkage taking place through Filemaker from J2Store to Magento and by extension to Odoo.

I will quite likely just take the Magento system down.  It will not be supported with updates after this coming June and the time investment of getting 2.x running and keeping it running does not seem available just now).  We will see.

Anyway, for now, I am going to start redirecting the URL's to land into this system.  Lets see what a pain that becomes.  Likely worth the effort but also perhaps now.

Sad, but Magento was aquired by Adobe and like Odoo, they are making it more and more difficult to use it as a Open Source software.  Not that either are impossible, but the reigns are steering the team towards privation.

Somewhat the nature of things these days I will say.

All good software, just a bit too time intensive.

Read more

Magento - Odoo - OCA Connector

Magento - Odoo - OCA Connector

This is a very functional system which brings the ability to work the "backend" of Magento by actually building and purchasing items you sell,

  • Functionally you get all of the aspects of Odoo, including CRM, Product Management and more
  • You also get the great E-Commerce capabilities of Magento, and its increditble extensability.

(to do:  more detail)

Read more

Joomla3 Appliance - Powered by TurnKey Linux