I have installed etcd in my mac using brew. I know we can pass the custom config file when starting the etcd using --config-file flag but I am not able to locate the default config file of etcd. So could you please let me know the location of the default config file of etcd?
By reading the Homebrew formula/package definition of etcd. It doesn't include any default config file.
Related
In the documentation for elasticsearch 7 it says explicitly
For the package distributions, the config directory location defaults
to /etc/elasticsearch . The location of the config directory can also
be changed via the ES_PATH_CONF environment variable, but note that
setting this in your shell is not sufficient. Instead, this variable
is sourced from /etc/default/elasticsearch (for the Debian package)
and /etc/sysconfig/elasticsearch (for the RPM package). You will need
to edit the ES_PATH_CONF=/etc/elasticsearch entry in one of these
files accordingly to change the config directory location.
Is there a way to specify my own path for a different /etc/default/elasticsearch file for a package distribution installation? I already tried by adding the following in my systemd service file which uses the EnvironmentFile I want, but it still uses /etc/default/elasticsearch when the service is comming up.
[Service]
...
EnvironmentFile=-/etc/default/elasticsearch-development
The answer to this (at least for version 7.7.0) is that you can't do it seamlessly with any option or environment variable because it is not provided. However it is possible to edit the file /usr/share/elasticsearch/elasticsearch-env that comes with the package installation and replace line 81 with the following:
if [ ! -z "$ES_DEFAULT" ]; then
source $ES_DEFAULT
else
source /etc/default/elasticsearch
fi
Then it is possible to set ES_DEFAULT in the system service file to point to a different /etc/default file.
[Service]
...
Environment=ES_DEFAULT=/etc/default/elasticsearch-development
I'm implementing an instance of Parse Server, I want know where the Parse Server Allocated the files ?
According to File Adapter, the default file storage is GridFS in mongodb.
Depends on the operating system and type of installation you used.
If installed on a linux/unix using the global install npm install -g parse-server mongodb-runner then your parse-server files will normally be under usr/lib/node_modules/parse-server. ( may differ from linux versions )
be careful when editing these files for hot hacks or modifications. If you later choose to upgrade parse-server they will be overwritten.
Your cloud file directly is normally created by you. So this could be home/parse/cloud/main.js. This can be in any location of your choice. To set a new location you will set that in the index file or json (depending on your startup process ).
cloud: '/home/myApp/cloud/main.js', // Absolute path to your Cloud Code
If you installed not using the global install, then obviously you would need to cd to where you cloned the project.
Windows would be similar. Clone (or download the zip) parse-server from the repo. Open a console window and “cd” to the folder where you have cloned/extracted the example server, eq:
cd "C:\parse-server"
Here is where the files will sit on the parse-server. Hopes this helps!
I have installed the Jabbered 15.07 on my MAC OS. After installation, I want to config it by editing the /Applications/ejabberd-15.07/conf/ejabberd.yml. I am not sure whether it is the file I should change, I searched the Internet and found that sb said the configuration is in the folder /etc but I did not found it there. In order to prove that it is the file I want to find, I open the admin interface and add a record in the "ACL" screen. And after that I checked the ejabberd.yml, but it remained unchanged. So is it the configuration file of ejabberd, if it is not which file it should be and how to configure it?
The location of the config file depend on how you installed ejabberd.
Apparently, you used binary installer, not make install, so config file is as your expected:
/Applications/ejabberd-15.07/conf/ejabberd.yml
Admin interface does not change the config file but write in mnesia database. You could configure ejabberd so that database override config file, but this is not a good practice. To make change permanent, you need to edit ejabberd.yml file.
Note: You should use latest ejabberd published version if you are starting today (15.11).
I am new to Salt, just want to install it on my MacBook for work.
I follow the instructions in https://salt.readthedocs.org/en/v0.16.4/topics/installation/osx.html
When I move the the step Salt-Master Customizations, I find I cannot find the configuration file.
I go to directory /etc/salt via Finder and only find one directory pki.
From http://docs.saltstack.com/en/latest/ref/configuration/examples.html#configuration-examples-master, it provides a sample configuration file. Then I am not sure what to do next? Do I need to create a configuration file under the directory of /etc/salt? If so, how to name the configuration file? Name it as master.conf?
Thanks very much!
Create a new file as:
/etc/salt/master
and add the sample configuration file you have found. More details can be found on the configuration page here: Configuring Salt
Have you tried adding -c /path/to/config/dir/ when starting the master?
I am getting an error attempting to start mongo with authorization enabled via the security.authorization configuration parameter (see http://docs.mongodb.org/manual/reference/configuration-options/#security.authorization)
On running mongod I get
Error parsing INI config file: unknown option security.authorization
try 'mongod --help' for more information
Any idea?
Thanks
Supporting data:
Mongo version 2.6.0 (installed via homebrew)
OSX Mavericks 10.9.2
start command:
mongod -f /usr/local/etc/mongod.conf
mongod.conf file (works fine if I comment out security.authorization):
# Store data in /usr/local/var/mongodb instead of the default /data/db
dbpath = /usr/local/var/mongodb
# Append logs to /usr/local/var/log/mongodb/mongo.log
logpath = /usr/local/var/log/mongodb/mongo.log
logappend = true
# Only accept local connections
bind_ip = 127.0.0.1
# auth
security.authorization = enabled
#security.authenticationMechanisms = MONGODB-CR #error occurs with or without this
No entry is made in the mongo.log file when this occurs
Note: I would have written this as a comment, however I do not have the points yet.
Just wondering whether what you are trying to achieve is authentication instead? If this is the case, all you need to set in mongodb.conf is:
# auth
auth = true # true or false. Whether or not authentication is required.
-- UPDATED:
Some other steps that are important:
Configure the db location: Set in mongodb.conf as (you already have this, but should check the directory and permissions exist):
# Store data in /usr/local/var/mongodb instead of the default /data/db
dbpath = /usr/local/var/mongodb
# Append logs to /usr/local/var/log/mongodb/mongo.log
logpath = /usr/local/var/log/mongodb/mongo.log
logappend = true
Dont forget to make sure the above /usr/local/var/mongodb directory and /usr/local/var/log/mongodb/ directory exist. The installer that you used may not have made them.
Create an Operating System user for mongodb: (If one has not already been created - this is how on linux, not sure for osx) - as root:
adduser --system --no-create-home --disabled-login --disabled-password --group mongodb
Add permissions to folders if they are not already set:
chown mongodb:mongodb -R /usr/local/var/mongodb
To setup database user authorization / privileges:
See the command reference here: http://docs.mongodb.org/manual/reference/command/#database-commands
MongoDB server config file format changed from version 2.6 and still old format works.
http://docs.mongodb.org/manual/reference/configuration-options/
Changed in version 2.6: MongoDB introduces a YAML-based configuration file format. The 2.4 configuration file format remains for backward compatibility.
The error is due to the reason your config file is using old format and adding parameter security.authorization = enabled using new format.You can fix the problem by
using old format settings mentioned at http://docs.mongodb.org/v2.4/reference/configuration-options
auth = true
or by converting conf file to new YAML format.