RPI setup scripts need update

[bbulkow]

Here is a list of things that I know about that have changed or need attention

• [ ] System image must be based on 64-bit OS. Installed with 64-bit Raspberry PI OS Lite (no graphics), bullseye based, assume the graphics version works fine too. It is possible that 32-bit works, but not certain, long story.
• [ ] There may be system differences based on the OS change, but I haven't seen any yet. For example, we still need the config to save against ARP. Python2 no longer exists but I believe all scripts are python3 anyway. Anything in python should probably be tested.
• [ ] Installed JDK must be Java 17, notably Temurin 17 LTS for 64-bit arm. I installed this by adding the Temurin repository to the sources then doing a straight apt install. This page is a starting point but doesn't have the repo instructions (not sure where I found those). https://adoptium.net/installation/ I prefer adding the repo because then you get security updates. Temurin is not in the standard RPI distributions. The benefit of using the repo is you automagically get the correct package for the OS you're on (32bit vs 64bit arm).
• [ ] all installations will be done from the 'chromatik' directory instead of 'oldlx', so I have copied the old versions of pi_setup to this directory so they can be modified at will.
• [ ] Root level documentation, and documentation in the chromatik directory, may need updates for installation. Assume all the other documents (how to run, etc) are getting fixed, but I see there's a doc file in pi_setup
• [ ] Let's not have multiple users (pi and entwined). I have used the pi user for my first install. Two users is confusing.
• [ ] I have changed the name of the lx-headless restart script, because it's not LX anymore, and I think I changed the spot where it gets installed. There is an outstanding bug about the service script but mark and I are working on that (the current script works but only because it has a sleep 10 in it).
• [ ] mvn must be set up and running correctly. It is common to just copy a version of the binaries, I believe I did an apt install maven though, so took the slightly out of date version from the distro. I think it's the only prerequisite for Chromatik itself, but I could be missing one.
• [ ] numpy must be installed in python for the installation install scripts. There might be another one. We did not do a requires script because really there was only one (or two) python modules required.
• [ ] Before running, chromatik/install.sh must be run. This does the compilation (and I might change the name). This creates a directory ~/Chromatik for run-time use.
• [ ] There is a license step, because all production machines need a chromatik license. We have some notes about how to do that (you create a .license file and it's tied to the machine somehow). If the license file isn't found chromatik starts but doesn't do anything, which I have asked mark about last night and presumably will fix (so we can have alerting). No network is required to run but I think you need network to create a license file. I don't think Mark documented how to do a license for a headless run so this might require asking him again.
• [ ] As a note, the configuration in "Config.java" no longer exists. We have most of the config files covered - for example, there will be a well known named file in the Chromatik directory which will be the inital autoplay file. The only one I don't know about right now is the Canopy configuration. As of writing, that's in a Java file :-( but carolyn has a task to move it to a JSON file which won't need a compile, we'll have to add that to the install directories.
• [ ] Before running, the installation itself (fixtures, project files, etc) must be installed. Like the old system, this is in installations/install.sh for basic use, and installations/install_production.sh for production use (which is where the pi_setup scripts get called from. The system is much simpler than it used to be - fewer files, fewer scripts.
• [ ] If we wish to ever run Chromatik from the pi itself (which should work fine with Chromatik), we'd want to install the base image using graphics and actually test it. It should work fine.

[mizpoon]

can we get a license that doesn't need manual activation? also install.sh doesn't exist I will add the latest pi_setup.sh, but you should test it out as I don't know how to actually get chromatik to run

[mizpoon]

Also I got 10.0.0.10 to work (ssh pi@10.0.0.10), but canot get pi.local or 192.168.10.1 to work something wrong with networking still