build-push-action
nocodb
Our great sponsors
build-push-action | nocodb | |
---|---|---|
31 | 125 | |
3,983 | 42,374 | |
3.5% | 3.6% | |
8.5 | 10.0 | |
2 days ago | 2 days ago | |
TypeScript | TypeScript | |
Apache License 2.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
build-push-action
-
Continuous Deployment with GitHub Actions and Kamal
We use the docker/build-push-action to build the application image. In addition to setting the correct tag, the image build step must also provide a label matching your service name. Because the image should be pushed to your container registry, we set push: true, and because we want ludicrous build speed we instruct the build step to utilize the GitHub Actions cache.
-
Dockerize and Deploy a NodeJS Application to Cloud Run with GitHub Actions
name: Lint and Dockerize the app on: push: branches: [master] pull_request: branches: [master] env: # Use docker.io for Docker Hub if empty REGISTRY: docker.io # github.repository as / IMAGE_NAME: ${{ github.repository }} jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write steps: - name: Checkout repository uses: actions/checkout@v2 - name: Set up Google Cloud uses: google-github-actions/[email protected] with: project_id: ${{ secrets.GCP_PROJECT_ID }} service_account_key: ${{ secrets.GCP_SA_KEY }} # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} # if: github.event_name != 'pull_request' uses: docker/login-action@v1 with: username: ${{ secrets.DOCKER_USERNAME }} password: ${{ secrets.DOCKER_PASSWORD }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action #- name: Extract Docker metadata # id: meta # uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38 # with: # images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image uses: docker/build-push-action@v2 with: context: ./ tags: ${{ secrets.DOCKER_USERNAME }}/magga:latest push: true file: ./Dockerfile - name: Image digest run: echo
-
Automating Tag Creation, Release, and Docker Image Publishing with GitHub Actions
docker/build-push-action@v4 to build and push Docker images with Buildx.
-
How to use notification in gitea actions
Hmmm interesting question... I use the following in my yaml: yaml - name: Build and push uses: https://github.com/docker/build-push-action@v2 can't you just use like: yaml - name: NTFY uses: https://github.com/dawidd6/action-send-mail@v3 and use the actions explained in the links?
-
Where do you commit files for containers that run CI scripts?
Docker made some decent actions free to use like this one to build and push docker images to registries.
- [Darksouls] Remaster pour PC Controller ne fonctionne pas ?
-
Automate Docker Image Builds and Push to GitHub Registry Using GitHub Actions π
name: Docker Image Publish on: push: branches: [ "main" ] # Publish semver tags as releases. tags: [ 'v*.*.*' ] pull_request: branches: [ "main" ] env: # Use docker.io for Docker Hub if empty REGISTRY: ghcr.io # github.repository as / IMAGE_NAME: ${{ github.repository }} jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write # This is used to complete the identity challenge # with sigstore/fulcio when running outside of PRs. id-token: write steps: - name: Checkout repository uses: actions/checkout@v3 # Install the cosign tool except on PR # https://github.com/sigstore/cosign-installer - name: Install cosign if: github.event_name != 'pull_request' uses: sigstore/cosign-installer@f3c664df7af409cb4873aa5068053ba9d61a57b6 #v2.6.0 with: cosign-release: 'v1.11.0' # Workaround: https://github.com/docker/build-push-action/issues/461 - name: Setup Docker buildx uses: docker/setup-buildx-action@v2 # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} if: github.event_name != 'pull_request' uses: docker/login-action@28218f9b04b4f3f62068d7b6ce6ca5b26e35336c with: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action - name: Extract Docker metadata id: meta uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38 with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image id: build-and-push uses: docker/build-push-action@v4 with: context: "{{defaultContext}}:src" push: ${{ github.event_name != 'pull_request' }} # Don't push on PR tags: ${{ steps.meta.outputs.tags }} labels: ${{ steps.meta.outputs.labels }} cache-from: type=gha cache-to: type=gha,mode=max
-
Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions π³π
Build and push Docker image: We will use the docker/build-push-action action to build and push the Docker image to Docker Hub. We will use the following inputs:
-
Show HN: Cross-Platform GitHub Action
I previously tried to use Docker `docker/setup-qemu-action@v2` and `docker/setup-buildx-action@v2` for this purpose (see that example https://github.com/docker/build-push-action#git-context). Thanks to buildkit, platform switching works transparently. However, building on ARM via QEMU on GitHub Actions is terribly slow (something like 5 times more), which is hard to accept. Therefore, full of hope, I am waiting for GitHub Actions to make cloud runners available on ARM, because it is a blocker for the implementation of Graviton on the AWS environment for us.
For a while, the blocker in GitHub Actions for providing ARM support was that Azure doesn't have ARM support. In this way, the Azure cloud offering may determine the habits of AWS consumers.
-
Do I need Dockerhub for CI/CD with Github Actions?
Build and push an image in CI. This extends #2 by pushing the image to a container registry. DockerHub is the default registry in Docker, but isn't the only registry. You could use GitHub's Container Registry as well. We (Docker) have supported GitHub Actions with lots of documentation to help out. You could then extend the pipeline to actually deploy your updated image too.
nocodb
- Show HN: Teable β Open-Source No-Code Database Fusion of Postgres and Airtable
- NocoDB: The Open Source Airtable Alternative
-
Pocketbase: Open-source back end in 1 file
It is great to see the number of good opensource projects in this area. Grist and NocoDB deserve mentions, although more targeted towards database management. It is also amazing that they provide so simple ways to get started (single file/electron)
- https://github.com/gristlabs
- https://nocodb.com/
-
A modern, open-source spreadsheet that goes beyond the grid
Have you seen https://github.com/nocodb/nocodb? I'm not sure it supports concurrent editing, but seems like it might.
- Instantly Turn Your Database into a No-Code Platform
-
Unicorn Startup Airtable Lays Off 27% of Firm, Shifts Focus to Big Clients
Baserow is cool. We evaluated it within our company a few months ago and eventually settled for Nocodb (https://nocodb.com/) - easy to run, more mature.
Leaptable is another Open Source framework like Airtable I saw recently with support for AI Agents. https://github.com/peterwnjenga/leaptable
- Ask HN: Why did Visual Basic die?
- NocoDB Feature Release: Group by and a New Unified Layout
-
Undb β open-source airtable alternative
That looks interesting!
I currently use NocoDB with a MariaDB database, so I can't easily switch over as Undb doesn't support MySQL as I see. But it has the feature I'm missing in NocoDB: a Calendar View which funnily NocoDB promoted on their website but doesn't have [1]. I guess I'll give it a try!
[1] https://github.com/nocodb/nocodb/discussions/832
-
Alternative for Microsoft Access?
You will probably like NocoDB
What are some alternatives?
setup-buildx-action - GitHub Action to set up Docker Buildx
Baserow - Open source no-code database and Airtable alternative. Create your own online database without technical experience. Performant with high volumes of data, can be self hosted and supports plugins
ssh-action - GitHub Actions for executing remote ssh commands.
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes π
metadata-action - GitHub Action to extract metadata (tags, labels) from Git reference and GitHub events for Docker
nocobase - NocoBase is a scalability-first, open-source no-code/low-code platform for building business applications and enterprise solutions.
ghaction-docker-meta - GitHub Action to extract metadata (tags, labels) for Docker [Moved to: https://github.com/docker/metadata-action]
Directus - The Modern Data Stack π° β Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
upload-artifact
appsmith - Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
login-action - GitHub Action to login against a Docker registry
Strapi - π Strapi is the leading open-source headless CMS. Itβs 100% JavaScript/TypeScript, fully customizable and developer-first.