| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| install:dev [2023/09/22 00:02] – [Run-time files] Replace more ftp links with https digital man | install:dev [2024/04/27 14:36] (current) – [Run-time files] Repeat the link to text.dat as Dumas Walker suggested digital man |
|---|
| - If you performed a [[dev:Git]] install (e.g. on *nix) and you opted for symbolic links to the ''[[dir:exec]]'' and ''[[dir:text]]'' directories, the only file you might need to manually update or merge would be the ''[[dir:ctrl]]/[[custom:text.dat]]'' file. All the other files should be automatically updated with your ''git pull'' command. | - If you performed a [[dev:Git]] install (e.g. on *nix) and you opted for symbolic links to the ''[[dir:exec]]'' and ''[[dir:text]]'' directories, the only file you might need to manually update or merge would be the ''[[dir:ctrl]]/[[custom:text.dat]]'' file. All the other files should be automatically updated with your ''git pull'' command. |
| - If you performed a [[dev:Git]] install (e.g. on *nix) and you did **not** opt for symbolic links, you will need to recursively copy the ''repo/exec'' and ''repo/text'' directories to your ''sbbs/[[dir:exec]]'' and ''sbbs/[[dir:text]]'' directories. | - If you performed a [[dev:Git]] install (e.g. on *nix) and you did **not** opt for symbolic links, you will need to recursively copy the ''repo/exec'' and ''repo/text'' directories to your ''sbbs/[[dir:exec]]'' and ''sbbs/[[dir:text]]'' directories. |
| - Over-write or merge-with your modified ''[[dir:ctrl]]/[[custom:text.dat]]''. If you see some corrupted text output from the terminal server or some features don't work as expected, skipping this step could be the cause. If you don't have have or expect to make any edits to your ''text.dat'' file, consider just using a 0-byte ''text.dat'' file to always [[custom:text.dat#use defaults]]. | - Over-write or merge-with your modified ''[[dir:ctrl]]/[[custom:text.dat]]'' file from [[https://gitlab.com/synchronet/sbbs/-/raw/master/ctrl/text.dat|here]]. If you see some corrupted text output from the terminal server or some features don't work as expected, skipping this step could be the cause. If you don't have have or expect to make any edits to your ''text.dat'' file, consider just using a 0-byte ''text.dat'' file to always [[custom:text.dat#use defaults]]. |
| |
| |
| |
| - From a command prompt (e.g. in your Synchronet ''exec'' directory), run: ''jsexec update'' | - From a command prompt (e.g. in your Synchronet ''exec'' directory), run: ''jsexec update'' |
| | |
| | **NOTE:**\\ |
| | The following //one-time// error message displayed by ''jsexec'' **when upgrading from Synchronet versions prior to v3.20** is expected and should be ignored: |
| | !ERROR loading configuration files: 2 (No such file or directory) opening /sbbs/ctrl/msgs.ini |
| | ... because later in the upgrade process, the ''msgs.ini''(and other) missing configuration files will be created (converted from ''*.cnf''): |
| | Upgrading Synchronet v3.1x config files to v3.20 |
| | main.cnf -> main.ini |
| | ../node1\node.cnf -> node.ini |
| | ../node2\node.cnf -> node.ini |
| | ../node3\node.cnf -> node.ini |
| | ../node4\node.cnf -> node.ini |
| | msgs.cnf -> msgs.ini |
| |
| Now you are ready to re-run the BBS and enjoy the "latest and greatest"! | Now you are ready to re-run the BBS and enjoy the "latest and greatest"! |
