Merge pull request #137 from tbodt/patch-2
Upgrade js-yaml to 3.10.0
|2 years ago|
|controllers||2 years ago|
|coverage||2 years ago|
|docs||2 years ago|
|lib||2 years ago|
|test||2 years ago|
|.dockerignore||3 years ago|
|.env||3 years ago|
|.gitignore||3 years ago|
|.travis.yml||2 years ago|
|CONTRIBUTING.md||2 years ago|
|Dockerfile||3 years ago|
|LICENSE.md||3 years ago|
|README.md||2 years ago|
|config.js||2 years ago|
|config.sample.json||2 years ago|
|config.test.json||2 years ago|
|docker-compose.development.yml||3 years ago|
|docker-compose.yml||3 years ago|
|index.js||2 years ago|
|logo.png||3 years ago|
|package.json||2 years ago|
|server.js||2 years ago|
|siteConfig.js||2 years ago|
|staticman.sample.yml||3 years ago|
|staticman_key.pub||3 years ago|
Static sites with superpowers
Staticman is a Node.js application that receives user-generated content and uploads it as data files to a GitHub repository. In practice, this allows you to have dynamic content (e.g. blog post comments) as part of a fully static website, as long as your site automatically deploys on every push to GitHub, as seen on GitHub Pages, Netlify and others.
It consists of a small web service that handles the
POST requests from your forms, runs various forms of validation and manipulation defined by you and finally pushes them to your repository as data files. You can choose to enable moderation, which means files will be pushed to a separate branch and a pull request will be created for your approval, or disable it completely, meaning that files will be pushed to the main branch automatically.
You can download and run the Staticman API on your own infrastructure, or you can simply use the public instance of the Staticman API for free. If using the public instance, you can skip to Setting up repository.
git clone email@example.com:eduardoboucas/staticman.git cd staticman npm install
cp config.sample.json config.development.json
Edit the newly-created config file with your GitHub access token, SSH private key and the port to run the server. Click here for the list of available configuration parameters.
Start the server.
Each environment, determined by the
NODE_ENV environment variable, requires its own configuration file. When you’re ready to push your Staticman API live, create a
config.production.json file before deploying.
Check this guide if you’re using Docker.
Staticman runs as a bot using a GitHub account, as opposed to accessing your account using the traditional OAuth flow. This means that you can give it access to just the repositories you’re planning on using it on, instead of exposing all your repositories.
To add Staticman to a repository, you need to add the bot as a collaborator with write access to the repository and ask the bot to accept the invite by firing a
GET request to this URL:
If you’re using the public instance, the account you want to add is staticmanapp and the URL is https://api.staticman.net/v2/connect/GITHUB-USERNAME/GITHUB-REPOSITORY.
Staticman will look for a config file. For the deprecated
v1 endpoints, this is a
_config.yml with a
staticman property inside; for
v2 endpoints, Staticman looks for a
staticman.yml file at the root of the repository.
For a list of available configuration parameters, please refer to the documentation page.
Would you like to contribute to Staticman? That’s great! Here’s how:
Are you using Staticman? Let us know!