Alternative Installation Strategies - MikaylaFischler/cc-mek-scada GitHub Wiki
Off-Line Installation
[!NOTE] This page is a work-in-progress.
When you are unable to have HTTP enabled on a multiplayer server, you will need to revert to other installation methods.
- Drag-and-drop the released bundle files
- Having an admin/mod/someone with permissions load the files directly onto your computers in the server (and optionally redistribute with disks)
- Drag-and-drop the folders/files onto the computers (and optionally redistribute with disks)
Release Bundles
Attached to all releases starting with v1.8.18-beta
are a set of large .lua
files. Here is an example list of the released files for v1.8.18-beta
:
common_v1.8.18-beta.lua
coordinator_v1.8.18-beta.lua
pocket_v1.8.18-beta.lua
reactor-plc_v1.8.18-beta.lua
rtu_v1.8.18-beta.lua
supervisor_v1.8.18-beta.lua
On each computer, you'll drag over the file beginning with "common" and the one matching the application you wish to install. Note that "drag over" means click and drag the file from your actual computer running the game into the game window itself onto the open terminal of the ComputerCraft computer you want to load it on to.
Once both are transferred (one at a time due to size), you will run the one with the application in its name and everything will unpack from there. Once that is completed, you'll find ccmsim
(cc-mek-scada installation manager) as the substitute for the HTTP-dependent ccmsi
application. It has fewer features due to no network connectivity, but still lets you manage your install.
Supervisor example for v1.8.18
:
- Drag over
common_v1.8.18-beta.lua
- Drag over
supervisor_v1.8.18-beta.lua
- Run
supervisor_v1.8.18-beta.lua
Future updates would be done via first executing ccmsim update-rm
, which would delete the application and leave configurations. You would then repeat your initial process of dragging over the two .lua
bundle files and install as you first did by running the one with the application in its name. Doing it this way preserves your configuration and log file. If you have a space issue, delete your log file (usually log.txt
).
Supervisor update example for v1.8.18
:
ccmsim update-rm
- Drag over
common_v1.8.18-beta.lua
- Drag over
supervisor_v1.8.18-beta.lua
- Run
supervisor_v1.8.18-beta.lua
Transferring via Disks
Installations can be copied from computer to computer via disks, though you will need to increase the size of the disks in the ComputerCraft configuration, as the default size as of writing this is far too small. This is intended for those who are unable to use the installer due to HTTP being disabled in servers where they cannot enable it or successfully request it to be enabled, but are able to get the disk size increased. Alternatively, folders can be drag-and-dropped into ComputerCraft (if your version of ComputerCraft supports that).
Currently, the following folders would need to be copied and transferred via disks:
scada-common
graphics
lockbox
- the app directory (
reactor-plc
,rtu
,supervisor
,coordinator
orpocket
)
Then, the following files must be copied as well from the root directory:
startup.lua
initenv.lua
configure.lua
If your disk is named 'disk', you can run the following command from a computer with an installed app. A reactor-plc
app is used as an example, so you would replace that below with the app you are transferring. You could store all the apps on one disk if there is space, and only copy back the ones you need. The three common directories (scada-common
, graphics
, lockbox
) are shared by each app so you would only need one copy of them.
For apps still using legacy config.lua files, it is suggested to make sure you aren't redistributing to others a non-default config.lua file, only a default one from a fresh, unconfigured install.
cp scada-common graphics lockbox reactor-plc startup.lua initenv.lua configure.lua /disk/