From: Max <maxim.suraev@campus.tu-berlin.de>
To: tantalum <sph@posteo.eu>
Cc: guile-user@gnu.org
Subject: Re: sph.io libraries
Date: Mon, 21 Jul 2014 18:15:54 +0200 [thread overview]
Message-ID: <53CD3CBA.6050804@campus.tu-berlin.de> (raw)
In-Reply-To: <53CD3650.4020708@posteo.eu>
Wow, that sounds like a lot of maintenance burden - have you considered using open
source hosting which specialize on fixing those?
Something like https://gitorious.org/ or http://hub.darcs.net/ depending on your vcs
preference. On a related note - using something like jekyll or hakyll to generate
plain-text website content could solve db issue once and for all while improving
security at the same time.
Getting back to the question which got me interested in your libraries in a first
place - do you have some working examples?
I'm especially curious in 'process' and 'record': I'd like to spawn plenty of
long-running processes while setting env. variable to process-specific value and
saving process pid into some data structure for further interacting with it.
For example, I'd like to spawn proc1 with DISP=X1, proc2 with DISP=X2 etc and I'd
like to save that into record with (proc1, X1, pid1), (proc2, X2, pid2)
How do I implement it using 'process' and 'record' from sph.io? How do I later access
pid2 for example? How do I iterate over all the records?
The existing docs are nice but they are too brief for newbies :(
21.07.2014 17:48, tantalum пишет:
> i am sorry, i am late... i was not subscribed to the list. i maintain
> the site
>
> yes, the site is unstable. despite that, it should always restart
> automatically, please try again, and when you see a 403 that probably
> means it is just starting, 502 that it just crashed ...
>
> at first i had to rewrite the server. that lead to downtimes as i found
> difficulties with sockets and signals, but that should be good now.
> i had a segfault in guile-reader and i just removed the dependency for
> now and try to write at least a bug report for that.
> now, if it crashes again i think it could only be one thing - the
> database, let's see.
>
> until recently there was also a permission problem with the git
> repositories: do you know about the setgid bit? i did not, and any time
> i pushed new changes, the new files got the group of my user and not of
> the git user which made the repository inaccessible to others. now i
> have a test script and will look for continuous integration solutions.
>
> those are things that are hopefully fixed, but what is not yet fixed is
> that i have to take the site down after i added or deleted content (not
> when editing) to import database changes. this is another reason for
> downtimes that i hope to remove some day.
>
> because, as always, there are so many things that can go wrong, if you
> encounter a problem you can mail me at sph@posteo.eu and i will try to
> fix it asap
>
> thanks for you interest
>
next prev parent reply other threads:[~2014-07-21 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 15:48 sph.io libraries tantalum
2014-07-21 16:15 ` Max [this message]
2014-07-21 19:03 ` tantalum
2014-07-21 21:59 ` Max
-- strict thread matches above, loose matches on Subject: below --
2014-07-22 11:12 tantalum
2014-07-08 13:52 Max
2014-07-08 14:50 ` Taylan Ulrich Bayirli/Kammer
2014-07-08 14:53 ` Thompson, David
2014-07-10 11:09 ` Max
2014-07-10 18:56 ` Taylan Ulrich Bayirli/Kammer
2014-07-10 18:59 ` Max
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CD3CBA.6050804@campus.tu-berlin.de \
--to=maxim.suraev@campus.tu-berlin.de \
--cc=guile-user@gnu.org \
--cc=sph@posteo.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).