Bitcraze is offering a special discount.
With the discount code below, you will be able to purchase a Bitcraze Crazyflie STEM drone bundle for the discounted pre-shipping price of $189 (normally $245), subject to Bitcraze’s terms and limitations.
To take advantage of the discount, follow these PDF instructions with the code: UDACITY_FC_120. (This offer expires in 30 days.)
The Google Services Framework Identifier (GSF ID) is a unique 16 character hexadecimal number that your device automatically requests from Google as soon as you log to your Google Account for the first time. For a specific device, the GSF ID will change only after a factory reset. To get this information programmatically, you need to do two steps.
A) Add the following to your manifest
<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />
B) Execute the following code
private static final Uri sUri = Uri.parse("content://com.google.android.gsf.gservices");
public static String getGSFID(Context context) {
try {
Cursor query = context.getContentResolver().query(sUri, null, null, new String[] { "android_id" }, null);
if (query == null) {
return "Not found";
}
if (!query.moveToFirst() || query.getColumnCount() < 2) {
query.close();
return "Not found";
}
final String toHexString = Long.toHexString(Long.parseLong(query.getString(1)));
query.close();
return toHexString.toUpperCase().trim();
} catch (SecurityException e) {
e.printStackTrace();
return null;
} catch (Exception e2) {
e2.printStackTrace();
return null;
}
}
On GNU/Linux, you can traverse a directory if and only if you have execute permission on the whole path that you are going to use to access it. This rule applies a limitation to scenarios where for some reason you want to give execute access to a certain user on a subfolder but you do not want to enable the execute permission on the all the folders in the path.
In order to access the folder theFolder in the path /folderA/folderB/theFolder, if you are on the same level as folderA (or higher) you need to have execute permission both on folderA and folderA/folderB additionally to the permissions needed on theFolder. On another scenario if you are located in the same level as folderB (and you have execute rights to it) even if you do not have the execute rights to folder folderA you would still be able to access theFolder as your whole path (which is a relative path in this scenario) skips folderA. This feature is due to the fact that in GNU/Linux that the path that you use to access a folder determines your access constraints. In cases where the user does not have execute access to the whole path, creating symbolic links for them will not help you give them access. The kernel will still go through the access rights of the whole path that the symlink describes and it will act accordingly.
A hack-ish solution around this issue is to use mount to remount a part of the file hierarchy somewhere else using the bind parameter. For example: if we needed to give access to a user to the folder theFolder that resides in /folderA/folderB/theFolder without enabling execute rights on folderA nor /folderA/folderB we could execute the following command in a folder where that user already has execute access in (for example in the user’s home folder).
sudo mount --bind /folderA/folderB/theFolder finallyTheFolder;
Recently, we moved a client to Docker and we needed to give them a way to automagically update all “latest” Docker images.
Since Docker does not have a single command to update all pulled images we used this one-liner to update all images at once:
docker images --format "{{.Repository}}:{{.Tag}}" | grep ':latest' | xargs -L1 docker pull;
The above command will:
RepositoryName:Tag:latest (which is the tag we are interested in)xargs -L1 to the command docker pullPlease note that you cannot really update an existing container using docker commands, what you need to do is actually:
As you understand, it is a good practice to save all of your data in volumes outside the container to make the update process easy.
For example, below you will find the commands using which we updated the jwilder/nginx-proxy and the jrcs/letsencrypt-nginx-proxy-companion images along with the two containers that were using them:
docker container stop nginx-proxy nginx-letsencrypt;
docker container rm nginx-proxy nginx-letsencrypt;
docker run -d -p 443:443 \
--name nginx-proxy \
--net reverse-proxy \
-v $HOME/certs:/etc/nginx/certs:ro \
-v /etc/nginx/vhost.d \
-v /usr/share/nginx/html \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
-v $HOME/my_proxy.conf:/etc/nginx/conf.d/my_proxy.conf:ro \
--label com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy=true \
jwilder/nginx-proxy:latest;
docker run -d \
--name nginx-letsencrypt \
--net reverse-proxy \
--volumes-from nginx-proxy \
-v $HOME/certs:/etc/nginx/certs:rw \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
jrcs/letsencrypt-nginx-proxy-companion:latest;
