Share database or server install

[myval]

Hi,
I am no web expert so I might ask super dumb question.
Currently I use Part-DB docker version ( since I am not able to install it any other way tried and failed) and would love to share the database across multiple PCs.
Would this be doable sharing the DB via cloud storage and or is there any other way / better way of doing so.

thanks
Josef

[jbtronics]

Part-DB is intended to run as a server itself. And then multiple clients and users can access this instance and work on it. If the server is exposed to the Internet (or via some VPN or so), then this is possible from everywhere on the world, as long as you have a Webbrowser.

You could probably synchronize the database backend between multiple Part-DB instances (for sqlite with some kind of filesharing and for MySQL replication). But this is not officially supported or recommended and will probably lead to some weird synchronization and concurrence issues...

[myval]

thanks, but I am still not sure how to tackle this.
I guess the best option would be to use some webhosting but I can not figure out how to install it there, what the server needs.
Could you or anyone help a bit to get it setup properly?

[virtadpt]

For starters, database servers were designed from the outset to be able to run multiple databases at the same time. For example, while I don't know what the upper limit on MariaDB is but the most databases I've ever seen it run is around five or six dozen.

Part-DB-server runs nicely in shared hosting; that's how I run it (because I need to access it from just about anywhere). However, I have to run the setup process on a machine at home and then rsync the whole thing up to my webhost. Here's how I do it (copied from my wiki):

You need PHP with php-cli installed. You also need the packages php-fpm, php-gd, php-intl, php-xsl, and php-sodium installed and enabled in /etc/php/php.ini. You also need to make sure that mysqli is enabled in /etc/php/php.ini because Composer will need to look for (but not necessarily use) the database driver.

The PHP libraries Part-DB-server needs are installed with Composer. The command I regularly use for this is composer install -o --no-dev

There are static(-ish) assets that need to be present in the public/ subdirectory that need installed: php bin/console assets:install public/

There are Javascript libraries that have to be installed and compiled with Yarn. I do this with the commands yarn install and yarn build (in that order).

At this point you either have a web server to point at the public/ subdirectory (in which case this next step can be skipped) or a bunch of stuff to upload to your webhost. I don't know what you have to work with right now, but for discussion's sake here's what I do:

• cd
• rsync -avz --exclude='.git/' Part-DB-server/ user@web.host/partdb.me.example.com

On the web hosting provider (or on the web server you have) there are three steps needed to get Part-DB-server operational; two of them configure and set up on-disk PHP caching and one preps the database.

• cd blah.../Part-DB-server/
• php bin/console cache:clear --no-warmup
• php bin/console cache:warm
• php bin/console doctrine:migrations:migrate

Assuming everything went well, you should now have a functional Part-DB-server installation.