Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Config File Activation #32

Open
efisher008 opened this issue Jul 23, 2024 · 1 comment
Open

Config File Activation #32

efisher008 opened this issue Jul 23, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@efisher008
Copy link
Collaborator

A couple of quick suggestions for the 'Getting Started' page at https://cedadev.github.io/padocc/start.html:

  1. For specifying environment variables please remove the spaces in the example text (below). This caused Bash to interpret them as separate arguments and might be confusing for users simply copying the example.
image
  1. It would be worth explicitly stating that you need to run/execute the config file in order to set the environment variables (e.g. using the command . config <config_file.sh>), which would be useful for beginner shell users.
@efisher008 efisher008 added the documentation Improvements or additions to documentation label Jul 23, 2024
@dwest77a
Copy link
Collaborator

Another suggestion for addition: Add the environment variable declarations to your .bashrc if preferrable.

@dwest77a dwest77a changed the title Setting/activating environment variables in config file Config File Activation Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@efisher008 @dwest77a