Enable Skip deployments to Laconic #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This modification enables Skip to deploy to any number of Laconic Service Providers.
Example (demo, requires backend config): https://skip-go-build.apps.vaasl.io/
We currently deploy to one Service Provider, via this automation.
The
package*.jsonmodifications are a temporary workaround to this issue, in order to force the use ofbuild-webapp.sh, which leverages the added export feature tonext.config.jsThe default
laconic-sonext pipeline requires significant modification tonext.config.jsand various attempts did not product a successful deployment, hence thebuild-webapp.shapproach.Next steps are to obtain credentials and deploy using encrypted config.