Skip to main content
Ctrl+K
freva-deployment 2507.3.0 documentation - Home freva-deployment 2507.3.0 documentation - Home
  • Freva Architecture and Configuration Guide
  • The freva-deployment software
  • After successful deployment
  • Frequently Asked Questions (FAQ)
  • What’s new
    • Contributing
  • GitHub
  • PyPI
  • Freva Architecture and Configuration Guide
  • The freva-deployment software
  • After successful deployment
  • Frequently Asked Questions (FAQ)
  • What’s new
  • Contributing
  • GitHub
  • PyPI

Section Navigation

  • Activation scripts and module files for users
  • Transitioning guide
  • Transitioning of the Plugins
  • Appendix III: Legal notes as flat-pages
  • After successful deployment

After successful deployment#

After all services are set up and running and the core library can be used you will most likely want to configure the system and make and make old freva plugins work within the new system. The chapter provides a glimpse of what’s todo after the system is working.

  • Activation scripts and module files for users
  • Persisent micro service data:
    • Access of service data on the host machine
    • Simple backup scripts:
    • The web UI admin Panel
    • Adding privacy notes and terms of conditions to the Web UI
  • Transitioning guide
    • Transition to new Database
    • Transition to new DRS Config
  • Transitioning of the Plugins
    • Transitioning steps:
    • Transitioning python2 plugins
    • After conda deployment: Increasing reproducibility of your plugin
    • Problem: conda doesn’t finish resolving dependencies
  • Appendix III: Legal notes as flat-pages
    • Privacy statement
    • Terms of use

previous

Example deployment configuration

next

Activation scripts and module files for users

© Copyright 2025, DKRZ - CLINT.

Created using Sphinx 8.2.3.

Built with the PyData Sphinx Theme 0.16.1.