On Tue, Jan 8, 2019, 20:34 Abhilash Raj <maxking@asynchronous.in wrote:
On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark@msapiro.net> wrote:
On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark@msapiro.net> wrote:
Please help me understand what steps are missing and I will try to provide the information.
Okay.
At the installation stage, you say the following: "I already had some things set up in /opt/mailman including a git subdirectory containing clones of the GitLab mailman, mailmanclient, mailman-hyperkitty, hyperkitty, django-mailman3 and postorius projects. On the third server I have added mailman-suite because I use the settings.py from that project as the basis for mine."
Please assume that the reader is a newbie to python3 virtualenv and give
details of the commands they need to execute to (a) clone all the
On 1/7/19 1:18 AM, Odhiambo Washington wrote: the projects
needed and (b) create the virtualenv.
The next steps are: mkdir /opt/mailman/mm
Then you say "I then created a /opt/mailman/mm directory and within
a
Python 3.6 virtualenv" What happens here is something that needs clarification, because you are specific about "python3.6". I have googled and realized that one has to be specific about the
On Tue, Jan 8, 2019, at 5:52 AM, Odhiambo Washington wrote: that python
version they want to use in their virtualenv as shown here ->
https://stackoverflow.com/questions/45293436/how-to-specify-python-version-u...
exact command to execute to create the /opt/mailman/mm/venv exact command to execute to activate virtualenv
I have added a comment to the page which I hope gives you what you want.
I also added a section on templates instead of referring to a prior version of the page.
That makes it better. However, as a newbie, something is not yet clear:
"When active in a particular shell, it can be deactivated with the command
deactivate or by exiting that shell."
HI am trying to understand the effect of detaching from a venv. I am assuming that a virtualenv is a container that is supposed to be always active for the services within to be accessible. Is that right? So, how do I ensure it's always running/up, or that does not matter as the scripts which run the services will always refer to the files?
virtualenv is not actually a container that is supposed to be active. It is merely a set of settings that are applied to your SHELL when you are in the virtual environment.
It is not supposed to be always active, only when you actually want to run commands in that virtual environment. The services will keep on running after you deactivate your shell and would function like other normal services on your machine.
-- thanks, Abhilash Raj (maxking)
Thank you for clarifying. So once I have a venv created, the services will just run as long as the startup scripts are running even when I'm logged out of the system?