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

Build a SSP debug SP #13

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Build a SSP debug SP #13

wants to merge 3 commits into from

Conversation

MKodde
Copy link
Member

@MKodde MKodde commented Nov 28, 2022

No description provided.

@MKodde MKodde force-pushed the feature/ssp-test-sp branch 2 times, most recently from b30dcdb to 65658e4 Compare November 28, 2022 13:40
@MKodde MKodde requested a review from quartje November 28, 2022 13:40
# Install Composer
COPY --from=composer /usr/bin/composer /usr/local/bin/composer

# Fix npm
Copy link
Contributor

Choose a reason for hiding this comment

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

NPM is not installed. Do you really need these steps?

# Install SSP: Clone and install rev adf1eb8 of SSP
WORKDIR /var/simplesamlphp/
RUN git clone https://github.com/simplesamlphp/simplesamlphp.git /var/simplesamlphp
RUN git reset --hard adf1eb8
Copy link
Contributor

Choose a reason for hiding this comment

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

Why the --hard reset here? And not a tag or a version?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point, I want to install this specific revision as it is also used in the Stepup-deploy SSP task. Using gir reset works for me in that respect.

As a step forward for this, I'd like to go to a more recent SSP version. But we might not be compatible with those versions yet. Given we use some older SSP constructions in the debug sp module.

@@ -0,0 +1,42 @@
FROM webdevops/php-nginx:7.2 AS ssp-debug-sp
Copy link
Contributor

Choose a reason for hiding this comment

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

Why the "ancient" 7.2 and not 8.1 ?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point, and I tested if we could use a more recent version. But the currently installed SSP version restricts us to using a 7.2 PHP.

@MKodde MKodde force-pushed the feature/ssp-test-sp branch 8 times, most recently from e3b4f2d to 4b5d0e6 Compare December 1, 2022 08:20
@MKodde MKodde force-pushed the feature/ssp-test-sp branch 4 times, most recently from 6303bcd to e24e14c Compare December 1, 2022 14:17
@MKodde MKodde force-pushed the feature/ssp-test-sp branch 3 times, most recently from e295c3b to a299d29 Compare December 5, 2022 07:46
@MKodde MKodde force-pushed the feature/ssp-test-sp branch from a299d29 to e9e1452 Compare December 5, 2022 07:49
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