I am using Ubuntu 16.04 as host and the version of Rocket.Chat That I use is 0.61.0.
I want to create custom slash commands in my rocket.chat server. Can anyone provide me a clue regarding how shall I do it??
Related
In the website of visualstudio at the following link:
https://code.visualstudio.com/docs/remote/remote-overview
the website says that VS Code Remote Development can connect in 3 ways:
Remote SSH
Remote - Containers
Remote - WSL
In the link about Containers the page says:
Linux: Docker CE/EE 18.06+ and Docker Compose 1.21+. (The Ubuntu snap package is not supported.)
But also says:
Other glibc based Linux containers may work if they have needed Linux prerequisites.
So it is unclear if the extension works with non-Docker containers.
Is it possible to use this extension to develop software inside LXC containers(locally or remotely)?
LXC and LXD are system containers, therefore you can definitely use the Remote SSH method.
The Containers method has been designed for Docker. It might be possible to get it to work with LXD with an appropriate devcontainer.json, but you would need to figure this one out. I could not find an existing guide for this.
One could do with Ansible and LXD , infact it would be nicer.
The Omnibus version of Gitlab by default are using postgresql['enable'] = true, this seems that the postgresql can not be accessed by normal psql command, even in the Omnibus Gitlab container itself.
So is this true? If not how can I access this embedded postgresql from remote terminal?
This question is really what I want to do and it relates to my another post What's the default password for postgreSQL installed by Gitlab Omibus version?
If it is omnibus and you are using bundled postgres then you can use gitlab-rails dbconsole for accessing the database.
So you can try something like this docker exec -it CONTAINERID bash and then you can simply run gitlab-rails dbconsole.
Do let me know if this helps.
As the official document explained but not that specific and clear, https://docs.gitlab.com/omnibus/settings/database.html#configure-postgresql-block,
to expose the Postgresql from Gitlab Omnibus version。
postgresql['trust_auth_cidr_addresses'] and postgresql['listen_address'] are important and have to specified together, whereas this details not that much put on the documentation. Just tweak these two carefully then you can telnet PostgreSQL or login it remotely by using DBeaver as a sql client.
I installed Omnibus Gitlab using the docker image of gitlab-ce. Now my question is what's the default password for the embedded PostgreSQL database password?
I checked the Dockerfile and some scripts along with it from https://gitlab.com/gitlab-org/omnibus-gitlab, but could not find any clue.
Actually no need to access the remote PostgreSQL server which is embedded in the Omnibus version for users. If this is needed, just follow the documents to do more configuration to achieve this, like my another post answered. How to access/login postgres in gitlab omnibus docker container or from remote terminal?
I installed successfully ddev for TYPO3 and now want to connect to the mariadb database. But what are the credentials? If I ssh into the container and want to connect I got a password prompt.
Access via external tools is described in Using Developer Tools with ddev.
Specifically you need to execute the following command to get the necessary credentials:
ddev describe
When upgrading my ddev and deleting all the containers, everything stayed the same except my new port number incremented up by one.
mariadb
Host: localhost:portNumberIncrementedByOne
User/Pass: 'db/db'
I tried to install Openfire on Ubuntu 16.04 it installed fine but when I go to: http://localhost:9090 it shows me "prometheus" graph page
I wanted to know if I could install openfire or configure openfire to use a different port instead?
Thank you
Try finding a file with name openfire.xml. The location of the file differs according to the way of installation. Use the following command for finding it
sudo find / -name openfire.xml
Inside that file there will be a line <port>9090</port> just replace 9090 with the required port no and then restart the application.