1. François Van Lerberghe
  2. as Embedded Server
  3. Tuesday, February 04 2020, 05:53 PM
  4.  Subscribe via email
I see in the Wiki
roducts:vserver:embedded:manual:deployment_optional_steps" target="_blank" rel="nofollow">Deployment Optional Steps
To avoid conflicts, it will be better if each application will use own name for folders and files.

Thus, I change
- vserver app name to myAppServer.app
- vserver ini file name to myAppServer.ini
- vlogs folder name in the myAppServer.ini file to "Logs"
Launching myAppServer.app
1) it doesn't read the myAppServer.ini
2) a new file" vserver.ini" is created
3) my Logs folder is not used and a vlogs folder is created
Must I do something else in order to do this working ?
(Previously, with vserver 5.8.8, this is working well)
Comment
There are no comments made yet.
Ruslan Zasukhin Accepted Answer
Hi,

we must to check this. Give us time please - couple of days.
Comment
There are no comments made yet.
Ivan Smahin Accepted Answer
As a workaround you should open contents of vServer.app and rename there:

1.
/Contents/MacOS/vServer_64 => /Contents/MacOS/myAppServer

2.
Edit Info.plist and replace every vServer_64 entry to your name
Comment
There are no comments made yet.
Thank you Ivan. This solve 90% of my problem. :)
Last thing to solve : when myAppServer is launched, it read accordingly the myAppServer.ini file, but an additional file is created, named "myAppServer.ini.example". Is there some workaround to avoid the creation of this file ?
Comment
There are no comments made yet.
Ivan Smahin Accepted Answer
Please report it to the mantis as a feature request.
Comment
There are no comments made yet.
Ruslan Zasukhin Accepted Answer
Ivan,

I think we can remove this file creation automatically IF we see that vserver name differs...

On the other hand ... maybe somebody may consider this useful ... then how to decide ?
Comment
There are no comments made yet.
I think it must exist a way to bypass this file creation.
Today, someone can see the example ini file
- in a fresh download
- detailed in the comments of the ini regular file
- explained in the wiki
Why a developer could want to see it again if he/she has customised the vserver file ?

The rule could be :
Create the example ini file if
- there is no ini file
or
- if vserver name is the same
or
- both
Comment
There are no comments made yet.
Ruslan Zasukhin Accepted Answer
We have decided to remove this example.ini at all.
Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.

Categories

Announcements & News
  1. 0 subcategories
Valentina Studio
  1. 2 subcategories
Valentina Server
  1. 4 subcategories
Valentina Database ADK
  1. 0 subcategories
Valentina Reports ADK
  1. 0 subcategories
Other Discussions
  1. 2 subcategories
BETA Testing
  1. 0 subcategories
Education & Research
  1. 0 subcategories