Open CodeCow opened 10 years ago
The update is intentional, but I might do that. For now, I'll keep it linked to my website while I get used to Github. Need to check why the Dropbox is down.
On Thu, Nov 28, 2013 at 7:30 PM, Code_Assassin notifications@github.comwrote:
Right now presskit(); is updating itself from the following two URL's:
and in case the files fail to update themselves , a Dropbox link is used as a backup
The secondary URL does not work(dropbox gives me a 404) while the primary URL can potentially update presskit(); to an older version if not maintained frequently.
Perhaps we can try to pull updates from the repository itself?
— Reply to this email directly or view it on GitHubhttps://github.com/ramiismail/dopresskit/issues/5 .
Dropbox works fine, but you need to link to a file directly since it doesn't do a directory listing. E.g.: http://dl.dropbox.com/u/12157099/presskit/archive.zip.
@Deron Thanks! Edited with correct information.
I'd like to recommend using the GitHub Releases feature.
@ramiismail would need to create a release tag when a build is ready to get shipped. But the latest release with a ZIP will be at a fixed URL, all ready to go. That URL won't change when there's a new version. Not to mention the notifications go out automatically for anyone subscribing.
@TheSeg I've implemented your feature on my fork, along with a few other pull requests from upstream here, in case you're interested: https://github.com/codingthat/dopresskit
Right now presskit(); is updating itself from the following two URL's:
and in case the files fail to update themselves , a Dropbox link is used as a backup
Perhaps we can try to pull updates from the repository itself?