Skip to main content

Develop mode installer

What the FlowDeploy develop mode installer touches.

Linux installer​

Modifies:

  • ~/.bash_profile: appends to bash_profile to set FlowDeploy and workflow manager (e.g. NXF_HOME) environment variables. The automated install will not work if bash_profile isn't used in your environment.
  • /etc/<shared_fs_settings>: creates this directory and creates files with shared file system settings.
  • /etc/fstab: appends automatic mount information for the shared file system.
  • <shared-file-system-mount>: creates this directory for mounting the shared file system

macOS Installer​

Modifies:

  • ~/.zshenv: appends to zshenv to set FlowDeploy and workflow manager (e.g. NXF_HOME) environment variables.
  • The automated install will not work if zshenv isn't used in your environment
  • /etc/<shared_fs_settings>: creates this directory and creates files with shared file system settings.
  • <shared-file-system-mount>: creates this directory for mounting the shared file system
  • /Library/LaunchDaemons/<shared_file_system_daemon>: creates this file with automated mount on boot.

If you're preconfiguring employee Macs (e.g. with JAMF), we recommend only installing macFUSE, and not including additional configuration options. That enables single-command setup, but doesn't share credentials or create an unexpected user experience.

For preconfiguring servers, you can simply create an image after running the FlowDeploy Linux install. Note that this includes authentication information that's used to revoke user access, so make sure individual users do not have unrestricted access to the image or machines created from the image.

Debugging​

Environment Configuration: If you are using a different shell (e.g., zsh on macOS), you may need to set the NXF_HOME environment variable to <shared_mount_point>/.nextflow. This ensures that the default configuration for all Nextflow pipelines points to the shared file system location.