[yast-devel] A New YaST *.opensuse.org domain?
Hi all, as you probably know we need to move our YaST blog from lizards.opensuse.org to a new place. We decided to use the Jekyll platform hosted at GitHub pages. And it would be nice to have a stable domain name so we do not invalidate the blog URLs when we need to move it again in the future (hopefully that won't happen, but never say never...). For us the easiest way is to obtain some subdomain in the *.opensuse.org domain. So far I found these options 1) yastblog.opensuse.org - to me it looks a bit hard to read and write... 2) yast.opensuse.org/blog - looks nice, we could alias "yast.opensuse.org" to "yast.github.io" and the /blog would work out of box as the prototype is already running at https://yast.github.io/blog. Moreover we would get a nice URL for the main landing page as well. 3) blog.yast.opensuse.org - this would probably make sense only if we needed more *.yast.opensuse.org domains, otherwise it's probably too long... What do you think about it? Any ideas, comments? -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2016-12-06 16:55, Ladislav Slezak wrote:
Hi all,
as you probably know we need to move our YaST blog from lizards.opensuse.org to a new place. We decided to use the Jekyll platform hosted at GitHub pages.
And it would be nice to have a stable domain name so we do not invalidate the blog URLs when we need to move it again in the future (hopefully that won't happen, but never say never...).
For us the easiest way is to obtain some subdomain in the *.opensuse.org domain.
So far I found these options
1) yastblog.opensuse.org - to me it looks a bit hard to read and write...
2) yast.opensuse.org/blog - looks nice, we could alias "yast.opensuse.org" to "yast.github.io" and the /blog would work out of box as the prototype is already running at https://yast.github.io/blog. Moreover we would get a nice URL for the main landing page as well.
3) blog.yast.opensuse.org - this would probably make sense only if we needed more *.yast.opensuse.org domains, otherwise it's probably too long...
What do you think about it? Any ideas, comments?
+1 for #2. And the motivation is fully aethetical.
-- Ladislav Slezák YaST Developer
SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8
-- Devin Waas QA Engineer for Maintenance - SUSE Enterprise Storage SUSE LINUX, s.r.o. CORSO II Krizikova 148/34, 186 00 Prague 8 Czech Republic -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, 6 Dec 2016 16:55:37 +0100
Ladislav Slezak
Hi all,
as you probably know we need to move our YaST blog from lizards.opensuse.org to a new place. We decided to use the Jekyll platform hosted at GitHub pages.
And it would be nice to have a stable domain name so we do not invalidate the blog URLs when we need to move it again in the future (hopefully that won't happen, but never say never...).
For us the easiest way is to obtain some subdomain in the *.opensuse.org domain.
So far I found these options
1) yastblog.opensuse.org - to me it looks a bit hard to read and write...
2) yast.opensuse.org/blog - looks nice, we could alias "yast.opensuse.org" to "yast.github.io" and the /blog would work out of box as the prototype is already running at https://yast.github.io/blog. Moreover we would get a nice URL for the main landing page as well.
+1 and also as bonus we can add link to blog to top of yast github page as fifth top level link. and that reminds me, why not having blog part of yast.github.io? is it problem so we need separate github project?
3) blog.yast.opensuse.org - this would probably make sense only if we needed more *.yast.opensuse.org domains, otherwise it's probably too long...
What do you think about it? Any ideas, comments?
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.12.2016 v 10:12 Josef Reidinger napsal(a):
and that reminds me, why not having blog part of yast.github.io? is it problem so we need separate github project?
Um, it depends, if we want to host the pages at the top level (without any subpath) like at yastblog.opensuse.org then we really need a separate repository. (Actually a separate organization as the yast.github.io repo is already taken.) If we want to use yast.github.io/blog location (or yast.opensuse.org/blog) then we theoretically could include the blog in the yast.github.io repository. But I'd still prefer a separate repository to have them isolated. The problem is that the CSS style and the JS code would be shared, you would need to be very careful to not break something in the other part when doing some changes. With separate repos you simply don't care... -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 12/07/2016 01:26 PM, Ladislav Slezak wrote:
Dne 7.12.2016 v 10:12 Josef Reidinger napsal(a):
and that reminds me, why not having blog part of yast.github.io? is it problem so we need separate github project?
Um, it depends, if we want to host the pages at the top level (without any subpath) like at yastblog.opensuse.org then we really need a separate repository. (Actually a separate organization as the yast.github.io repo is already taken.)
If we want to use yast.github.io/blog location (or yast.opensuse.org/blog) then we theoretically could include the blog in the yast.github.io repository.
But I'd still prefer a separate repository to have them isolated. The problem is that the CSS style and the JS code would be shared, you would need to be very careful to not break something in the other part when doing some changes.
With separate repos you simply don't care...
Well, I'd prefer to care. :-) I'd the blog to just be a section of yast.o.o (the artist currently known as yast.github.io), completely integrated with it. With common style headers, etc... and hosted in the same repo. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.12.2016 v 14:30 Ancor Gonzalez Sosa napsal(a):
Well, I'd prefer to care. :-)
I'd the blog to just be a section of yast.o.o (the artist currently known as yast.github.io), completely integrated with it. With common style headers, etc... and hosted in the same repo.
OK, I tried that in my testing fork, you can see the result at http://blog.ladslezak.cz/blog. Yeah, too many "blog" in the URL, but I already use "blog.ladslezak.cz" for my personal blog so I need to use the "/blog" path prefix to not collide with it. Warning: some features/links are broken because of this prefix, the original yast.github.io page uses absolute paths at some places and does not handle prefix correctly. You can even go directly to the blog index page: http://blog.ladslezak.cz/blog/blog/ Uh, a really ugly URL..., but do not worry, at the real location the URL will look much better. The Current State: ------------------ Works: - Basic post rendering - Blog index pagination - Links between posts - Emoji in posts - Enabled sitemap.xml and feed.xml autogeneration - Added /blog prefix for the blog posts Missing features: - CSS style is completely broken, I need to merge the blog specific tweaks - Syntax highlighting does not work (the same problem) - The images are missing (I need to change the path prefix) - Removed social media sharing buttons (broken styling) - The blog tag and category index pages does not work - A template for the new blog posts (disabled for now) Please, check the prototype, I need a quick feedback. Merging is a bit tricky as the yast.github.io uses different directory layout and config. (Probably from the old Jekyll 2.x?) -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tuesday 2016-12-06 16:55, Ladislav Slezak wrote:
1) yastblog.opensuse.org - to me it looks a bit hard to read and write...
2) yast.opensuse.org/blog - looks nice, we could alias "yast.opensuse.org" to "yast.github.io" and the /blog would work out of box as the prototype is already running at https://yast.github.io/blog. Moreover we would get a nice URL for the main landing page as well.
I'd also go for option #2. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 06.12.2016 16:55, Ladislav Slezak wrote:
2) yast.opensuse.org/blog
+1
I see many potential uses for a yast.opensuse.org domain.
Finally, we'll get to rule the world!
(OK, just a very small part of it, but whatever).
Kind regards
--
Stefan Hundhammer
Dne 6.12.2016 v 16:55 Ladislav Slezak napsal(a):
2) yast.opensuse.org/blog - looks nice, we could alias "yast.opensuse.org" to "yast.github.io" and the /blog would work out of box as the prototype is already running at https://yast.github.io/blog. Moreover we would get a nice URL for the main landing page as well.
Thank you all for the feedback! And the winner is.... 2)! :-) Lukas, could you please ask to create an alias (CNAME) for the "yast.opensuse.org" domain pointing to "yast.github.io"? Thank you in advance! -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 7.12.2016 13:35, Ladislav Slezak wrote:
Lukas, could you please ask to create an alias (CNAME) for the "yast.opensuse.org" domain pointing to "yast.github.io"?
I've asked one particular opensuse.org admin for that after explaining him what and why. He's on vacation, so we'll have to wait a few hours now. Bye Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux Sent from my openSUSE Tumbleweed https://en.opensuse.org/Portal:Tumbleweed -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 7.12.2016 15:07, Lukas Ocilka wrote:
On 7.12.2016 13:35, Ladislav Slezak wrote:
Lukas, could you please ask to create an alias (CNAME) for the "yast.opensuse.org" domain pointing to "yast.github.io"?
I've asked one particular opensuse.org admin for that after explaining him what and why. He's on vacation, so we'll have to wait a few hours now.
So, the result is: Not that easy, but possible. Our friend Theo says: --- cut --- Use software.opensuse.org. This is Ancor's machine, so it would be easy to set it up. Assuming your webpage is static only, you can have a cronjob there to pull in the new code every X minutes. Alternatively, you can use a CI job to trigger a git pull whenever the code changes. Yet another solution would be to use a salt reactor to trigger the git pull. The CI solution is also nice in case your webpage is using a static blog generator, like pelican, where you can submit source files in your git repo, and the CI will compile and deploy if successful. --- cut --- All this has a simple reason, according to current rules, opensuse.org must not be used (even point to, er CNAME) to machines that are not under their control. So the answer is: Allow the content to be available somewhere for "some opensuse.org machine" to download (and maybe process it), ideally done automagically using Jenkins, cron or similarly. Let's decide and then PLS tell Theo what is the expected result and what we want from him (domain, space, ...). Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux Sent from my openSUSE Tumbleweed https://en.opensuse.org/Portal:Tumbleweed -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 8.12.2016 v 13:40 Lukas Ocilka napsal(a):
All this has a simple reason, according to current rules, opensuse.org must not be used (even point to, er CNAME) to machines that are not under their control.
Ouch, what a shame... The beauty of Jekyll + GitHub Pages is that you do not need to care about that at all, everything is automatic and you even do not need any machine for processing, just push to a git a repo and that's it...
So the answer is: Allow the content to be available somewhere for "some opensuse.org machine" to download (and maybe process it), ideally done automagically using Jenkins, cron or similarly.
That's make it quite complicated :-(
Let's decide and then PLS tell Theo what is the expected result and what we want from him (domain, space, ...).
What we need: - Watch the GitHub repo - Build the pages by Jekyll whenever a new commit appears - Upload the generated files to a web server - The webserver can be (or for security reasons should be) very simple, we just need to serve static files (no DB, no PHP/Ruby/whatever) - The required disk space is minimal, the generated site has few megabytes, Jekyll takes ~60MB (without core Ruby) for the build - And of course a new nice domain, that's why we are doing all this... -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (7)
-
Ancor Gonzalez Sosa -
Devin Waas -
Josef Reidinger -
Ladislav Slezak -
Lukas Ocilka -
Stefan Hundhammer -
Steffen Winterfeldt