No changes would be made to that in the future, right ?

i'm using it for that purpose too 🙂

you just went one level deeper by adding a hierarchy!

so yes, no changes with that in the future

> you just went one level deeper by adding a hierarchy! @User yeah thought it'd make sense

maybe I'll go for

base.*

or

home.*

instead

also I just realized, I was gonna have

*.tags.*

for hierarchies that have tags but that's redundant and could create dupes, I will instead have a

base.tags.*

and then

*.tags

notes linking back to tags from

base.tags.*

and maybe

base.tags

the note having an index of all notes tags*

🤔

Am I getting to overkill territory here 😅 ?

haha, you're in good company in that case

instead of doing a 'root' hierarchy, i consider my vault as my root

so instead of

base.tags

, i just do

tags

your top level nodes should be semantically equivalent to what you would attach to

root.*

to have an index of all tags, maybe have a

tags.all

or a

tags.index

> Can you share how you use the cron? @User So I when I said cronjobs, I meant http://supervisord.org/ and https://github.com/guard/guard 😅 Below is my config. Haven't cleaned it up for human consumption but should convey the gist - arc.rb

rb
require 'time'

guard :shell do
  watch /.*/ do |m|
    now = Time.now.utc.to_datetime.strftime '%Y-%m-%dT%H'
    commit = now
    out = `git log -n1 --grep #{now}`
    if out.empty?
      `git add . && git commit -m "#{commit}"`
    else
      `git add . && git commit --amend -m "#{commit}"`
    end
  end
end

- supervisor.conf

conf
[program:guard_dev]
directory=/Users/kevinlin/Dropbox/Apps/Noah/dev
command=bash -c "source $HOME/.zshrc && guard -G ../arc/Guardfile -i"
stdout_logfile=/tmp/%(program_name)s.out.log
stderr_logfile=/tmp/%(program_name)s.err.log

[program:guard_self]
directory=/Users/kevinlin/Dropbox/Apps/Noah/self
command=bash -c "source $HOME/.zshrc && guard -G ../arc/Guardfile -i"
stdout_logfile=/tmp/%(program_name)s.out.log
stderr_logfile=/tmp/%(program_name)s.err.log

[program:guard_notesv2]
directory=/Users/kevinlin/Dropbox/Apps/Noah/notesv2
command=bash -c "source $HOME/.zshrc && guard -G ../arc/Guardfile -i"
stdout_logfile=/tmp/%(program_name)s.out.log
stderr_logfile=/Tmp/%(program_name)s.err.log

> your top level nodes should be semantically equivalent to what you would attach to

root.*

@User Yeah makes sense, thanks for sharing

I want to sync my vault on a git repo, however I want to encrypt it before I push, and in case I pull from remote I want to decrypt it again, any idea how I would go about achieving this ?

git hooks maybe ?

git hooks and using something like bcrypt on push/pull might do the trick

all depends on your level of paranoia. public git hub repo -> private github repo -> custom hosted git repo -> encrypted notes

we have an issue open to explore how to better natively support this with dendron. if you come across something better than bcrypt, feel free to update the issue 🙂 https://github.com/dendronhq/dendron/issues/120

I'd go private github/gitlab repo and encrypted

I don't think I'm paranoid enough at this point to deploy it to a private git instance ... yet 😂

Alright, thanks. Cause I'm really planning on going big on dendron/pkm. Like manage pretty much everything that needs to be remembered / digested

including my network of friends / friends of friends / acquaintances ...etc, and I wouldn't be comfortable putting that info out there unencrypted

haha, give it time 😉

and yeah, pretty much everything i know is inside dendron at this point 😅

Once I've assembled enough knowledge, I'd like to start sharing/blogging at some point. And that would present some more great learning opportunities I imagine

i'm working on being more public about that too. someone you should checkout is @User and his everything i know wiki --> https://wiki.nikitavoloboev.xyz/