Create a template service file at /etc/systemd/system/[email protected]. The template parameter will correspond to the name
of target host:
[Unit]
Description=Setup a secure tunnel to %I
After=network.targetCreate a template service file at /etc/systemd/system/[email protected]. The template parameter will correspond to the name
of target host:
[Unit]
Description=Setup a secure tunnel to %I
After=network.targetNow that Electron has hit Chrome's 60s we can have proper module support. But of course, the standard (for very good reasons) prevents loading modules from file: and it makes sense for both Electron and NW.js to adhere to the statusquo.
So if you were really excited and this bums you, don't worry, you are in for awesome things.
The future Electron eco-system offers two options for native ES modules:
Custom Electron protocol via Chromium's module loading subsystem
Custom NodeJS loaders via Node's module loading subsystem recommended
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <base href="app://./" /> | |
| <meta http-equiv="Content-Security-Policy" content="script-src 'self' app:; object-src 'self' app:;"> | |
| <script type="module" src="./module.js"></script> | |
| </head> | |
| <body> | |
| Check the console! |