Closed elcojacobs closed 11 years ago
Problem here is, we need to establish a standard install place to put it.
This ties back into one of my other thoughts on BrewPi... perhaps we shouldn't install brewpi-script directly to /home/brewpi . I would recommend keeping the home dir open for other uses as well, by instead installing to /home/brewpi/brewpi-script . Then we could use /home/brewpi/brewpi-tools , and the user could place any other stuff they want to (or leave it open for us to use in the future as well). I think you may have added this already, but would also enable something like brewpi-config/ as a location to put files that will change, like the config or profiles, so that we dont need to track them via gitignore
Thinking more about it, we could check what path the updater is running from, assuming that is where the git repo is, but that is an assumption that may not always be correct. But, could atleast be a starting point. I'd still like to keep thinking about eventually moving out of installing directly into ~
I agree we will have to move out of home/brewpi, at least for the app code. A good moment to do this is with the big rewrite of the code (move towards python web server).
I have added code to update the updater, so this one is closed!
https://github.com/BrewPi/brewpi-tools/commit/51b93620dac0de016e6b2cec6e2ff752da8e5eae
The updater should check its own repo/remote for updates :)