Using Visual Studio Code with git-server and openHABian

[binderth (Thomas Binder)]

I’m no developer. This up front!

But I see the possibilities with a git repository and running openHAB to have a Version history, comparisons and so on…
Presently I don’t have a clue on how to achieve this:

1. running Visual Studio with a git Server in the first place
2. deploying (or copying or whatever) the files to openHABian
3. keeping track of changes

Is there a good howto for Dummies like me to Setup VS Code with git in the first place? I don’t seem to find a foolproof tutorial.
Do I need to use the Project for openHABian within the SMB-share of openHAB or is it better to deploy/copy the files differently?
How is the best practise for tracking changes in openHAB Environment?

Thanks for help!

PS:

• I have an own git server running on my Synology
• I have the openHAB-conf presented by SMB-share in the local network

[sihui]

Automatic Backup openHAB2 via GIT to BitBucket (FREE)

All, I typed up a script that will handle backing up my openHAB2 server to Bitbucket daily at 12AM (Midnight). Feel free to modify/use for GitHub or whatever GIT server you use. I went with Bitbucket over GitHub as Bitbucket offers unlimited private repositories for free whereas GitHub wants $7/month for that. Please note that Bitbucket has a 1GB soft cutoff and 2GB hard cutoff per repository, but I’m backing up more than I should and only using less than 400MB for my entire backup. What’s nic…

Automatic Backup openHAB2 via GIT to BitBucket (FREE)

Feel free to modify/use for GitHub or whatever GIT server you use.

[rlkoshak (Rich Koshak)]

VSCode will recognize you’ve opened a git controlled folder automatically Soo as you came files and such it will keep track of what has changed and let you commit and push changes and such. So there is nothing special to do there.

I don’t know what capabilities VSCode had to come a repo in the first place though, but I’d be shocked if it isn’t there somewhere in the menus.

The big thing to remember with git is each repo is it’s own independent thing. So you make changes, added files, and commit changes to your local git. Then you push them to the upstream using a push. For you upstream is your Synology server.

So let your in use files (e.g. /etc/openhab2) be a clone of your upstream repo. VSCode will recognize it as a git repo even over samba.

I posted somewhere how I set mine up using .gitignore to only get the important stuff from userdata. I’m on my phone with sorry service so can’t really find it. Let me know if you can’t and I’ll try to dig it up again when I get back to service.

[binderth (Thomas Binder)]

I posted somewhere how I set mine up using .gitignore to only get the important stuff from userdata. I’m on my phone with sorry service so can’t really find it. Let me know if you can’t and I’ll try to dig it up again when I get back to service.

I confess I already was on that thread - and forgot about it…

Best approach for git and openhab config

The same as for conf. I initially did a git init, copied over the conf and userdata folders to get started (also ~openhab/.java as that is where the oauth token stuff is stored for Nest connections). So I really just have the one repo which contains both my conf and userdata. I don’t do anything different for the two. About the only complaint that I have with this setup is my cloned repo OH runs on is almost always “dirty” because I have code that copies around icons for weather and the jsondb…

[Confectrician (Jerome Luckenbach)]

Just as a thought:

I am using a GitHub private repo as second remote.
This could be an additional option for keeping a versioned “backup” of your config files.
Easy too et up and you are doing all the stuff for the productive repo anyway already.