the following content has been approved for
AllertaLOM (GooglePlay) is a multi-service Android and iOS application developed by Italian's administrative region Lombardy.
The main purpose of AllertaLOM is to provide a single point of information focused on alerts and notifications about the territory. Scope is therefore restricted to the solely Lombardy region.
Since Google Compute virtual machine will be behind a nat network, you have to pass to the join command the "advertise" ip address. Without it the node will be added in any case, but the overly network won't work (because the system will try to contact the virtual machine through its local address):
sudo docker swarm join \ --token SWMTKN-1-qwe...... \ # here your public IP --advertise-addr 18.104.22.168 \ 22.214.171.124:2377
Since the web is plenty of examples related to SSH forward tunnels (the famous SSH -L command) but lacks of information about its reversed counterpart (SSH -R), I decided to write down a few lines developed while working on a Go implementation of the SSH command:
Fetch innotop from its GIT repository:
sudo apt-get install git git clone https://github.com/innotop/innotop.git
Install any missing Perl dependency:
sudo apt-get install libclass-dbi-mysql-perl sudo apt-get install libterm-readkey-perl
Use below command:
cd /edx/app/edxapp/edx-platform/ sudo -u www-data /edx/bin/python.edxapp ./manage.py cms --settings aws delete_course course-v1:edX+DemoX+Demo_Course commit
Open Atrium 2.43 (and also some previous versions) is affected by a bug mutuated by radix theme.
As always, there might be better fixes, but the below – until someone decide to fix this up, works:
Right after the update to Drupal Open Atrium version 2.43, all dropdown-toggle buttons were not working any more.
Since I’m using a child theme, this time the workaround was to add bootstrap library to the child theme. Something like the below code inside the theme.info file:
Last but not least: The operator is invalid on filter: Field: Groups audience:target_id.
If, as me, you will find it printed on the View Administration interface, right after an update, then it’s time to select the filter criteria on the incriminated view and check one of the availabe operators, which for some reason are now blank!
And the error will disappear, permitting you to continue with the editing of the view.
This post is just a personal reminder, on internet you will find quite a lot of stuff, every solution might even work, but I prefer to deal with the minimum number of configuration files so: