#FileWatcher

[virginmiral]

Docker mount volume filewatcher detect changes

#Docker mount volume filewatcher detect changes for free

#Docker mount volume filewatcher detect changes install

>docker run -rm –it Microsoft/dotnet:latestĪ few things will happen when running that command:ġ. Run the following command to start a new container in an interactive mode, attaching the terminal, so we can run commands inside the container: You can check these images in their GitHub or Docker Hub sites. Net Core Docker images that we can use as a starting point. Microsoft has conveniently created and published. This article's code is available on github. But they still provide many of the benefits of virtual machines like isolating your processes and files.Īssuming that you are up and running with docker on your machine, let us get started with. That means they are lighter and easier to start/stop. These containers are different from virtual machines as they share the OS kernel with the host machine. This way, the application is guaranteed to work with any environment as the image contains everything that’s required to run the application. The apps as such are no longer deployed to different environments, but it’s the images – app with its dependencies, that gets deployed. These images can be distributed, deployed and run within any Docker containers.ĭocker also changes the way applications are deployed. The docker website explains What is Docker? In simple words:ĭocker allows you to build an image for your application with its necessary dependencies (frameworks, runtimes etc).

#Docker mount volume filewatcher detect changes install

If you have never used docker before, I would recommend you to check Download and install docker for your OS, and make sure you run through some of the examples in the Getting Started Tutorial. Net Core inside Docker containers - Introduction Net applications, in a very similar way to the more popular jsfiddle. NET Core applications can be run inside Docker containers by building your own version of dotNetFiddle.ĭotNetFiddle is an online environment where users can write and execute simple.

#Docker mount volume filewatcher detect changes for free

Download this magazine from here or Subscribe to this magazine for FREE and download all previous and current editions. This article is published from the DNC Magazine for Developers and Architects. This guarantees that the software will always run the same, regardless of its environment. Docker containers wrap a piece of software in a complete filesystem that contains everything needed to run: code, runtime, system tools, system libraries. NET Community on GitHub.NET Core is open source and cross platform, and is used to create applications and services that run on Windows, Linux and Mac.ĭocker is a software containerization platform. Net Core is a new lightweight modular platform maintained by Microsoft and the.

[terrispecials]

Docker mount volume filewatcher detect changes

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES PLUS

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES WINDOWS

Fixed a race condition crash when a directory is swapped for a file ( #513).Don’t walk directories without read permissions ( #408).Fixed missing field initializers and unused parameters in.Support for unscheduling deleted watch ( #541).Fixed a bug when calling FSEventsEmitter.stop() twice ( #466).Removed delay from non-move events ( #477).Fixed wrong source path after renaming a top level folder ( #515).Fixed the way OSError are re-raised ( #377).Fixed events containing non-ASCII characters ( #516).Skip unprocessable socket files ( #509).Fixed flavors of FreeBSD detection ( #529).Use os.scandir() to improve memory usage ( #503).Identify synthesized events with is_synthetic attribute ( #369).The utility is no more installed by default but via the extra.Removed the deprecated walker_callback argument,.Emitters that failed to start are now removed.Dropped support for Python 2.6, 3.2 and 3.3.Not a very scalable way to monitor a deeply nestedĭirectory of files and directories with a large number of To monitor file descriptors just makes this a painful way

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES PLUS

That plus the enormousĪmount of bookkeeping that watchdog needs to do in order This is an inherent problem with kqueue because it usesįile descriptors to monitor files. To do that is to edit your ~/.profile file and add Number of files that you will be monitoring. Running on your system to be increased to more than the Number of file descriptors allowed to be opened by programs Note that when using watchdog with kqueue, you need the

OS-independent (polling the disk for directory snapshots and comparing them.

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES WINDOWS

Windows (ReadDirector圜hangesW with I/O completion ports.

Each trickĬlass is initialized with its corresponding keys in the tricks.yaml file asĪrguments and events are fed to an instance of this class as they arrive. The directory containing the tricks.yaml file will be monitored. min.js compilation_level : advanced # simple|advanced source_directory : app/static/js/ destination_directory : app/public/js/ files : index-page : - app/static/js/vendor/jquery*.js - app/static/js/base.js - app/static/js/index-page.js about-page : - app/static/js/vendor/jquery*.js - app/static/js/base.js - app/static/js/about-page/**/*.js TrickĬlasses are augmented with a few additional features that regular event handlersĪn example tricks.yaml file: tricks : - : patterns : - watchmedo_webtricks.GoogleClosureTrick : patterns : hash_names : true mappings_format : json # json|yaml|python mappings_module : app/javascript_mappings suffix. Subclass and are written by plugin authors. Watchmedo can read tricks.yaml files and execute tricks within them in

[managetonki]

Filewatcher stopped working

The storage event trigger captures the folder path and file name of the blob into the properties and To use the values of these properties in a pipeline, you must map the properties to pipeline parameters. If your pipeline has parameters, you can specify them on the trigger runs parameter side nav. Click Next: Data preview to confirm the configuration is correct and then Next to validate the Data preview is correct. dropdown and select the trigger you created. When the side nav appears, click on the Choose trigger. To attach a pipeline to this trigger, go to the pipeline canvas and click Trigger and select New/Edit. Once your filter conditions have been verified, click Finish. Configuring filters that are too broad can match a large number of files created/deleted and may significantly impact your cost. This screen shows the existing blobs matched by your storage event trigger configuration. Select whether or not your trigger ignores blobs with zero bytes.Īfter you configure you trigger, click on Next: Data preview. In your specified storage location, each event will trigger the Data Factory and Synapse pipelines associated with the trigger. Select whether your trigger will respond to a Blob created event, Blob deleted event, or both. Other types of wildcard matching aren't supported for the trigger type. Note that Blob path begins with and ends with are the only pattern matching allowed in Storage Event Trigger.For example, april/shoes.csv will trigger an event on any file named shoes.csv in folder a called 'april' in any container. To specify a folder in any container, omit the leading '/' character. For example, a container named 'orders' can have a value of /orders/blobs/2018/april/shoes.csv. Container and folder names, when specified, they must be separated by a /blobs/ segment. Blob path ends with: The blob path must end with a file name or extension.This field can't be selected if a container isn't selected. Valid values include 2018/ and 2018/april/shoes.csv. Blob path begins with: The blob path must start with a folder path.You can use variety of patterns for both Blob path begins with and Blob path ends with properties, as shown in the examples later in this article. Your storage event trigger requires at least one of these properties to be defined. The Blob path begins with and Blob path ends with properties allow you to specify the containers, folders, and blob names for which you want to receive events. For more information about access control, see Role based access control section. No additional permission is required: Service Principal for the Azure Data Factory and Azure Synapse does not need special permission to either the Storage account or Event Grid. To create a new or modify an existing Storage Event Trigger, the Azure account used to log into the service and publish the storage event trigger must have appropriate role based access control (Azure RBAC) permission on the storage account.

[juststamp]

Docker mount volume filewatcher detect changes

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES HOW TO

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES INSTALL

Underscores convert to double underscores: is written as. The Neo4j configuration settings can be passed to a Docker container using the following naming scheme: Prefix with NEO4J. Here is an example of how I want to be able to use our FileWatcher class: 1 #include 2 #include "FileWatcher. This chapter provides a conversion table for the Neo4j configuration settings to the Docker format. We’ll start by writing a FileWatcher class that will check a given folder for changes at regular intervals.

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES INSTALL

If you want to install GCC 9 on your macOS check this article. Please note that, at the time this writing, Apple’s Clang from Xcode 10 or the Command Line Tools doesn’t support the std::filesystem library. Here is an example of compiling a C++ program that uses std::filesystem with GCC: 1 g++ -std=c++17 -Wall -Wextra -pedantic test_fs_watcher.cpp -o test_fs_watcherĬlang 8: 1 clang++ -std=c++17 -stdlib=libc++ -Wall -Wextra -pedantic test_fs_watcher.cpp -o test_fs_watcher -lc++fsĬlang 9 and up: 1 clang++ -std=c++17 -stdlib=libc++ -Wall -Wextra -pedantic test_fs_watcher.cpp -o test_fs_watcher If you want the ultimate performance, you should try to use the operating system functions like inotify on Linux or kqueue on macOS and FreeBSD.Īt the time of this writing, you can use the C++17 std::filesystem library with GCC 9, Clang 7 and MSVC 2017. The code was written as an exercise or demo to show what you can do with the C++17 std::filesystem library. With the dev container extension, VS Code. As long as you have Docker and VS Code installed on your machine, you can easily configure your projects with a Dockerfile and a devcontainer.json file. The base folder will be checked for changes at regular time intervals and, in case of changes, we’ll run a user defined function.ĭisclaimer: The code presented in this article is not meant to be used as is in production. Dev containers also allow you to close the gap between your development and production environments, making it much easier to debug production issues. Build After I saved my dockerfile, I will build the image and call it webserver using the following command.

DOCKER MOUNT VOLUME FILEWATCHER DETECT CHANGES HOW TO

For our limited purposes, we’ll monitor only the creation, modification and deletion of all files from the watched directory. Below, is a simple example of how to mount a Docker volume: From centos VOLUME /data In my example, I am mounting an image called /data to my image. We are going to implement a C++17 file watcher that will monitor a given folder for file changes. The advantage of using the C++17 std::filesystem library is that your code will be portable on all operating systems for which a C++17 compiler is available. In this article I will show you how to use the C++17 std::filesystem library to write a simple file watcher or file monitor. Solarian Programmer My programming ramblings Home Archives Contact Privacy C++17 Filesystem - Writing a simple file watcher Posted on Januby Paul

[chriwode]

Die eigene TYPO3 Extension integrieren

Teil 5 - Nachdem wir nun die wichtigsten Einstellungen in PhpStorm vorgenommen haben, wird es Zeit unsere eigene Extenion zu integrieren.

Spätestens an dieser Stelle kommt für mich auch Git ins Spiel, welches unbedingt gebraucht wird. Mit Git könnt ihr jegliche Art von Dokumenten und Inhalt, in unserem Fall Code versionieren. Wer jetzt denkt „Ich entwickle ja allein, das brauch ich nicht“, dem sei gesagt, doch du brauchst Git.

Das Projekt im Git-Repository

Wie eingangs schon erwähnt ist es an der Zeit den Code in einem beliebigen Git-Repository zu speichern. Ich selbst habe mich vor einiger Zeit dazu entschlossen die Kunden-Distribition direkt im Projekt-Repository und nicht in einem separten Repository abzulegen.

Auf die lokale Installation von Git möchte ich an dieser Stelle verzichten und auf die Website von Git verweisen. Eure Repositories könnt ihr z.B. bei den Anbietern GitHub, BitBucket oder GitLab sogar kostenfrei speichern. Damit spart ihr euch zum einen die Installation eines Git-Servers und deren Wartung, zum anderen sind eure Repositories von überall aus für euch erreichbar.

Der Vorteil eines Git-Repository sollte eigentlich klar sein, dennoch möchte ich kurz die Vorteile benennen:

Versionierung des Codes möglich

Zentrale Anlaufstelle

Arbeiten im Team am gleichen Code möglich

Durch PullRequests (PR) können andere den Code überprüfen, testen und ggf. korrekturen vornehmen

Nachvollziehen von Codeänderungen

.... und viele mehr

Wir speichern in dem Git-Repository nun nicht nur die Kunden Distribution, sondern das gesamte Projekt mit all seinen Abhängigkeiten. Somit kann ein Projekt schnell und einfach von neuen Kollegen aufgesetzt werden, wofür es grob nur 3 Schritte benötigt:

Projekt aus Git auschecken

composer install ausführen

Datenbank einspielen

Git initialisieren

Das Projekt muss nun mit Git auf eurem lokalen Rechner initialisiert werden. Dazu öffnet ihr in PhpStorm den "Terminal", welcher beim öffnen sich bereit in eurem Projektverzeichnis befindet. Nun tippt ihr den einfachen Befehl git init ein, woraufhin ihr die Rückmeldung Initialized empty Git repository ... erhaltet.

Git Index befüllen

Nun noch den Befehl git add ., wodurch alle Dateien und Verzeichnis (sofern nicht in der .gitignore enthalten) in den Index von Git aufgenommen werden. In PhpStorm sollten sich eure Datein nun entsprechend Grün färben. Mit dem Befehl git commit -m "Initial commit" werden nun alle Änderungen vermerkt, die Grünfärbung eurer Dateien verschwindet wieder. Bei Änderungen an Dateien, werden diese zukünftig blau gefärbt.

Projekt ins Git-Repository pushen

Jetzt müssen wir unserem lokalen Git nur noch mitteilen wo sich der Git-Server befindet und setzen einen entsprechenden Remote, z.B. zu GitHub: git remote add origin https://github.com/user/repo.git

Die URL in dem Befehl müsst ihr entsprechend anpassen. Infos dazu findet ihr bei eurem Git-Hoster.

Nun können wir mittels des Befehls git push origin master unseren Commit auf den Server übertragen. Damit ist es nun möglich, dass andere Teammitglieder, Kollegen, Freunde oder wer auch immer Zugriff auf das Repository hat, an dem Projekt mitarbeiten kann.

Extension anlegen - customer_theme_example

Bevor die Struktur für die Extension angelegt wird, sollte in der Datei ".gitignore" (im Projekt-Root) folgende Zeile hinzugefügt werden !/web/typo3conf/ext/customer_theme_example. Dadurch wird Git angewiesen das entsprechende Verzeichnis nicht zu ignorieren.

Die eigene Extension legen wir nun im Verzeichnis /web/typo3conf/ext/ an. Die Grundstruktur der Exentsion kann wie im nachfolgenden Screenshot aussehen. Weitere Strukturierungen sind durchaus möglich und denkbar.

Ihr könnt nun immer wenn eine Aufgabe für die Kunden Distribution abgeschlossen ist, diese direkt in eurer Git-Repository übertragen.

Sass compilieren - ohne FileWatcher

Wie in der Ordnerstruktur erkennbar ist, nutze ich für die CSS-Erstellung Sass als PreProcessor, wodurch weniger Code geschrieben und andere Sass-Dateien inkludiert und überschrieben werden können. In PhpStorm gibt es sogenannte FileWatcher welche bei Änderungen in Dateien anspringen und unterschiedliche Dinge ausführen können. Ich selbst mag den FileWatcher für Sass nicht, da dieser wirklich bei jeder Änderung anspringt, obwohl man sich noch nicht sicher ist, ob der geschriebene Code so bleiben soll. Werden zudem noch CSS-Frameworks inkludiert, dauert das Rendering entsprechend lange, was wiederum den Arbeitsfluss stört (triff zumindest für mich zu).

Daher nutze ich die Option der "Externen Tools" in PhpStorm, wodurch die Generierung manuell aufrufen werden kann und die CSS-Datei dabei automatisch im Verzeichnis /customer_theme_example/Resources/Public/Css/ abgelegt wird. Auf dem unteren Screenshot kann man meine Konfiguration für die Sass-Generierung sehen. Möglich sind auch weitere Konfigurationen, so dass diese speziell gestartet werden können (z.B. eine minimierte CSS).

Nachdem diese Einstellung gespeichert ist, legt man eine entsprechende Sass Datei in der Distribution an

Nun kann man mit der rechten Maustaste auf die Sass-Datei klicken und erhält in dem Context-Menü einen Punkt "Sass" in welchem sich als Unterpunkt "Sass to Css" befindet.

Nachdem nun auch mit Git gearbeitet wird, ist die Einrichtung eines TYPO3 Projektes in PhpStorm in den Grundlagen fertig. An dem Projekt kann nun gearbeitet werden, bevor wird es z.B. mit TYPO3.Surf auf den Ziel-Server des Kunden deployen. Dazu aber mehr im nächsten Kapitel ;)

Fragen, Probleme, Anregungen? Dann her damit, in den Kommentaren oder per Twitter an @chriwode.

[gameguides]

Victoria 3 How to Move Settlements in Map Editor

Welcome to our Victoria 3 How to Move Settlements in Map Editor guide. This modding guide will describe how you can move cities and other types of settlements on the map, so that they are in a different spot at the start of the game. #Victoria3 We know that there are people who have a hard time finishing the Victoria 3 game. If you are one of those who find it difficult to finish the game, let's take you to our Victoria 3 guide.

Victoria 3 How to Move Settlements in Map Editor

Is some city in the wrong place? Want to rearrange cities? Have you created a new state and you need to move cities around? Look no further! Vocabulary: - Hub / Anchor / Anchor hub : Invisible in the game, this is the point that roads and other types of splines connect to. It is associated with settlements and in the map editor it has a purple sphere around it. - Locator : An object which has visible graphics that look like a city, farm, mine, wood camp or port. In the map editor it has a yellow sphere around it (when the appropriate settings are enabled). It is normally placed near the hub. - Splines / Strips : Roads and other things that connect hubs But what exactly does that mean for the map? Hubs and locators together help define what I called in the title settlements and in the thumbnail cities. Every state has four settlements, and coastal provinces have an extra. These are: - city - farm - mine - port - wood While the roads are frequently visible always, the settlements themselves will only be on the map if the state has a building associated with that settlement type, such as a naval base for a port, or a chemical plant for a city. If during the course of your testing you want to make sure that a settlement is in the right place, start a building for that settlement! The Map Editor If you don't know how to open the map editor, you have a few choices. - Open the console by pressing the key above Tab and to the left of 1 in the top left of your keyboard. It is possible that you will need to have debug mode enabled, which you can do in two ways: Either have it in your commandline by having the argument -debug_mode (and while you're there, add -filewatcher, too!) - make sure you have the - at the front, OR in the launcher go to Gameplay Settings in the menu at the left and launch the game with the option Open game in Debug Mode. Once you've got that sorted, in the console type map_editor. - Add a commandline argument that reads -map_editor. This will automatically launch the map editor after the game has been loaded, so you will need to remove it before you can properly play the game again. The map editor is fairly resource-heavy, so if it crashes, it's probably because you don't have enough (free) computer resources. If this happens, try closing other programs while the editor is launching. When it launches, and you get rid of the console if you had it open, you will see something like this:

Victoria 3 How to Move Settlements in Map Editor The first thing you're going to want to do is click on the Mask Painter Tool in the left menu, the second one from the bottom.

Then in the menu that it opens on the right, look at the bottom-left window and tick the two boxes circled in red: Autorefresh and Draw City Spheres.

NOTE: Autorefresh requires a lot of resources, too. I have frequently crashed the editor by not giving it enough resources, so here it's also important to make sure your computer has enough. Moving the Settlement I've decided for this guide that I want to adjust the location of Tampere in Finland slightly. I'll click the Spline Network Strip Tool so I can see hubs and their splines (the roads and other connections).

We need to move both spheres - the pink/purple one that's the hub, and the yellow one that's the locator. It doesn't matter which order you move them in, but if you want the locator to be right on top of the hub (which I normally do because I don't like the look of the ends of the roads when they just stop abruptly), then I suggest starting with the hub. That's what I'll do. I'll just move it a little bit to the southeast.

So I'm dragging the hub southeast, and once it's in a good place I let go, and the game recalculates where the splines (roads) should go. I can adjust those with the Spline Network Adjustment Tool if I want, which is just below the currently-selected tool. Now let's move the locator. Choose the Map Objects Editor tool and click the Tampere sphere once.

Victoria 3 How to Move Settlements in Map Editor Then choose the Move tool from the top menu (shortcut key W) and drag the sphere to the desired location. If you're doing more than just one, it's good practice to switch back to the selection tool immediately by pressing Q and clicking away from the currently selected locator, that way you won't accidentally drag locators around.

SAVE SAVE SAVE It's happened before that I accidentally crashed the map editor after having made lots of edits to hubs. It may be annoying to save frequently, but it's better than losing 10+ minutes of work! Hit the Save As... button, and make sure that any files that have changed (that have their box ticked), are saving to your mod.

I strongly recommend against hitting the Save All button ever. Just reject it. I once hit it and it took a while to save and overwrote the base game files, so I needed to verify my game cache. It really put a dent in my modding vibe. Save and save often. Advanced: Hub IDs and types There are some other important things to note that didn't fit in this example: Hubs have an ID associated to them, which when you select a hub you can see in the top right of the map editor. The ID is always of the format . State IDs are perhaps most easily found in the map_data/state_regions folder. Settlement types are as follows: - 00 - city - 01 - farm - 02 - mine - 03 - port - 04 - wood Thus, the ID of the city for Lombardy (id 76) is 7600. The mine for Hedjaz (id 402) is 40202. The port for Guangdong (id 497) is 49703. With ports you might notice that it in fact has TWO hubs! This second hub always has the ID 00, and is different to the city because it's a Type 1 hub (which tells the game that it's a sea hub). Thus, although Guangdong's sea-facing hub's ID is 49700, because it's Type 1 instead of the normal Type 0, the game doesn't confuse it with the city in Guangdong (which is 49700 Type 0). At the time of writing, I don't know how to make new Type 1 hubs. If you figure it out, please let me know in the comments! Other AdvancedInfo At its foundation, hubs are intended only to connect splines/strips. For that reason, sometimes locators are not in the exact same location as their hubs. One example is in the Yukon Territory in North America. Deciding to put the locator somewhere different from the hub is a choice of visual design - maybe you want the road/railroad to go somewhere different than the settlement. Maybe you want to represent a settlement that was extremely difficult to reach. Maybe you want to make it easier for roads to reach hard-to-reach places. After all, splines/strips cannot pass through a third state to connect hubs in different states. Sometimes a hub far from its locator may make it easier to connect disparate states. Spline types: - Roads are always present - Railroads will only appear when you have researched the relevant technology - Coastal naval routes connect ports to sea hubs - Naval routes are the thick dashed line that connect sea hubs to other sea hubs Each one has its own colour in the editor, which you can see when you play around with them a bit. (I may write more here when it comes to mind) Read the full article

[hackgit]

​Filewatcher A simple auditing utility for macOS It can audit all events from the system...

​Filewatcher A simple auditing utility for macOS It can audit all events from the system audit pipe of macOS and filter them by process or by file. You can use this utility to: 1. Monitor access to a file, or a group of files. 2. Monitor activity of a process, and which resources are accessed by that process. 3. Build a small Host-Based IDS by monitoring access or modifications to specific files. 4. Do a dynamic malware analysis by monitoring what the malware is using on the filesystem. https://github.com/santoru/filewatcher

-

[laflechanet]

Nueva noticia publicada en LaFlecha

New Post has been published on https://laflecha.net/filewatch-para-buscar-archivos-compartidos-desde-google-drive/

Filewatch, para buscar archivos compartidos desde Google Drive

Si somos usuarios de Google Drive y le damos bastante uso, cabe la posibilidad de que algunos de los archivos que tengamos subidos los podamos tener también compartidos, tanto con otros usuarios como de forma completamente pública a través de sus correspondientes enlaces.

Para saber cuales son, podemos hacer uso de Filewatch. Se trata una solución gratuita y segura basada en la web por la cual obtendremos una lista de archivos que tengamos compartidos a través de nuestra cuenta de Google Drive.

Para ello, basta con que conectemos Filewatch con nuestra cuenta de Google Drive para que que esta herramienta nos escanee todos los archivos que tengamos almacenados en busca de aquellos archivos compartidos.

Posteriormente nos ofrecerá una lista desde la cual podemos proceder a la revisión de aquellos a los que queramos cambiar la configuración de uso compartido. Su desarrollador señala en Product Hunt que se trata de una herramienta segura que funciona del lado del cliente, nunca del lado del servidor, por lo que no se almacenará información alguna en el mismo.

Es, por lo tanto, de una interesante herramienta que en un momento dado nos puede venir bien, sobre todo, si disponemos de un amplio número de archivos alojados, algunos de los cuales podamos tenerlos compartidos y queramos, en un momento dado, saber exactamente cuales son.

Fuente: wwwhatsnew.com

[hottestproducts]

Find your public files, before someone else does

[e-commerce-magento]

RT @mage2tv: Published release 0.0.40 of the cache-clean.js filewatcher with some bugfixes and a new hotkey G to clean the [G]enerated code directory. https://t.co/C25KXQXQMe

Published release 0.0.40 of the cache-clean.js filewatcher with some bugfixes and a new hotkey G to clean the [G]enerated code directory.https://t.co/C25KXQXQMe

— mage2.tv (@mage2tv) April 23, 2019

from Twitter https://twitter.com/fbeardev

[levashove]

Как навести порядок в Google Диске

Как навести порядок в Google Диске #googledrive #google #webservices

Как навести порядок в Google Диске

Сервис Filewatch позволяет просканировать Google Диск и найти все ��айлы и папки, к которым у вас есть доступ. После этого можно будет выбрать любой файл, открыть его и изменить настройки доступа.

        Filewatch может отфильтровать файлы и показать только те, которые вы можете редактировать, или те, которые создали сами. Если вам нужен…

[herrprofessor]

Filewatch — Find your public files, before someone else does http://bit.ly/2lY8HfK #hotproduct

Filewatch — Find your public files, before someone else does https://t.co/Wvas7urzpK #hotproduct

— herrprofessor (@ilprofessoredi) July 5, 2018

from Twitter https://twitter.com/ilprofessoredi July 05, 2018 at 07:31PM via IFTTT

[topicprinter]

Visit the site Discuss on Product Hunt