On 20/07/15 22:32, Colomban Wendling wrote:
Le 20/07/2015 22:28, Enrico Tröger a écrit :
On 20/07/15 14:46, Jiří Techet wrote:
On Mon, Jul 20, 2015 at 11:19 AM, Lex Trotman elextr@gmail.com wrote:
Move plugins.geany.org to github pages. https://pages.github.com/ Attaches right to the repositories where the site source is.
I'm not keen on relying more and more on Github. It's great service they offer, no doubt here. But since we already host some services, especially web pages, I think we should also host plugins.geany.org ourselves.
Totally agreed. BTW, what is plugins2.g.o supposed to be? It exists, but it's mostly broken.
IIRC it was a test installation of Dominic.
Or to the geany server - what matters is just to be far away from SF wherever it is...
That's the plan currently. Already ealier today I emailed Dominic asking to assist in moving plugins.geany.org to the geany server. Just waiting for his feedback.
But I'm afraid we have to wait to SF come back anyway because we probably don't have the release tarballs anywhere else than on SF.
Don't we have at least the latest ones, like on Frank's computer, and the installers on yours?
Ha, you are right. I actually have the tarballs as well as the installer of the last release locally. I'd like to wait for Dominic's feedback but in the worst case, I will have a look tomorrow evening on getting it to work in any way.
Regards, Enrico
If its gonna be hosted on Geany projects server it needs to be HTTPS and that means getting a "real" certificate accepted by browsers.
Cheers Lex
On Tue, Jul 21, 2015 at 6:58 AM, Lex Trotman elextr@gmail.com wrote:
If its gonna be hosted on Geany projects server it needs to be HTTPS and that means getting a "real" certificate accepted by browsers.
HTTPS isn't used for Geany tarballs or binaries from
http://www.geany.org/Download/Releases
so it doesn't have to be used for the plugins either (may be a nice-to-have but not required IMO).
Cheers,
Jiri
On 21/07/15 14:54, Jiří Techet wrote:
On Tue, Jul 21, 2015 at 6:58 AM, Lex Trotman elextr@gmail.com wrote:
If its gonna be hosted on Geany projects server it needs to be HTTPS and that means getting a "real" certificate accepted by browsers.
Could you please elaborate why "it needs" to be reachable via HTTPS? Just for my curiosity.
I will setup the plugins website now and it will be reachable via HTTPS with the same SSL certificate as the main Geany website, the certificate has a wildcard for *.geany.org.
HTTPS isn't used for Geany tarballs or binaries from
http://www.geany.org/Download/Releases
so it doesn't have to be used for the plugins either (may be a nice-to-have but not required IMO).
No doubt on "nice to have". This is the same as for the Geany website itself. We need to solve the certificate issue. Though it is a seperate issue.
Regards, Enrico
On 21/07/15 21:36, Enrico Tröger wrote:
On 21/07/15 14:54, Jiří Techet wrote:
On Tue, Jul 21, 2015 at 6:58 AM, Lex Trotman elextr@gmail.com wrote:
If its gonna be hosted on Geany projects server it needs to be HTTPS and that means getting a "real" certificate accepted by browsers.
Could you please elaborate why "it needs" to be reachable via HTTPS? Just for my curiosity.
I will setup the plugins website now and it will be reachable via HTTPS with the same SSL certificate as the main Geany website, the certificate has a wildcard for *.geany.org.
Done as announced. Though apart from the not "real" certificate, on the Addons plugin page there is a "http://" image references even when accessed via https://. This is the full http:// image URL is hard-coded in the plugin's README. I'll fix this soon. However, this is not a new problem.
There are a few more things we should need to fix:
- the Treebrowser plugin README references an image on Imageshack which is not available any longer - the Markdown plugin README references its images as relative links which is good but I could not find how the deploy scripts in the plugins.geany.org repository will handle these images. So for now, I just copied them into the docroot of plugins.geany.org. I'll leave this up to Dominic once he is available again (currently he is on vacation).
And in general, it seems the plugins' READMEs seem to be in a quite varying state in terms of style. This isn't a big problem but might be improved anyway.
Regards, Enrico
On 22 July 2015 at 05:36, Enrico Tröger enrico.troeger@uvena.de wrote:
On 21/07/15 14:54, Jiří Techet wrote:
On Tue, Jul 21, 2015 at 6:58 AM, Lex Trotman elextr@gmail.com wrote:
If its gonna be hosted on Geany projects server it needs to be HTTPS and that means getting a "real" certificate accepted by browsers.
Could you please elaborate why "it needs" to be reachable via HTTPS? Just for my curiosity.
For the same reason that github went all https, and thats even with all of git's sha checking. I'll bet almost nobody checks the sig of the tarballs.
Cheers Lex
I will setup the plugins website now and it will be reachable via HTTPS with the same SSL certificate as the main Geany website, the certificate has a wildcard for *.geany.org.
HTTPS isn't used for Geany tarballs or binaries from
http://www.geany.org/Download/Releases
so it doesn't have to be used for the plugins either (may be a nice-to-have but not required IMO).
No doubt on "nice to have". This is the same as for the Geany website itself. We need to solve the certificate issue. Though it is a seperate issue.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel