This is the beauty of docker in that it allows you to easily separate the applications state (configuration, data etc.) from the actual application itself.
So as long as you are using the suggested docker commands (with the --mount directive or in docker-compose the suggested volume: directives) the actual data itself (the MySQL DB and the Snipe IT images etc.) are persisted outside of the actual application (and it's environment variables)
This means you can modify the environment variables and then completely recreate the containers no worries. The application will retrieve the configuration and relevant data as it normally would (this is similar to restarting a traditional server in some ways) as all you are actually destroying is the application 'code' not the data you have created by configuring it. This allows you to very easily update the application (simply change the image version in the docker compose file typically) as well as recovering from a crash etc. (the container will simply automatically restart)
docker-compose downcommand (as this will remove volumes as well) and instead use
docker-compose stopEDIT: Small correction docker-compose down will only remove volumes with the -v argument so no worries there :)
To Whom It May Concern,
I would like to thank first for taking your time to help me and read this. I'm currently having issues in installing Snipe-IT and I would love to install and have it self-hosted. Below is the issue that I'm encountering with. I'm currently running it from a CentOS 7 VM.
sudo /bin/composer install --no-dev --prefer-source
Loading composer repositories with package information
Installing dependencies from lock file
Your requirements could not be resolved to an installable set of packages.
- Installation request for tecnickcom/tc-lib-barcode 1.15.20 -> satisfiable by tecnickcom/tc-lib-barcode[1.15.20]. - tecnickcom/tc-lib-barcode 1.15.20 requires ext-bcmath * -> the requested PHP extension bcmath is missing from your system.
To enable extensions, verify that they are enabled in your .ini files:
- /etc/php.ini - /etc/php.d/20-bz2.ini - /etc/php.d/20-calendar.ini - /etc/php.d/20-ctype.ini - /etc/php.d/20-curl.ini - /etc/php.d/20-dom.ini - /etc/php.d/20-exif.ini - /etc/php.d/20-fileinfo.ini - /etc/php.d/20-ftp.ini - /etc/php.d/20-gd.ini - /etc/php.d/20-gettext.ini - /etc/php.d/20-iconv.ini - /etc/php.d/20-json.ini - /etc/php.d/20-ldap.ini - /etc/php.d/20-mbstring.ini - /etc/php.d/20-mysqlnd.ini - /etc/php.d/20-pdo.ini - /etc/php.d/20-phar.ini - /etc/php.d/20-simplexml.ini - /etc/php.d/20-sockets.ini - /etc/php.d/20-sqlite3.ini - /etc/php.d/20-tokenizer.ini - /etc/php.d/20-xml.ini - /etc/php.d/20-xmlwriter.ini - /etc/php.d/20-xsl.ini - /etc/php.d/30-mcrypt.ini - /etc/php.d/30-mysqli.ini - /etc/php.d/30-pdo_mysql.ini - /etc/php.d/30-pdo_sqlite.ini - /etc/php.d/30-wddx.ini - /etc/php.d/30-xmlreader.ini - /etc/php.d/40-zip.ini
You can also run
php --ini inside terminal to see which files are used by PHP in CLI mode.
Yeah, thanks! New issue! Haha, when using drop down menus, for example, selecting a department or location, everything appears for about 3 seconds and then they vanish. If you click fast, you can select them. Also when editing 'people' the entire list sometimes vanishes, have to keep refreshing until they appear again...anyone ever seen this happen?
No idea as to why this might be happening - good step might be to enable debug mode and see if anything obvious is happening there, I don't experience that issue at all
I figure it out what was the problem, base in the notes that I was guiding myself with they have a missing step. If you have the same issue as me, you can resolve it by running this command:
yum install php-bcmath
Once I ran that command, I was able to ran the command below successfully.
composer install --no-dev --prefer-source