![]() ![]() mount type=bind,source=/VSERVER_DATA/projects,target=/opt/VServer/projects \ mount type=bind,source=/VSERVER_DATA/databases,target=/opt/VServer/databases \ Start your Valentina Server container like this: The upgrade procedure is very simple in this case.ĭatabases and projects are stored in the following folders: * /opt/VServer/databases * /opt/VServer/sqlite_databases * /opt/VServer/projectsĬreate appropriate directories on the host system: * /VSERVER_DATA/databases * /VSERVER_DATA/sqlite_databases * /VSERVER_DATA/projects The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly. This places the database files and projects in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The better way is to create a data directory on the host system (outside the container) and mount this to a directory visible from inside the container. Also, the upgrade procedure is complicated, as it involves copying data between containers of different versions. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers. Unlike the command line utility, Kitematic publishes these ports automatically.Ĭonnect to Valentina Server from the Valentina Studioīy default, the Valentina Server data (databases, projects, licenses, configuration) is kept inside the container. Note, the ports may be reassigned upon restart, so you may want to specify the port mapping manually:Īlternatively, you can use the Kitematic application to create and manage your containers visually. You can use this information to establish a connection. It returns a result in the following format: In order to get the list of assigned ports, it is necessary to execute the following command: We didn’t specify an explicit mapping so the Docker engine assigns random ports for published ports. … where some-vserver is the name you want to assign to your container ![]() In order to connect outside the container, it is necessary to publish them passing appropriate -p arguments to docker run command. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |