Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blocks:manage_script_directory [2024-03-20 14:01] mattias [First time installation] |
blocks:manage_script_directory [2024-04-24 06:58] (current) mattias |
||
---|---|---|---|
Line 1: | Line 1: | ||
=====Manage the script directory===== | =====Manage the script directory===== | ||
- | We keep the latest version on our script environment in our [[https:// | + | We always |
+ | |||
+ | :!: Before doing anything with an existing script directory in a working system, it is always recommended to make a security copy of the / | ||
- | :!: Before doing anything with an existing script directory in a working system, it is always recommended to: | ||
- | * stop the server | ||
- | * make a security copy of the / | ||
====First time installation==== | ====First time installation==== | ||
- | From a freshly installed Blocks, one should also install an up-to-date version of the files describing the Blocks scripting environment | + | From freshly installed Blocks, one should also install an up-to-date version of the files describing the Blocks scripting environment, dependencies |
- | ====Get the files==== | + | ===Get the files=== |
- | There are a few different methods to obtain the files, but in general for any desktop environments one can download a zip of the repo by clicking the green < | + | There are a few different methods to obtain the files, but in general for any desktop environments one can download a compressed .zip archive |
+ | |||
+ | ===Decompress the files=== | ||
+ | When this file is decompressed it will result in a new directory, blocks-script-master. | ||
+ | |||
+ | ===Merge the files into the script directory=== | ||
+ | Navigate inside this directory and select all files and directories. Now one can drag/copy all the files into the / | ||
- | ====Update==== | + | ====Update |
+ | An update of the files is the same thing as with the fresh install for any desktop environment. For linux there is a script that automates this: | ||
+ | ===Production Linux Deskotop environments=== | ||
+ | For production Linux environments provision with our image, one can use the update_scripts.sh that automates the whole procedure including making a security copy and stopping the server. Before running the script, cd into the /script/ directory in the cli. The script has some dependencies that may be missing in i.e virtual machines not provisioned by the image. | ||
+ | < | ||
+ | pixi-server@pixi: | ||
+ | </ | ||
+ | Run the script: | ||
+ | < | ||
+ | pixi-server@pixi: | ||
+ | </ | ||
===Linux Desktop=== | ===Linux Desktop=== | ||
===Linux CLI=== | ===Linux CLI=== |