-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add ability to install custom Stata packages #25
Comments
PLUS should be set to within the project space, so it can be seen by the researcher running the code, though a fully encapsulated docker image wouldn't care where it is installed. This is more for transparency than reproducibility.
|
Does "project space" equate to our "tale workspace"? Because our workspace is mounted at runtime, to be built into the Docker image any packages would need to be installed outside of the workspace. Packages can be installed into the workspace at run time and would be included when exporting/publishing, etc, but not as part of the the built image. But I may have misunderstood. |
sorry for confusion. Any installed packages should be installed for a given tale, not for a given user, at build time of the Docker image (not at runtime of the code running within the Docker). In essence, best practice is NOT to install live, but install only once, when building the Docker image. Note that this should be the same paradigm as for Python, R, etc. |
For environments and package managers other than STATA, custom packages can be declared and installed at image build time instead of run time (e.g., apt.txt, requirements.txt, install.R, toolboxes.txt).
We need to support both
ssc
andnet install
commands. Both of these appear to use thePLUS
system directory, which is by default in~/ado/plus/
.I propose that we add support for an
install.do
file (similar toinstall.R
) that would be run at build time. Each line can be an arbitrary Stata command, but intended forssc
ornet install
. For example:install.do
:I think it might make sense to change the PLUS sysdir to something outside of ~, such as:
The text was updated successfully, but these errors were encountered: