Kibana being installed, I'm trying now to configure it correctly. I have a question : is there a way to modify Kibana's default data path. For example, you can modify log path by changing logging.dest var value within the file "/etc/kibana/kibana.yml" but this file doesn't contain any var for changing data path. I already looked within their official documentation but I found nothing...
In the meantime, if you have any advices concerning Kibana's installation and configuring, I'm totally listening...
Thank you all for your answers :)
Can do that by updating the "path.data" value in the config file "kibana.yml"
path.data: "new path for data"
location for config file is /etc/kibana/kibana.yml for rpm install for tar/zip install it will be in config folder.
DATA_PATH=/data /opt/kibana-5.2.0/bin/kibana
Related
Nexus OSS 3.7.1-02 running on RHEL 7. I have several repositories on it and I am able to publish and retrieve packages and jars, therefore, I presume that the setup is working correctly.
In the official documentation, I am referring to the 'Serving SSL Directly' section which uses the embedded Jetty server for serving https connections.
I am unable to find the file '$install-dir/etc/org.sonatype.nexus.cfg' mentioned in the documentation and there are a couple of config. around this file. I executed a find command for that file on the root directory but the file doesn't exist at all.
Another confusing step is:
Edit $install-dir/etc/org.sonatype.nexus.cfg. Change the nexus-args
property comma delimited value to include
${karaf.etc}/jetty-https.xml.
Now there's neither any directory under the 'karaf' directory nor does the file exist there but I found one jetty-https.xml file under nexus-3.7.1-02/etc/jetty.
How shall I proceed?
That isn't the official documentation, it's the documentation for "3.0". The official documentation is here: https://help.sonatype.com/display/NXRM3 (unversioned).
Specifically, I suspect you're looking for this: https://help.sonatype.com/display/NXRM3/Configuring+SSL.
Anyway, that file was replaced in an older version.
It now resides in ${data-dir}/etc/nexus.properties.
I am trying to build a Sailfish OS app, and I need to use *.wav files, which are to be distributed through the *.rpm package. In my case, these files are to be put in /usr/share/[application_name]/sounds/*. How do I set up the *.pro and *.yamp files accordingly?
This isn't a RPM question per se: you seem to be asking how to configure
your application through *.pro and *.yamp if you deliver content in
*.rpm packages.
The packaging answer is: Patch the configuration files exactly the same
as if you were installing the *.wav files manually (i.e. not through *.rpm).
You will need to copy the *.wav content into the %buildroot tree that
is used to stage the files to be included in the package, as well as the
modified *.pro and *.yamp content. All the files to be included in the
*.rpm package will need to be mentioned in the %files manifest exactly
as they are to be installed (i.e. w/o the %buildroot prefix used for
staging files while building).
I finally found an answer!
I want to thank to the owner of that project:
https://github.com/krig/metronom-sailfish
From the .pro and the .yaml files of this project i found out how to deploy the files. First, we declare that constant:DEPLOYMENT_PATH = /usr/share/$${TARGET} which seems to hold the path to /usr/share/[appname]. Next, we define some kind of a variable (TODO: find a more detailed explanation of that). The definition of that first sets the path to the files, for example, data.files = data (the second data is the folder). Next, we set data.path to $${DEPLOYMENT_PATH}. We list all the files in OTHER_FILES and add the setting, in our case, data, to INSTALLS. Now, that we are finished with the .pro file, we move to the .yaml file for the .rpm and we add to the necessary line to the Files: section, in our case, - '%{_datadir}/%{name}/data', the last being the folder we need to add. TODO: to whoever is more experienced, please provide a more detailed answer.
Did you check https://sailfishos.org/develop-packaging-apps.html carefully? May helps.
I downloaded rpm installer for Centos and installed gitlab.
I also fallowed this link: How to change URL of a working GitLab install?
I searched for 'how to change gitlab url' and similar... but found old results point to /etc/nginx/sites-enabled. But there is no directories like that. I changed every Url I found in files but still project url is the old. Is there any way to change it directly in template files or in config ? Tnx in advance
I just edited this file:
'/opt/gitlab/embedded/service/gitlab-rails/config/gitlab.yml' and now it is file :)
I have a Symfony2 application that I would like to deploy using Capistrano3. Performing cap install creates a config directory in the projectroot. To keep my project clean, I would like it to install the config dir into something like app\config\capistrano. Is this possible? I cannot find any hints in the documentations.
Found the anwser in a pull request on Github.
Enter the following two lines to your Capfile, before capistrano\setup beign called.
set :deploy_config_path, 'app/config/deploy.rb'
set :stage_config_path, 'app/config/deploy'
`
It is implemented in the 3.1.x branch
Look at your Capfile and change the path to the config file. This should be enough.
I want to run two different Meteor apps on the same server (on different ports) but I want to change something in one of Meteor's core packages and I want one app to use the original package and the other app to use the modified one. How could I do it?
A bit more straightforward answer, based on answer from here :
Create packages folder in your project and change location to that folder ('cd yourproject' && 'mkdir packages' && 'cd packages')
Fetch files from git ('git clone https://github.com/YOUR_PACKAGE_ADDRESS' - you need to have git installed)
Inside fetched package folder find package.js and edit inside 'Package.describe' name value, for example by adding '-manually-modified'
Edit files you need to modify inside fetched package folder.
Add package to project (meteor add package-name-manually-modified)
You can get the package's files at the github repo : https://github.com/meteor/meteor/tree/master/packages
Fetch the files you want except the package.js files and add them to your project. Of note is you need to ensure their loading order sometimes so you might have to modify the file names, to have a look at the loading order have a look at package.js. By default meteor orders file by name but packages don't necessarily use that.
You can avoid renaming the files if you just mod the package and add it back using meteorite : https://github.com/oortcloud/meteorite
Full instructions on how to make a smart.json : https://atmosphere.meteor.com/wtf/package. If its anything nice please consider adding it to atmosphere too!
I have my packages in my user folder at its root as a hidden folder called .meteor.
Perhaps you can check there? On a mac it would be under:
~/.meteor/packages/your package name
You must also now go into a file there os.json, and change the "length" variable for the file you changed to match the new byte file size. Otherwise it might not compile, but try compiling first and see if its an issue that you changed some package code.