8000 all production server and GUI instances will be run from lsdc_<tla>_prod by JunAishima · Pull Request #301 · NSLS2/lsdc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

all production server and GUI instances will be run from lsdc_<tla>_prod #301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 30, 2023

Conversation

JunAishima
Copy link
Collaborator
  • development clones of LSDC will be located at /nsls2/software/mx/daq/lsdc_ (original clones located in the original location), while production clones have been checked out to /nsls2/software/mx/daq/lsdc__prod

 * development clones of LSDC will be located at
   /nsls2/software/mx/daq/lsdc_<tla> (the original location),
   while production clones have been checked out to
   /nsls2/software/mx/daq/lsdc_<tla>_prod
@JunAishima JunAishima changed the title all server and GUI instances will be run from lsdc_<tla>_prod all production server and GUI instances will be run from lsdc_<tla>_prod Jun 27, 2023
@JunAishima JunAishima changed the base branch from master to 2023-2-amxfmx June 27, 2023 15:46
@@ -1,7 +1,7 @@
#!/bin/bash -l
export PROJDIR=/nsls2/software/mx/daq/
export CONFIGDIR=${PROJDIR}bnlpx_config/
export LSDCHOME=${PROJDIR}lsdc_amx
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the ${CONFIGDIR}daq_env_amx.txt controlled by us or the user? If it is the later anything we are going to rely on being what we set it to should probably be set after the bl specific file.

Similarly, activating a conda env can set ENVS so maybe do that first?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the entire ${CONFIGDIR} should not be editable by the user, we have full control of it.

I have found that it can be tricky to set ENVs, so would rather not touch them if this works

@JunAishima JunAishima changed the base branch from 2023-2-amxfmx to master June 30, 2023 14:39
@JunAishima JunAishima merged commit e3b10b0 into master Jun 30, 2023
@JunAishima JunAishima deleted the update-lsdc-prod-location branch June 30, 2023 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0