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

deployment to test API #227

Merged
merged 7 commits into from
Jun 26, 2024
Merged

Conversation

sofyalaski
Copy link
Contributor

mounts functional Accounts and assigns respective groups permission to test the API

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any reason why this is a new file, rather than a change in dev/docker-compose.yaml?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For testing I wanted to have an empty database which is maybe not so practical for deploying SciCat for actual development.

@sofyalaski sofyalaski closed this Jun 6, 2024
@sofyalaski sofyalaski reopened this Jun 6, 2024
@sofyalaski
Copy link
Contributor Author

I added an additional service called "test_be_next" and not just a profile (contrary to what we discussed @minottic ). The reason is that for testing another environment file is required.

@minottic
Copy link
Member

minottic commented Jun 6, 2024

thanks. Yes, I think it's unavoidable. I'll propose a small change on Monday, to see if we can reuse part of the existing .env, but looks good otherwise. Thanks!

Copy link
Member

@minottic minottic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are some conflicts to fix, but after that it looks good! as long as we include the jobconfig.json file, I am happy to resolve the other comments in another PR

dev/docker-compose.yaml Outdated Show resolved Hide resolved
dev/config/backend_next/.test_env Outdated Show resolved Hide resolved
dev/config/backend_next/.test_env Outdated Show resolved Hide resolved
dev/docker-compose.yaml Outdated Show resolved Hide resolved
@sofyalaski
Copy link
Contributor Author

I updated the docker-compose as you asked.

Copy link
Member

@minottic minottic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

after resolving the conflicts and adding the extra lines we can merge

Thanks!

dev/config/test_backend_next/.env Outdated Show resolved Hide resolved
dev/docker-compose.yaml Outdated Show resolved Hide resolved
@minottic minottic self-requested a review June 26, 2024 09:50
@minottic minottic merged commit b84cf0e into paulscherrerinstitute:main Jun 26, 2024
23 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants