[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #21325 [Internal Services/Service - lists]: Installing Schleuder
#21325: Installing Schleuder
---------------------------------------------------+-----------------
Reporter: hiro | Owner: qbi
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Service - lists | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
---------------------------------------------------+-----------------
I have been looking for a solution to have a working test of Schleuder
working on our mail server.
As per now there are two possible approaches. None of them is ideal for
different reasons.
Approach 1:
Schleuder is a Ruby application. More precisely it is installed as a ruby
gem as it is written in Thor (a small framework to write command line
interfaces as a gem)
As other gems, Schleuder has a number of dependencies that it needs to
run. Namely other gems. Some of these gems are just downloaded, some need
to be compiled with native extensions.
These gems are basically written in C and need ruby-dev to be compiled for
your system. Pulling ruby-dev pulls a lot of packages. Some of these we
wouldn't like to keep on the mail server (e.g. having a compiler).
Note that these gems do not need to be compiled system wide. It would be
possible to use either rvm or rbenv to manage ruby versions and bundler to
manage gem dependencies. These can all run as user. Still we will need the
possibility to compile software on the machine (at least during the
deployment phase).
Approach 2:
This involve compiling gems on a different machine and creating deb
packages that will install the required dependencies for the Schleuder
user.
I have left the required packages on:
/srv/schleuder.torproject.org/home/pkg/
This way you can inspect them and see if you are happy with how and what
is going to be installed.
Note that I have compiled this on a test VM that I use locally. There
might be arch mismatch with our mail server that I will need to address
(this is just a test now).
As I said at the beginning there are various pros and cons for each
approach, so before continuing I think it would be beneficial to discuss
this here and agree on a possible solution. Maybe there is also a 3rd
approach that I haven't fully considered, in this case feel free to
propose something and I will investigate it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21325>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs