graasp / graasp-deploy Goto Github PK
View Code? Open in Web Editor NEWDeploy Graasp locally, on bare metal, or in the cloud.
Home Page: https://graasp.github.io/graasp-deploy/current/
License: GNU Affero General Public License v3.0
Deploy Graasp locally, on bare metal, or in the cloud.
Home Page: https://graasp.github.io/graasp-deploy/current/
License: GNU Affero General Public License v3.0
Since we might not include type checking in some repos (ie. builder) it would be nice to test it from a workflow.
Remove unused caller templates as they will be moved to .github repository
Use the jacobsvante/tag-major-minor-action action to do so.
Those can be used with v3
If the deployment failed (most probably because the container is faulty) the container will be infinitely mounted.
The solution would be to trigger a new deployment instruction with the latest working container (a previous untagged master?).
NEXT_PUBLIC_APP_VERSION=$npm_package_version
NEXT_PUBLIC_APP_NAME=$npm_package_name
Formatting of the new detected version is broken after #62
They are all show on a single line when they should be on multiple lines.
Add workflow to perform smoke tests, that will also be included as part of the continuous delivery pipeline
We should use versions (tags) and create releases of the workflows to ease the use and update of re-usable workflows.
Although using the commit SHA is the most secure and stable way according to the docs, it means it is less easy to know if the workflow uses the latest version.
So instead of graasp/graasp-deploy/.github/workflows/cintegration-s3-apps.yml@a5e6f97c18c86d97e3e8f15b27e4d898746327cf
we could use graasp/graasp-deploy/.github/workflows/cintegration-s3-apps.yml@v1
graasp
: how to reuse?Use migration tool to version migrations of each plugin:
Generate CloudFormation SDK / CDK directives from higher-level intermediate representation (e.g. Typescript) with dependency graph (see #1)
Starting in version 3, the workflow uses node 16 by default.
Node 12 was used previously and is now deprecated.
Some workflows would need it. For instance, both cypress and type checking need yarn install.
I think it's also valid for all the workflows that require to build.
Here is an example of used cache https://github.com/graasp/graasp-deploy/blob/main/.github/workflows/cypress.yml
Sometimes we don't want to push an app at the same time as everything.
It would be nice to have a "select" between yes/true to decide exactly the stack we want to trigger.
For reference: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Modification should be:
- name: Set output
run: echo "::set-output name={name}::{value}"
To:
- name: Set output
run: echo "{name}={value}" >> $GITHUB_OUTPUT
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.