You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was following the installation instructions provided for the ChEMBL database in a local computer (here).
Facing the requirement to start the postgresql service, two options are suggested:
1- start it manually upon every computer reboot (not so comfortable).
2- start it automatically upon system start by creating a startup script (maybe undesired if preferring to save computer resources in case no action related to the use of postgresql service is expected).
a third option may be included, which in my case worked out as the optimal: start postgresql service upon environment activation / stop postgresql service upon exiting the environment.
I was able to successfully configure those actions following this documentation and the following procedure:
with the corresponding environment activated, determine the ${CONDA_PREFIX} variable;
next, create the corresponding start/stop scripts in the directories CONDA will use to autostart/autostop:
foo@bar:~$ mkdir -p ${CONDA_PREFIX}/etc/conda/activate.dfoo@bar:~$ mkdir -p ${CONDA_PREFIX}/etc/conda/deactivate.dfoo@bar:~$ echo"sudo service postgresql start"${CONDA_PREFIX}/etc/conda/activate.d/start_postgresql.shfoo@bar:~$ echo"sudo service postgresql stop"${CONDA_PREFIX}/etc/conda/deactivate.d/stop_postgresql.sh
With that configuration the service starts and stops as expected,
The text was updated successfully, but these errors were encountered:
Hi,
I was following the installation instructions provided for the ChEMBL database in a local computer (here).
Facing the requirement to start the postgresql service, two options are suggested:
1- start it manually upon every computer reboot (not so comfortable).
2- start it automatically upon system start by creating a startup script (maybe undesired if preferring to save computer resources in case no action related to the use of postgresql service is expected).
a third option may be included, which in my case worked out as the optimal: start postgresql service upon environment activation / stop postgresql service upon exiting the environment.
I was able to successfully configure those actions following this documentation and the following procedure:
With that configuration the service starts and stops as expected,
The text was updated successfully, but these errors were encountered: