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.

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

❓ [Question]: what is the birdhouse/templates directory? #499

Open
mishaschwartz opened this issue Mar 6, 2025 · 2 comments · May be fixed by #502
Open

❓ [Question]: what is the birdhouse/templates directory? #499

mishaschwartz opened this issue Mar 6, 2025 · 2 comments · May be fixed by #502
Assignees
Labels
question Further information is requested

Comments

@mishaschwartz
Copy link
Collaborator

Questions

Does anyone still use it?
It seems very out of date with the current configuration.
Can we delete it?

References

Environment

Information Value
Server/Platform URL
Version Tag/Commit
Related issues/PR
Related components
@mishaschwartz mishaschwartz added the question Further information is requested label Mar 6, 2025
@tlvu
Copy link
Collaborator

tlvu commented Mar 6, 2025

It's been there since before I joined Ouranos. Since 5 years, nobody ever asked me about it and I do not use it either.

Looking at the docker-compose.override next to it, it's mostly CRIM hosts. @fmigneault anyone at CRIM still use those?

If not, it's safe to delete I think.

@fmigneault
Copy link
Member

I think they were intended as early recipes to set up common deploy patterns by new users, such as configuring the WPS or THREDDS services for public ports or dev instances.

They are not used on our end.
I think most of these concepts are covered in the docs or specific components READMEs.
No problem to remove.

@mishaschwartz mishaschwartz linked a pull request Mar 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants