Git repository change
-
git://github.com/smos/pfsense-ipv6.git works fine in the auto-update URL, I haven't tried the https URI, but it should work also (note: I have collab access to the repo, so YMMV…the git:// uri absolutely is working however).
--Bill
-
My problem was this url is not correct to view in your browser.
https://github.com/smos/pfsense-ipv6.git
Go ahead paste in browser, click on it, etc = 404
Now this one does work
https://github.com/smos/pfsense-ipv6And yes this url works in the firmware updater or if using playback gitsysnc
git://github.com/smos/pfsense-ipv6.gitI also agree this site SUCKS!!!! in Firefox 4 – and you have to enable RC4 SSL support, because the link to CSS for from cloudfront is only served using RC4 SSL -- that really blows if you ask me. Great if you still want to offer that up, but how about something else so people that have it disabled can still view the page correctly.
have not looked into why yet, but trying to load current link for the merge creates 1000's of errors in firebug on firefox.
Why did you move to this site? What was wrong with other git site?? I don't like the new atom feed either - missing dates, on the feeds. Reminder people if you using the RSS on the dashboard need to change the feed url
https://github.com/smos/pfsense-ipv6/commits/master.atomBut am curious why the move to the github site - what was wrong with the other site??
-
My problem was this url is not correct to view in your browser.
https://github.com/smos/pfsense-ipv6.git
Go ahead paste in browser, click on it, etc = 404
Yes and Seth corrected himself.
Now this one does work
https://github.com/smos/pfsense-ipv6And yes this url works in the firmware updater or if using playback gitsysnc
git://github.com/smos/pfsense-ipv6.gitI also agree this site SUCKS!!!! in Firefox 4 – and you have to enable RC4 SSL support, because the link to CSS for from cloudfront is only served using RC4 SSL -- that really blows if you ask me. Great if you still want to offer that up, but how about something else so people that have it disabled can still view the page correctly.
have not looked into why yet, but trying to load current link for the merge creates 1000's of errors in firebug on firefox.
Why did you move to this site? What was wrong with other git site?? I don't like the new atom feed either - missing dates, on the feeds. Reminder people if you using the RSS on the dashboard need to change the feed url
https://github.com/smos/pfsense-ipv6/commits/master.atomBut am curious why the move to the github site - what was wrong with the other site??
I was the sole maintainer to the pfsense Gitorious install. It was massively outdated and was going to take an extremely large amount of effort to update. github is faster and they deal with site issues leaving us (me) time to actually code instead of staring at dozens of daily exception notifications in email. If you actually used our Gitorious install you'd be happy as hell that we moved off of it (to anything). We already use github for our commercial offerings so it made more sense to move to github instead of gitorious.org.
At the end of the day, not only does github actually work (unlike our gitorious install - not an issue of gitorious for the record, but of age and issues with the vm it's hosted on), but it's fast and it's a TON easier to manage forks and user contributions.
–Bill
-
I am quite surprised that anyone has objected to us moving. Github is really excellent and is going to ultimately make our lives much easier as Bill stated - letting us focus on code and less on hosting.
-
But am curious why the move to the github site - what was wrong with the other site??
Anyone who asks that obviously didn't work with it much, lot of things didn't work right or were flaky in gitorious. Github is vastly better, we've been using it for our private repos for a couple years and much, much prefer it for many reasons, plus getting rid of one of the biggest PITA jails we have (eventually) will be great.
-
My exp with the old setup was click on the links in the RSS feeds to get the details of the changes - that worked no problems. I could run my playback gitsync and got the new code.
It worked - I was not aware of what issues it might of been to keep it working on the backend.. If this is easier for you than great.
All I can say from an end user point of view is its SLOW as hell with firefox atleast trying to view that merge. I had issues with page at first because they only serve up their CSS via SSL RC4, I had RC4 disabled.
The RSS feed does not show date time of the changes - which I liked!!!
Something on the website that Firefox does not like??
The link to this commit about merge kills firefox
https://github.com/smos/pfsense-ipv6/commit/69be9601ac8fcff7a4afda93d8d32035ec1877e4But like I said I was not aware of the issues you had with the old system - thanks for the info.. github is clearly a major site, just odd what is going on with firefox on the site - and anyone know a way to see the date of the commits in the rss feed on the dashboard?
-
My exp with the old setup was click on the links in the RSS feeds to get the details of the changes - that worked no problems. I could run my playback gitsync and got the new code.
It worked - I was not aware of what issues it might of been to keep it working on the backend.. If this is easier for you than great.
All I can say from an end user point of view is its SLOW as hell with firefox atleast trying to view that merge. I had issues with page at first because they only serve up their CSS via SSL RC4, I had RC4 disabled.
The RSS feed does not show date time of the changes - which I liked!!!
I can only imagine that the RC4 thing is for speed since the only reason to encrypt the CSS is so you don't get a mismatched encryption warning from FF.
Hmm, I don't use a feed reader, but the XML from the ATOM feed looks like it has timestamps. If this is seen in the pfSense dashboard widget, I'll take a look, maybe we were pulling a bad field and it can be easily fixed.
Something on the website that Firefox does not like??
The link to this commit about merge kills firefox
https://github.com/smos/pfsense-ipv6/commit/69be9601ac8fcff7a4afda93d8d32035ec1877e4That's a horrendously large sync. Looks like it has over 1100 changed files, I'm not totally surprised it's making Firefox cry (mine didn't die, but it certainly had massive issues rendering the page). If it's any consolation, I'm reasonably confident that our Gitorious install wouldn't have been any happier with it. I expect other commits should be much happier, that one just happens to be really really large (probably due to a mistake I made in a merge on the upstream repo).
But like I said I was not aware of the issues you had with the old system - thanks for the info.. github is clearly a major site, just odd what is going on with firefox on the site - and anyone know a way to see the date of the commits in the rss feed on the dashboard?
I'll try to take a look at the RSS reader today, if I can see a fix that won't break other feeds, I'll get it pushed.
–Bill
-
As you can see no timestamps on the rss feed on the dashboard
I opened up the settings tab so you could see exact url using - is this wrong?
And even when you open up the actual change from the feed you don't see timestamp on the gitpage – you get how many hours ago it was ;)
But yup when you open up the feed url directly you do see the timestamps - guess something weird in the dashboard widget not pulling the stamp
-
Could you show me the output from the old atom feed in the rss widget? I've looked at the code and I don't see how it's treating what github is sending any different (ie. I don't even see a reference to a date in the code). I know it's not perfect, but if you mouseover the "about 19 hours ago" on github, it'll give you the exact timestamp. Not sure why they went with the 'approximate' method, but I 'spose they never found any huge value in displaying an exacting timestamp on the site (it's probably an asthetic thing shrug).
–Bill
-
That's a horrendously large sync. Looks like it has over 1100 changed files, I'm not totally surprised it's making Firefox cry (mine didn't die, but it certainly had massive issues rendering the page). If it's any consolation, I'm reasonably confident that our Gitorious install wouldn't have been any happier with it.
Gitorious would have just refused to show it entirely, "too large", so it loading at all is definitely an improvement. Gitorious had that nice habit of doing that to small diffs in some circumstances too. That page indeed takes a long time to load but that's just the massive amount of stuff there. Chrome loaded the page about 5* faster than Firefox 4.
