-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/06/15 13:12, l.m wrote:
> When I check the running Onionoo server at onionoo.torproject.org
> I see it is using Apache. In the installation documentation running
> the web service starts the embedded Jetty. The first question I
> have is: which i
Hello,
When I check the running Onionoo server at onionoo.torproject.org I
see it is using Apache. In the installation documentation running the
web service starts the embedded Jetty. The first question I have is:
which is responsible for the static components of the official Onionoo
server? Does
Hi Luke,
>Django (and by implication, python) are an accepted technology
>at tor, but as much as I wish it would be different, the tor web
>infrastructure is still based on python 2.7 (basically, you can
>only depend on whatever is in wheezy and wheezy-backports if
>you want something to run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/15 23:39, l.m wrote:
> Hi Karsten,
>
>> Not sure what frameworks you have in mind. But I'm happy to hear
>> more about frameworks that would make Onionoo easier to extend
>> and not perform worse (or even better) than now. If you have
>> so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/15 23:04, Tim Semeijn wrote:
> Hey Karsten,
>
> Good to hear more onionoo mirrors are welcome. The instructions
> are nicely detailed so I will be able to try set up onionoo most
> likely next weekend. I will provide you with feedback on the
Hi,
Django (and by implication, python) are an accepted technology at tor, but as
much as I wish it would be different, the tor web infrastructure is still based
on python 2.7 (basically, you can only depend on whatever is in wheezy and
wheezy-backports if you want something to run on tor's in
Hi Karsten,
>Not sure what frameworks you have in mind. But I'm happy
>to hear more about frameworks that would make Onionoo
>easier to extend and not perform worse (or even better) than
>now. If you have something in mind, please say so.
Thanks for the clarification. I'm not against the choi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Karsten,
Good to hear more onionoo mirrors are welcome. The instructions are
nicely detailed so I will be able to try set up onionoo most likely
next weekend. I will provide you with feedback on the instructions.
A feature with a list of fallback
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 22:33, l.m wrote:
> Actually I've been meaning to ask a question related to this. I've
> been wondering if, during the development of Onionoo, you
> considered any other frameworks? I'm not familiar with the history
> of Onionoo so I don't
Hi,
Actually I've been meaning to ask a question related to this. I've
been wondering if, during the development of Onionoo, you considered
any other frameworks? I'm not familiar with the history of Onionoo so
I don't know if you made the choice based on some constraint. I read
the design doc whic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Tim,
On 21/04/15 23:01, Tim Semeijn wrote:
> Improved documentation and process of setting up Onionoo would be
> welcomed by more people, including myself. Busy setting up Compass
> and with Atlas and Globe mirrors active the cherry on the pie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Improved documentation and process of setting up Onionoo would be
welcomed by more people, including myself. Busy setting up Compass and
with Atlas and Globe mirrors active the cherry on the pie would be an
own Onionoo instance (if needed also as backu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/04/15 22:06, nusenu wrote:
> Hi Karsten,
>
>> Though it's very likely easier to parse those directly (possibly
>> using Stem) rather than setting up an Onionoo instance for the
>> exact time you're interested in.
>
> can you say something abo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Karsten,
> Though it's very likely easier to parse those directly (possibly
> using Stem) rather than setting up an Onionoo instance for the
> exact time you're interested in.
can you say something about what amount of minimal memory and disk
sp
14 matches
Mail list logo