DISCLAIMER: This is an unofficial guide. If you mess things up then you may lock yourself out of TrueNAS or even worse, make it unusable. There's also no guarantee that this works in the future.
Currently the easiest way to access kubectl is through ssh and k3s tool. If
you have ssh access enabled then you can ssh to your TrueNAS server and use it
This service will use the same remote name you specified when using rclone config create. If you haven't done that yet, do so now.
Next, create the mountpoint for your remote. The service uses the location ~/mnt/<remote> by default.
mkdir ~/mnt/dropbox
| #!/bin/bash | |
| set -e -o errexit -o pipefail -o nounset | |
| ################################### | |
| # This script can be used by itself, but it's recommended that you read | |
| # a tutorial on Proxmox forum first: https://forum.proxmox.com/threads/hey-proxmox-community-lets-talk-about-resources-isolation.124256/ | |
| ################################### | |
| # Do not modify these variables (set by Proxmox when calling the script) | |
| vmId="$1" |
| #!/bin/bash | |
| set -e -o errexit -o pipefail -o nounset | |
| ################################### | |
| # This script can be used by itself, but it's recommended that you read | |
| # a tutorial on Proxmox forum first: https://forum.proxmox.com/threads/hey-proxmox-community-lets-talk-about-resources-isolation.124256/ | |
| ################################### | |
| # Do not modify these variables (set by Proxmox when calling the script) | |
| vmId="$1" |
| { | |
| // http://eslint.org/docs/rules/ | |
| "ecmaFeatures": { | |
| "binaryLiterals": false, // enable binary literals | |
| "blockBindings": false, // enable let and const (aka block bindings) | |
| "defaultParams": false, // enable default function parameters | |
| "forOf": false, // enable for-of loops | |
| "generators": false, // enable generators | |
| "objectLiteralComputedProperties": false, // enable computed object literal property names |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
