Ds4windows: [Notice] Updater Service Will Go Offline March 2019

[Ryochan7]

I hesitated bringing up this problem before but a recent email about my domain expiring has shown that the problem will affect others soon enough. My current ryochan7.xyz domain is set to expire January 19th but that won't really matter since DS4Windows and the DS4Updater use the server's IP address instead; I did not have a domain when I took over the DS4Windows project. What will affect others is not having a web host. I have enough money to pay the January payment for my hosting bill but I definitely will not have the money to pay beyond that.

[Nerdy314159265]

Could the updater be rewritten to look at Github directly so that you don't need to host anything?

I would think that you could have a file on the Github that lists the latest version and a link to the necessary files to update the program presumably also on Github on the release page or something. Then when the program checks for updates it can open a static link to the raw version of the file check the version number, if it's newer then download the files from the links below.

Do you think that would work?

[GingerAdonis]

I fully agree that the best way to go is to verify the GitHub release page and use that for the updater. The GitHub API calls are fairly easy to use.

[tremendoza]

Or we could donate 😐....

[mika-n]

Or auto-updater is removed and replaced with a simple notification that there is a newer version available (if that option is enabled in settings). People could then follow an URL link to Github release page and download the latest version whenever they want to.

Github already has a static URL link which takes to the latest release: https://github.com/Ryochan7/DS4Windows/releases/latest

The app could use that github "latest" URL (or use github API to do the same in standardized API way), parse the version tag from there and instruct people to navigate to the https://github.com/Ryochan7/DS4Windows/releases URL to download the latest or any other version they want.

I would prefer simple solution and let users to do the installation manually because auto-installer may have sometimes all sort of permission problems.

[Ryusennin]

I don't use the updater service. A simple notification would suit me just fine.

[Ryochan7]

I agree that changing the updater to rely on GitHub would be best. Technically the GitHub releases API could be used to obtain information about the latest DS4Windows release. I don't think I would want to add an extra assembly dependency for reading JSON files in DS4Windows though. It might be easier just to add the main version file to the DS4Windows repository and have the updater check it instead.

If this is implemented soon then there should be enough of a transition period so that most people won't be affected.

[Ryochan7]

I believe that I have everything set up now with DS4Windows and DS4Updater. The updates have been tested and downloading from the new locations works. I also had to copy over the "Virtual Bus Driver.zip" archive.

[Ryochan7]

The changes have been tested and a new version of DS4Windows has been released.

[Ryochan7]

Update. ryochan7.xyz is now officially dead. I am not going to go through previous issues and update any test build links. Just make sure to note that the server's IP address is 23.239.26.40 and update any links accordingly. For the time being, I will just have to start using Google Drive to host any new test builds.

As for the server itself, I got a few tips which will cover keeping the server online for one more month. No matter what, the server used to host old test builds and the old update files will go offline around March 1, 2019.

[GingerAdonis]

Have you looked into AppVeyor for generating builds? (continuous
integration) Lots of open-source projects use it.

On Mon, 21 Jan 2019, 21:20 Travis Nickles <[email protected] wrote:

Update. ryochan7.xyz is now officially dead. I am not going to go through
previous issues and update any test build links. Just make sure to note
that the server's IP address is 23.239.26.40 and update any links
accordingly. For the time being, I will just have to start using Google
Drive to host any new test builds.

As for the server itself, I got a few tips which will cover keeping the
server online for one more month. No matter what, the server used to host
old test builds and the old update files will go offline around March 1,
2019.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Ryochan7/DS4Windows/issues/531#issuecomment-456189324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACn8uMH68yArRRnsHTNetdlU6xGUi6mAks5vFiEigaJpZM4ZjGXE
.

[Ryochan7]

I have never looked into it. Deploying manually does not take that long so I have not had a desire to automate the process. AppVeyor looks pretty neat and it does offer options to only build under certain scenarios. Test builds would still be done manually either way. Also, the DS4Windows and DS4Updater apps use two separate GitHub repositories so that would probably cause some minor issues.

[Ryochan7]

It has been done. The old server is now offline.

[Ryochan7]

This issue is no longer relevant so it can be closed now.