Start a version scheme and show it somewhere about plexrequests-meteor HOT 10 CLOSED

I've been meaning to do that for some time just haven't had a chance, I'll move it up the to do list!

from plexrequests-meteor.

Currently releases to the master branch have version numbers, although it's not displayed in the application itself (seen here) but I will change this.

For the dev branch not sure what's the best way to handle it, maybe just provide the Git commit hash as it's really just a staging area for new features. Ideas welcome though!

from plexrequests-meteor.

I think Couchpotato does git hashes. I am not even sure if I am on their dev branch but it auto updates so I never have to think about it.

Anyway, I think git hashes for the dev branch would be perfectly fine. Its just a way to easily distinguish what I am on and if I should update.

from plexrequests-meteor.

OK, I'll look into adding that as well as stating which branch you're on (and release for master). I wish I could implement auto-updates but haven't a clue how to

from plexrequests-meteor.

I would suggest looking at similar projects, such as sickrage og CP. It probably is something like this:

git fetch
git pull
restart application

from plexrequests-meteor.

Started to create page, but need help creating the new server functions not async to wait for the result to pass to the client side call (I forgot nodejs stuff is all async).

59a08ef

from plexrequests-meteor.

There's a synchronous version of git-rev https://www.npmjs.com/package/git-rev-sync
You can use a promise on the server (Though I think there's an issue when trying to get the result on the client)
Or, a hacky way you can do is to store the result in the db.

from plexrequests-meteor.

@jrudio thanks for the link to the synchronous version!

from plexrequests-meteor.

This is entirely useless if you're using the downloaded zip file which doesn't contain the .git folder (a note is present on the page). But more importantly, when you bundle the app for running in production (how I'm running it) you also lose the git information.

Need to come up with a second way, store commit/branch in a Collection maybe, but how would those downloading the .zip get it. Unless we don't use the commit hash at all, and manually tag things.

from plexrequests-meteor.

How about hardcoding a semantic version in a collection and increment on every commit (obviously).

Then, on an interval check the repository for a file, say version.txt, and see if the current app is less than the version in the repo.

If it is then download the .zip and display in the console or even the application that you have a new version downloaded. You can accomplish this easily with the package request.

from plexrequests-meteor.