env variable in the my_env_file doesn't mean we don't support it - please set the option in your my_env_file and launch a new container to pick up your latest changes! So just because we don't list every single possible. env Options You want to Set Should Be Set Here!Īny additional parameters you set in your my_env_file will be automatically propagated into your running Snipe-IT environment. env file that Snipe-IT does use, so what you put in here matters.Īny Other. env file Snipe-IT uses directly, but the values you put in it are used to generate the. You'll see examples of this in the commands further down the page as you initialize your Docker container.įor the purposes of this documentation, we'll call our file my_env_file. You can call this file anything you want, and put it wherever you like, just remember what you called it and where you put it, since you'll need to reference this file when you run your Docker containers, using the -env-file= argument. These environment variables will also affect your MySQL configuration. The Snipe-IT env-file is a simple text file with some variables and values that your Snipe-IT installation needs, separated by = signs. If you are using a method other than the standard docker CLI to integrate Snipe-IT into your docker environment, then you will need to make sure to pass all of the below mentioned variables into your Snipe-IT environment. To keep things simple, we try to centralize all of those settings in an environment file. Snipe-IT's Docker configuration requires many different environment variables in order to function correctly. The easiest way to get started with Snipe-IT on Docker is to use the Docker image we push to Docker Hub: That's not a Snipe-IT thing, that's a docker thing. If you don't recreate your Snipe-IT container, it won't pick up the new values. This Docker image uses some advanced concepts such as linking, storage volumes, and multiple images, so it may not be a good choice for learning Docker, however if you're willing to put some time into researching the concepts and background of Docker, we'll be happy to help you as best we can.Īny configuration changes in your docker-env file will require a container restart! If you don't know the implications of the steps you're taking here, you could potentially lose access to your data. We'll attempt to walk you through a Docker setup here, but please see the Docker documentation for a more in-depth understanding of Docker fundamentals. While it's not difficult to use, it can be a little confusing for folks who are less familiar with containerization. If you grabbed a docker image from any other repo, you're kinda on your own, since we cannot be responsible for images we do not manage directly.ĭocker is a very popular software containerization platform. The ONLY docker image we support is snipe/snipe-it. - Asset Label Printer Examples and settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |