| const data = { | |
| "url": "https://news.polymer-project.org/", | |
| "title": "Top Stories - NEWS", | |
| "children": [ | |
| { | |
| "url": "https://news.polymer-project.org/list/doodles", | |
| "title": "Doodles - NEWS", | |
| "children": [ | |
| { | |
| "url": "https://news.polymer-project.org/list/top_stories", |
| #Usage: | |
| # | |
| #NOTE: The script expects an argument which is the full File Path of the EVTX file. | |
| # | |
| #C:\>ExtractAllScripts.ps1 | |
| #The default behavior of the script is to assimilate and extract every script/command to disk. | |
| # | |
| #C:\ExtractAllScripts -List | |
| #This will only list Script Block IDs with associated Script Names(if logged.) | |
| # |
UPDATED 22.11.2022
It's been two years since the last update, so here's the updated working script as per the comments below.
Thanks to BryanHaley for this.
setInterval(function () {
video = document.getElementsByTagName('ytd-playlist-video-renderer')[0];
video.querySelector('#primary button[aria-label="Action menu"]').click();
Najprostszym i najpewniejszym sposobem na bezproblemową instalację Node.js jest użycie NVM (Node Version Manager), który pobierze za nas odpowiednią paczkę, zainstaluje ją i ustawi poprawnie wszystkie systemowe ścieżki.
https://github.com/coreybutler/nvm-windows/releases/download/1.1.7/nvm-setup.zip
Part of collection: Hyper-converged Homelab with Proxmox
After struggling for some days, and since I really needed this to work (ignoring the it can't be done vibe everywhere), I managed to get Docker to work reliable in privileged Debian 12 LXC Containers on Proxmox 8
(Unfortunately, I couldn't get anything to work in unprivileged LXC Containers)
There are NO modifications required on the Proxmox host or the /etc/pve/lxc/xxx.conf file; everything is done on the Docker Swarm host. So the only obvious candidate who could break this setup, are future Docker Engine updates!
| // | |
| // _oo0oo_ | |
| // o8888888o | |
| // 88" . "88 | |
| // (| -_- |) | |
| // 0\ = /0 | |
| // ___/`---'\___ | |
| // .' \\| |// '. | |
| // / \\||| : |||// \ | |
| // / _||||| -:- |||||- \ |
| https://tackserver-code.ir/api/json/mrpooya.xyz.json | |
| https://test2.sub-channel.workers.dev/vless/iphone/random | |
| https://raw.githubusercontent.com/yebekhe/TelegramV2rayCollector/main/sub/base64/mix | |
| --------------*------------*---*----------------------- | |
| --------------*------------*---*----------------------- |
Whilst Asustor's ADM suits most people, it is possible to install ANY intel operating system on the nimbustor4/2 (as5202t/as5304t) as they run fairly generic intel hardware (asmedia sata controller, rtl8125 2.5gbe nic and ite system management chip)
in this gist I'll detail the steps needed to install and configure Debian11
Before proceeding you need to decide where you're going to install Debian.
Most people will choose to install it to a usb3 attached drive - either a usb3 ssd ( samsung t5 or similar ) or a usb3 hdd. This gives the most straightforward install ( just tell Debian to use the entire usb3 drive to install to ) and maximises available space on the NAS HDDs
The other option is to install Debian direct to the NAS hard drives - that means no extra drive hanging off the nas, and you can raid1 mirror the system partition across all drives for added resiliency ( though this is somewhat limited as the EFI boot partition is only on sda - so in the case of sda failing you'd need to boot off i
| Expected Result: | |
| ---------------- | |
| One | |
| Two | |
| Three | |
| Four | |
| Six |
