How do I customise Rundeck with a logo? - rundeck

I've just installed Community Rundeck 3.2.2 with RPM on a RHEL 8.1.
I've tried to customise it with my logo images with no success:
Created user-assets directory in /var/lib/rundeck
Copied the images there (png and jpg)
Defined the settings in /etc/rundeck/rundeck-config.properties
rundeck.gui.logo=logoTNC600x600grey.jpg
rundeck.gui.logoSmall=logoTNC200x200white.png
rundeck.gui.instanceNameLabelColor=#ededed
rundeck.gui.instanceNameLabelTextColor=#000000
rundeck.gui.title=TNC Rundeck
rundeck.gui.staticUserResources.enable=true
rundeck.gui.login.welcome=Welcome to TNC
Restarted Rundeck service to no avail: picture not shown in web browser
What have I missed?
Regards,
Raul Costa

You need to add your assets at /var/lib/rundeck/user-assets path (create if it doesn't exist, remember: the "rundeck" user needs to reach that path). Also, verify the files extensions.
Update: change the order of elements in your configuration. Works in the following order:
# custom logo
rundeck.gui.staticUserResources.enabled=true
rundeck.gui.logo=logo.jpg
rundeck.gui.logoSmall=logosmall.jpg
rundeck.gui.instanceNameLabelColor=#ededed
rundeck.gui.instanceNameLabelTextColor=#000000
rundeck.gui.title=TNC Rundeck

Related

Where are the libraries for H5P getting stored in Moodle container

I am running a Moodle Docker container. It is running at localhost:8080. There I installed H5P Interactive Contents from https://moodle.org/plugins/mod_hvp in Site Administration>Plugins>Install plugin. Inside the moodle container (one can go there by docker exec /bin/bash), I can find the hop_mod in the /mod directory.
Now I am installing (with Edit Mode enabled in Moodle) different libraries of H5P Content (e.g., Interactive Video, Multiple Choice, Quiz, etc.) in Moodle like this:
Now I just wanna check where these libraries are getting saved. First, I thought they would be somewhere in /mod/hvp/ inside my moodle container. However, I could not find them. In some sources I found that files in Moodle get saved in /moodledata/filedir inside moodle container. I wanted to make sure if the libraries also get saved there. As the files are saved with their named hashed in /moodledata/filedir and there are literally thousands of folders here, it is impossible to check for the libraries or any file I want to check here.

Running the "AWS Image checker tool" says I have multiple profiles and wont let me make an image. I only see one?

I am using the AWS workspace product. I built an environment and I want to take an image of it, however it fails. when I run the included image checker tool it says I have multiple profiles.
Looking in windows users I only see one profile. I do have a couple entries under the (hidden) c:\users for different .net packages I have installed, is that what is causing it?

Installing Grafana Panel Plugin

I am attempting to install the piechart plugin on my Grafana v2.5 environment and no matter what I do the panel does now show as an option in the UI. I cloned the repository to /var/lib/grafana/plugins as documented and restarted the grafana-server service and that did not work. I also tried putting the plugin in a separate directory and referencing it as:
[plugin.piechart]
path = /home/usr/share/grafana/panel-plugin-piechart
I made sure that the grafana service has ownership of the plugin directory, and checked the grafana logs but it did not have useful information.
https://github.com/grafana/panel-plugin-piechart
You will need Grafana master based on the release date of the plugin.
Confirmed here - https://groups.io/g/grafana/message/1181
You definitely need to upgrade your Grafana. This is very seamless operation - just install a new package on top of the old one. You can back up through copy /var/lib/grafana/grafana.db for safety before doing that.
Check the permission of the files in plugins directory,
all the files of the plugin should be in its directory, i.e. every plugin should be contained its own directory
if the plugins directory has any package.json file or webpack.config.js available outside then also your plugins will fail to load.
the above mentioned files are part of every panel plugins and should only exist in their respective directories.
execute "chown" and set the owner to grafana:grafana group:user
(by default root is the owner of the files and directories.)
Are you running Grafana as a standalone service or in a docker container?
If running as a service directly you can visit the Grafana community page and find the plugin installation instructions from there.
https://grafana.com/grafana/plugins/grafana-piechart-panel
(Verified on Grafana version 6.x.x & 7)
If running within a dockerized service you need to copy the plugin in your workspace and specify the directory within the docker image so it can locate the plugin from there. You can do this by using the environment variables and mention these within a docker-compose file
GF_PATHS_PLUGINS /var/lib/grafana/plugins
https://grafana.com/docs/grafana/latest/installation/configure-docker/
I have been able to work with both these options

Empty Kibana Screen, Kibana not showing Data

Getting empty/blank screen (except for a few buttons on the top toolbar) in kibana.
I have elasticsearch 3.3.2 running on my localhost. I downloaded kibana-3.1.2. I unzipped the file and copied the contents of the extracted directory into my webserver. I copied then into "C:\inetpub\wwwroot". The config.js file is unmodified, because I am running on localhost and this will work for now.
The kibana folder now shows up in ISS under default Web site.
![enter image description here][1]
When I have an instance of elasticsearch running (verified by entering http://localhost:9200 in web browser)
I enter "http://localhost/kibana-3.1.2/" into my web browser (I have tried this in chrome and firefox).
This automatically redirects me to "http://localhost/kibana-3.1.2/#/dashboard/file/default.json" and shows the template of the kibana page but I can't do anything in it, and it doesn't have a "getting started guide" like the instillation instructions said there would be.
![enter image description here][2]
I don't know what I have missed or what I did wrong.
The problem is most likely that the Kibana javascript is unable to load default.json from IIS. You need to add a MIME Type mapping for the .json extension. Map it to application/json.
If you still get an empty dashboard, change the application pool used by the site to "No Managed Code" and "Classic" and recycle the application pool.
Did you set the
elasticsearch: "http://localhost:9200"
in kibana.yml?
Otherwise it might be the nginx configuration (that was the case for me).
BTW, an easy way to check is to download the Kibana 4 Beta which doesn't run on port 80 and doesn't require nginx (or other)...
You have to run Kibana 3 with tomcat server.. copy kibana folder into tomcat server,webapps folder... and run with the link "localhost:8080/kibana-3.1.2" (8080 ----> Give as per your tomcat port).
Now your kibana will start.

Product Image Upload Error

Below error while uploading images for Products:
{"name":"img5.jpg", "type":"application/octet-stream","tmp_name":"C:/Windows/Temp/phpA0A2.tmp","error":0, "size"2456,"path":"C:/.../media/tmp/catalog/product","file":"/i/m/img5_2.jpg.tmp","url":"http://www.example.com/media/tmp/catlog/product/i/m/img5_2.jpg","cookie":{"name":"adminhtml","value":"ghhjgjfhghy95","lifetime":"3600":"path":"/","domain":'mysite.com'}}
I am using php 5.3 on Windows, everything else works fine.
I tried all possible ways which I know or found like giving permissions, to directories, setting c:/windows/temp on php.ini, all session variables are set to (No), I tried with User Agent (Yes) also but no success. Also mapped security settings on c:windows/temp with Media folder.
I noticed Magento not writing files on the temp directory, but i created a test file which is writing to temp dir. only Magento files are not being written?
Please anyone can support on this or any one knows some good free extension to manage product images? I prefer to have default upload working.
Magento's official system requirements (click here) show that Magento is only supported on the following operating systems:
Supported Operating Systems: Linux x86, x86-64
Try switching to a linux based development environment and see if this solves your issue.