Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

strapi-plugin-update-static-content

Package Overview
Dependencies
Maintainers
0
Versions
17
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

strapi-plugin-update-static-content

An strapi plugin to rebuild and deploy your SSG website via Github Actions.

  • 3.0.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
120
decreased by-3.23%
Maintainers
0
Weekly downloads
 
Created
Source

Update Static Content - Strapi v4

Update your statically generated site with github actions (more coming on the way).


strapi plugin update static content logo

Plugin Previews

Plugin Settings

strapi plugin update static content configuration

Plugin Page

strapi plugin update static content plugin


Features

  • Workflow History
  • Trigger multiple workflows
  • Config Page
  • Downloading Logs
  • Roles to access the plugin
  • Strapi Permissions in v1.0.7

Installation

  yarn add strapi-plugin-update-static-content
  OR
  npm i strapi-plugin-update-static-content

Plugin Configuration

  1. Create a JWT BASE64 secret key

    For example with : openssl rand -base64 32

  2. Add the key in the .env

  3. Add plugin configs inside strapiProject/config/plugins.js

module.exports = ({ env }) => ({
  'update-static-content': {
    enabled: true,
    config: {
      JWT_SECRET: env('JWT_SECRET'),
    },
  },
});

NOTE: add roles property (roles: ['strapi-super-admin', 'strapi-editor', 'strapi-author']) if you are using the plugin lesser than v1.0.7 since above that version it is handled by Strapi Permissions.

  1. Create a file in the root of your project .github/workflows/deploy.yml like below. In this example we are using fing cloud
name: Fing Deployment # a name for your workflow

on: # trigger on push event and main branch to the repo
  push:
    branches: [main]
  workflow_dispatch: # must be included in your .yml file for manually triggering event
defaults: # in case of monorepo project you can use `defauls` and choose the subfolder
  run:
    working-directory: ./gatsbyJS
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2
      - name: install fing-cli and deploy
        env: # set the cloud provider token to the secrets on github and use it on run
          TOKEN: ${{ secrets.FING_TOKEN }}
        run: | # write your shell scripts for deploying or building based on your host provider
          npm install -g @fingcloud/cli
          fing --access-token "${TOKEN}" up --app vahoora-gatsby --dispatch
  1. Create a GitHub Personal Access Token on Github : https://github.com/settings/tokens

    See more on the Github Documentation

  2. Then, you can add the workflow in the plugin settings from the admin panel, save and you'll be able to trigger your workflows from strapi.

Usage

  1. Add the workflow in the plugin's settings admin/settings/update-static-content
  2. Trigger a build in the plugin page

Roadmap

  • Cancel workflow manually.
  • Better documentation.

Special Thanks

Reza from Fing

Keywords

FAQs

Package last updated on 09 Aug 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc