11 Apr
2016
11 Apr
'16
10:12 a.m.
Hi all,
Goto10 and Puredyne don't exist any more, so links could be taken down
from http://linuxaudio.org/members and
http://wiki.linuxaudio.org/apps/all/puredyne
There are some links in the wiki that would need cleaning up too.
Cheers!
Daniel
11 Apr
11 Apr
5:30 p.m.
hi all!
On Mon, 11 Apr 2016, Daniel James wrote:
Goto10 and Puredyne don't exist any more, so links
could be taken down
from http://linuxaudio.org/members and
http://wiki.linuxaudio.org/apps/all/puredyne
There are some links in the wiki that would need cleaning up too.
just a heads up, to make sure :^)
Dyne.org - and dyne:bolic - keep going
we plan a new version of dyne:bolic as soon as we manage to be done
with Devuan.org - which is an engaging task to say the least.
ciao
--
Denis Roio aka Jaromil http://Dyne.org think &do tank
CTO and co-founder free/open source developer
加密 6113 D89C A825 C5CE DD02 C872 73B3 5DA5 4ACB 7D10
6:05 p.m.
On 04/11/2016 10:12 AM, Daniel James wrote:
Hi all,
Goto10 and Puredyne don't exist any more, so links could be taken down
from http://linuxaudio.org/members and
http://wiki.linuxaudio.org/apps/all/puredyne
There's been an initiative at LAC yesterday to start re-doing the
web-presence. www.linuxaudio.org (9 pages) and the lac.linuxaudio.org
frontpage.
David Runge (miniLAC'16 organizer) started moving it to pelican.
There are some links in the wiki that would need
cleaning up too.
Well, everyone can edit the wiki.
best,
robin
12 Apr
12 Apr
5:40 a.m.
It would be wonderful if someone took the initiative and pushed forward
with maintaining the LAO site. I will gladly hold the fort and ensure we
have uninterrupted service but my time is simply too limited these days to
do much more than that. What we do need to be careful about is implementing
frameworks that may be susceptible to hacking, particularly if/when they
become stale and out of date, as was the case with our last drupal version
of the website. I am personally partial to wordpress because it can be
auto-updated and has generally proved fairly secure... With that in mind,
we need to check what kinds of security concerns pelican framework may have
and whether those can be autopatched--please keep me posted as things
develop. Thank you.
Best,
Ico
On Mon, Apr 11, 2016 at 12:05 PM, Robin Gareus <robin(a)linuxaudio.org> wrote:
On 04/11/2016 10:12 AM, Daniel James wrote:
Hi all,
Goto10 and Puredyne don't exist any more, so links could be taken down
from http://linuxaudio.org/members and
http://wiki.linuxaudio.org/apps/all/puredyne
There's been an initiative at LAC yesterday to start re-doing the
web-presence. www.linuxaudio.org (9 pages) and the lac.linuxaudio.org
frontpage.
David Runge (miniLAC'16 organizer) started moving it to pelican.
There are some links in the wiki that would need
cleaning up too.
Well, everyone can edit the wiki.
best,
robin
_______________________________________________
Consortium mailing list
Consortium(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/consortium
1:46 p.m.
On 04/12/2016 05:40 AM, Ivica Bukvic wrote:
What we do need to be careful about is implementing
frameworks
+1
The idea is to not use any framework.
Pelican [1] is a tool that generates static HTML from markdown (or
reStructuredText). There's nothing to crack.
David got the ball rolling [2], also see his email to LAU.
With that in mind,
we need to check what kinds of security concerns pelican framework may have
and whether those can be autopatched--please keep me posted as things
develop.
see above. The site is generated (usually locally) by the one who edits
it then copied (usually rsync over ssh) to the server.
Given how rarely the site is updated, there are currently no plans to
automate re-generate the HTML automatically. But monitoring or hooking
into git and running pelican on the server to generate the HTML is safe
as long as access to the git repo holding the actual content is.
long story short: As long as ssh is safe, we're good.
best,
robin
[1] http://blog.getpelican.com/
[2] https://github.com/linuxaudio
2:02 p.m.
Hi Robin,
The site is generated (usually locally) by the one who
edits
it then copied (usually rsync over ssh) to the server.
How about maintaining the sources in a shared git repo, then having a
post-commit hook to generate the HTML? Then we could send pull requests
to update pages.
Cheers!
Daniel
13 Apr
13 Apr
1:28 p.m.
hi guys,
cozy to exchange emails with you all after so long :^)
feels good, hope you are all well.
On Tue, 12 Apr 2016, Daniel James wrote:
yes! this is the best approach. Pelican, Middleman (ruby) or what
not. I even ended up writing my own sw for this (webnomad). the
general approach of "baking" instead of "frying" web pages is much
healthier.
and thinking back... of how much contributions web presence really
gathers, in the face of the fact not even the most succesfull project
have this big horde of contributors ready to update webpages... then
how stupid we were all back 10 years ago thinking that dynamic webpage
was ever necessary. and if it really is, then +1 for wordpress, works
great.
ciao*
The site is
generated (usually locally) by the one who edits
it then copied (usually rsync over ssh) to the server.
How about maintaining the sources in a shared git repo, then having a
post-commit hook to generate the HTML? Then we could send pull requests
to update pages.
2934
days inactive
2936
days old
consortium@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Daniel James -
Ivica Bukvic -
Jaromil -
Robin Gareus