Systemd Mount of Jottacloud on Startup - Help Ask

Hey All, I’m a new user to Linux and Bluefin, and I am trying to set up a systemd service to mount my rclone connection to Jottacloud on startup. Thus far I have successfully mounted the cloud manually with rclone mount --vfs-cace-mode full jottacloud: ~/jottacloud, Which allows me to interact with documents in the cloud and edit them live.

When I went to look for how to automatically perform this command on startup, I ran into the rclone documentation for autostart [rclone mount] and this guide [Autostart rclone mount using systemd – Guy Rutenberg].

I have gotten something to happen when I run the pair of commands in the end of the article by Guy Rutenberg systemctl --user daemon-reload and systemctl --user enable --now rclone-jottacloud, but the folder is not popoulated with the contents of my cloud, as it was when I run the mount command manually.

Below is the config file I have at the end of the ~/.config/systemd/user/default.target.wants/pathway, named rclone-jottacloud.service. I note that the last folder in that pathway appeared after running the second systemctl command, and that the file it contains is a copy of the on I originally created in the /user/ folder:

[Unit]
Description=Jottacloud (rclone)
AssertPathIsDirectory=%h/jottacloud
# Make sure network is enabled
After=network.target

[Service]
Type=simple

ExecStart=/usr/bin/rclone mount --vfs-cache-mode full jottacloud: ~/jottacloud

# Perform lazy unmount
ExecStop=/usr/bin/fusemount -zu %h/jott acloud

# Restart the service whenever rclonoe exits with a non-zero exit code
Restart=on-failure
RestartSec=15

[Install]
#Autostart after reboot
WantedBy=default.target

If anyone can give me some tips on getting this mount to work, or other automounting solutions on Bluefin, I would sincerely appreciate it.

– w0lm