admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2024-05-22 18:40:30 +00:00
parent 78ed13b24e
commit 52ccc3fe5e
3 changed files with 18 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
dist/assets/linux-server/config.json vendored
View File

@@ -4,5 +4,5 @@
"AYANOVA_DEFAULT_TRANSLATION":"en",
"AYANOVA_DATA_PATH":"/var/ayanova/data/",
"AYANOVA_LOG_LEVEL": "Info",
"AYANOVA_JWT_SECRET": "1234567MyRandom32CharacterSecret"
"AYANOVA_JWT_SECRET": "12345YourRandom32CharacterSecret"
}

12
docs/8.0/ayanova/docs/ops-install-windows-iis.md
View File

@@ -225,13 +225,15 @@ B. otherwise, If you already have a backup solution in place for your PostgreSQL
OPTIONAL EDIT:
Add a 32 character [AYANOVA_JWT_SECRET](ops-config-jwt-secret.md) property to the configuration if you want to ensure that logged in User's session can survive a restart of the AyaNova server. If this is not set AyaNova will invalidate all login tokens any time the server restarts by generating a new random JWT secret on boot.
Modify the 32 character [AYANOVA_JWT_SECRET](ops-config-jwt-secret.md) property of the configuration which ensures that the logged in User's session can survive a restart of the AyaNova server. If this is not set AyaNova will invalidate all login tokens any time the server restarts by generating a new random JWT secret on boot which under IIS happens frequently.
Change this from the default of "11111YourRandom32CharacterSecret" to be unique to your site (must be 32 characters).
```json
{
...existing properties...
"AYANOVA_LOG_LEVEL": "Info",
"AYANOVA_JWT_SECRET": "1111111MyRandom32CharacterSecret"
"AYANOVA_JWT_SECRET": "11111YourRandom32CharacterSecret"
}
```
@@ -261,7 +263,11 @@ You should see a console window open and some text that indicates the server ver
##### If the server closes immediately upon running with an error
In some cases where a critical configuration value is completely missing, the server console may display the error but close too quickly to read it. In this case you can view the message by starting AyaNova.exe manually from a command line prompt. For example if AyaNova is installed to the default location open a command prompt (press WIN-x, select "command prompt" from the menu) and type `"c:\Program Files\ayanova\AyaNova.exe"` (note the quotation marks) to run AyaNova and see the error and make the necessary changes.
In some cases where there is a critical error completely preventing AyaNova server from running, the server console may display the error but close too quickly to read it. In this case you can view the message by opening a shell / command line prompt and starting `AyaNova.exe` manually from it's program files ayanova folder.
If you see an error about the `config.json` file there is likely a comma missing or some other format issue from when it was edited in the earlier step. Double check that it's not missing a comma or has an extra comma at the end that is not required or anything else that stands out.
If you receive an error that mentions `Microsoft.NETCore.App` it may be that the .net installation did not complete properly even though the display runtimes command executed properly. In this case the issue is often resolved by redoing the .net installation instructions above.
#### 6\.2 Double-click the AyaNova App shortcut

13
docs/8.0/ayanova/docs/ops-install-windows-lan.md
View File

@@ -157,13 +157,15 @@ B. otherwise, If you already have a backup solution in place for your PostgreSQL
OPTIONAL EDIT:
Add a 32 character [AYANOVA_JWT_SECRET](ops-config-jwt-secret.md) property to the configuration if you want to ensure that logged in User's session can survive a restart of the AyaNova server. If this is not set AyaNova will invalidate all login tokens any time the server restarts by generating a new random JWT secret on boot.
Modify the 32 character [AYANOVA_JWT_SECRET](ops-config-jwt-secret.md) property of the configuration which ensures that the logged in User's session can survive a restart of the AyaNova server. If this is not set AyaNova will invalidate all login tokens any time the server restarts by generating a new random JWT secret on boot.
Change this from the default of "11111YourRandom32CharacterSecret" to be unique to your site (must be 32 characters).
```json
{
...existing properties...
"AYANOVA_LOG_LEVEL": "Info",
"AYANOVA_JWT_SECRET": "1111111MyRandom32CharacterSecret"
"AYANOVA_JWT_SECRET": "11111YourRandom32CharacterSecret"
}
```
@@ -191,11 +193,12 @@ You should see a console window open and some text that indicates the server ver
##### If the server closes immediately upon running with an error
In some cases where a critical configuration value is completely missing, the server console may display the error but close too quickly to read it. In this case you can view the message by starting AyaNova.exe manually from a command line prompt. For example if AyaNova is installed to the default location open a command prompt (press WIN-x, select "command prompt" from the menu) and type `"c:\Program Files\ayanova\AyaNova.exe"` (note the quotation marks) to run AyaNova and see the error and make the necessary changes.
In some cases where there is a critical error completely preventing AyaNova server from running, the server console may display the error but close too quickly to read it. In this case you can view the message by opening a shell / command line prompt and starting `AyaNova.exe` manually from it's program files ayanova folder.
As you will remember from the installation above, you kept the checkmarked 'Start AyaNova server when Windows starts'. When your lan server is rebooted, the AyaNova Server shortcut will run on startup.
If you see an error about the `config.json` file there is likely a comma missing or some other format issue from when it was edited in the earlier step. Double check that it's not missing a comma or has an extra comma at the end that is not required or anything else that stands out.
If you receive an error that mentions `Microsoft.NETCore.App` it may be that the .net installation did not complete properly even though the display runtimes command executed properly. In this case the issue is often resolved by redoing the .net installation instructions above.
![SCREENSHOT OF setup window checkmarked server start with windows](img/ops-install-windows-lan-startup.png)
#### 5\.2 Double-click the AyaNova App shortcut