Ideas:
- Add setup.sh or install.sh script - run it locally or with curl?
- Clones the repo to
~/.unicron
- for dev, should this be the same? Or symlink? Or separate? I've had issues before where something (including cron) was broken for a few days and I didn't know. Unfinished unstashed work can cause issues.
As part of install, create actual script in /usr/local/bin default, or ~/bin with arg. Which will do this.
- Script:
SCRIPT_DIR=...
cd $SCRIPT_DIR
make $@
Maybe it is a symlink rather to a script in unicron which does the same thing. (symlink is better for keeping logic in version control).
This could run the install script.
Will also need a way of doing git pull. Keep it like a repo cloned with https for updates rather than trying to download.
Also make sure to checkout to latest tag when running unicron update. Unless a flag is used to indicated latest/master.
What to do about unicron data? Keep it separate in a var directory so the repo can be deleted. Maybe ~/.unicron/unicron-repo can be the repo
See how Oh my ZSH handles this
This setup could be done manually first to see if I like it and then all brought into scripts (automate second).
Ideas:
~/.unicronAs part of install, create actual script in
/usr/local/bindefault, or~/binwith arg. Which will do this.Maybe it is a symlink rather to a script in unicron which does the same thing. (symlink is better for keeping logic in version control).
This could run the install script.
Will also need a way of doing
git pull. Keep it like a repo cloned withhttpsfor updates rather than trying to download.Also make sure to checkout to latest tag when running
unicron update. Unless a flag is used to indicated latest/master.What to do about unicron data? Keep it separate in a var directory so the repo can be deleted. Maybe
~/.unicron/unicron-repocan be the repoSee how Oh my ZSH handles this
This setup could be done manually first to see if I like it and then all brought into scripts (automate second).