The documentation states that extra configuration can be put in the /artifactory_extra_conf directory. This directory does not exist in the artifactory-oss:6.1.0 docker image. When I create the directory myself it is not used, also I see no reference of it in the /entrypoint-artifactory.sh script.
Does anybody know if this behavior has changed and documentation is simply behind or that I'm maybe misinterpreting the docs?
Related
My goal is to put my telegraf config into source control. To do so, I have a repo in my user's home directory with the appropriate config file which has already been tested and proven working.
I have added the path to the new config file in the "default" environment variables file:
/etc/default/telegraf
like this:
TELEGRAF_CONFIG_PATH="/home/ubuntu/some_repo/telegraf.conf"
... as well as other required variables such as passwords.
However, when I attempt to run
telegraf --test
It says No config file specified, and could not find one in $TELEGRAF_CONFIG_PATH etc.
Further, if I force it by
telegraf --test --config /home/ubuntu/some_repo/telegraf.conf
Then the process fails because it is missing the other required variables.
Questions:
What am I doing wrong?
Is there not also a way of specifying a config directory too (I would like to break my file down into separate input files)?
Perhaps as an alternative to all of this... is there not a way of specifying additional configuration files to be included from within the default /etc/telegraf/telegraf.conf file? (I've been unable to find any mention of this in documentation).
What am I doing wrong?
See what user:group owns /etc/default/telegraf. This file is better used when running telegraf as a service via systemd. Additionally, if you run env do you see the TELEGRAF_CONFIG_PATH variable? What about your other variables? If not, then you probably need to source the file first.
Is there not also a way of specifying a config directory too (I would like to break my file down into separate input files)?
Yes! Take a look at all the options of telegraf with telegraf --help and you will find:
--config-directory <directory> directory containing additional *.conf files
Perhaps as an alternative to all of this... is there not a way of specifying additional configuration files to be included from within the default /etc/telegraf/telegraf.conf file? (I've been unable to find any mention of this in documentation).
That is not the method I would suggest going down. Check out the config directory option above I mentioned.
Ok, after a LOT of trial and error, I figured everything out. For those facing similar issues, here is your shortcut to the answer:
Firstly, remember that when adding variables to the /etc/default/telegraf file, it must effectively be reloaded. So for example using ubuntu systemctl, that requires a restart.
You can verify that the variables have been loaded successfully using this:
$ sudo strings /proc/<pid>/environ
where <pid> is the "Main PID" from the telegraf status output
Secondly, when testing (eg telegraf --test) then (this is the part that is not necessarily intuitive and isn't documented) you will have to ALSO load the same environmental variables into the current user (eg: SET var=value) such that running
$ env
shows the same results as the previous command.
Hint: This is a good method for loading the current env file directly rather than doing it manually.
Many CI providers give you a directory whose contents are retained across builds and you can use that as a cache. Everything that is stored elsewhere is lost. This means that any artefacts that are created during a nix-build that are placed in the nix store (/nix/store) are lost. I'm trying to figure out how to convince nix to prefer that other cache directory over the global /nix/store. However the documentation is a bit lacking.
What I've tried so far:
Add file:///the/path to substituters and then nix copy --to that path. However I discovered that nix only creates some metadata files in that directory and copies the actual derivation into /nix/store. That's not what I want.
Use local?root=/the/path instead of the file:// url (btw, this syntax is not documented anywhere, I only found it in a single github issue!). That made nix copy the whole derivation to that folder, but I couldn't figure out how to convince nix-build to actually consult that store during build.
Would it be possible to use something along the lines of nix run --store ~/my-nix nixpkgs.hello -c hello --greeting 'Hi everybody!'? The installation guide points to uses of --store for such a use case, as well as some sections in the manual: 1, 2.
An example of this can be found in nix run's tests.
There are also the environment variables NIX_STORE_DIR which might be of use? It's documented in nix-shell --help.
There's also several issues in the Nix repo, here's an interesting discussion.
Schemacrawler makes reference to a "configuration file", e.g. in https://www.schemacrawler.com/diagramming.html it says:
Show column ordinals, by setting configuration option schemacrawler.format.show_ordinal_numbers=true in the configuration file.
But I've not found what and where that file is.
I run Schemacrawler from its provided Docker images and struggle to make sense of where to configure e.g. schemacrawler.format.show_ordinal_numbers=true as referenced in the above docs.
Anyone know how this is intended to work?
(BTW I'm asking on SO because their repository suggests to do so)
Seems it makes use of this file: config/schemacrawler.config.properties.
From its Github repo I found these links:
Diagram Readme
Sample config file
Jon,
Please use the latest SchemaCrawler Docker image. When you open a shell in this Docker container, you will have a schemacrawler.config.properties file in the home directory. You can edit this file in vi, and then use it with SchemaCrawler by providing an additional -g ./schemacrawler.config.properties command-line switch. Instructions are provided on the Docker Hub SchemaCrawler page.
Sualeh Fatehi, SchemaCrawler
I downloaded Docker for Mac since it was a prerequisite for Hyperledger Fabric (also listed here).
Now, I downloaded platform specific binaries listed here.
The instructions said:
If you are using Docker for Mac, you will need
to use a location under /Users, /Volumes, /private, or /tmp. To use a
different location, please consult the Docker documentation for file
sharing.
So,I used the following directory: /Users/user_name/Documents/Hyperledger\ Fabric/
I followed the same commands as listed on the site.
However, I was not able to add the line below to the ~/.bash_profile.
export PATH=/Users/user_name/Documents/Hyperledger\ Fabric/bin:$PATH
If I added the above line and ran the bash_profile, it gave an error and after that commands like ls, open were giving error not found.
It seems that there is a problem with the file location since I
installed Docker for Mac instead of Docker toolbox.
The problem is that your directory name contains a space. One way to avoid this problem is to specify a directory name that has no spaces. This would be the ideal approach since once you introduce a space in the PATH variable it would need to be quoted where used subsequently.
Alternately, you could set the path as:
export PATH="/Users/user_name/Documents/Hyperledger Fabric/bin":$PATH
However, as noted this has drawbacks.
Sorry for the newbie question, i see lots of references to conf/neo4j-wrapper.conf , but cannot find this anywhere on my windows server installation of Neo4j 2.1.2.
can somebody tell me where it is please?
thanks
You'll have to create the "conf" directory yourself.
I tried it on my windows machine before answering you, as I encountered the same problem initially.
In my case, I first created the directory
C:\Program Files (x86)\Neo4j Community\conf
and in there I created the files
neo4j.properties
neo4j-wrapper.conf
See Neo4j post here
I might be mistaken, but, I don't believe the Windows version puts an instance of that file on disk.
Given that neo4j.properties is in your actual graph DB directory (e.g. c:\\Neo4j\default.graphdb), you might try creating an instance of the file there and seeing what happens.
Or you could also try creating a conf/ directory from that same location and putting it in there.
I'm used to working with the Linux version, myself.
Let us know what you find!
HTH