gitwig-package | the gitwig static site generator
kandi X-RAY | gitwig-package Summary
kandi X-RAY | gitwig-package Summary
gitwig-package is a Python library. gitwig-package has no bugs, it has no vulnerabilities, it has build file available and it has low support. You can download it from GitHub.
gitwig is another of these blog enabled static site generators. You want some more buzzwords? It’s written in [python][py], uses [markdown][md] for the content and [genshi][ge] as a templating engine. As a bonus [git][gi] is used for deploying the content to the server. What makes it different from the other projects? Well most of them don’t combine them in the way I like :-) The main focus here is, that the rendering of the content to HTML happens on the server and not locally on my machine. This has the main advantage is, that I don’t have to wait for my laptop to finish the rendering and deploying all the changes to the server. The main disadvantages might be that there is no good error reporting in place and that the rendering might take longer.
gitwig is another of these blog enabled static site generators. You want some more buzzwords? It’s written in [python][py], uses [markdown][md] for the content and [genshi][ge] as a templating engine. As a bonus [git][gi] is used for deploying the content to the server. What makes it different from the other projects? Well most of them don’t combine them in the way I like :-) The main focus here is, that the rendering of the content to HTML happens on the server and not locally on my machine. This has the main advantage is, that I don’t have to wait for my laptop to finish the rendering and deploying all the changes to the server. The main disadvantages might be that there is no good error reporting in place and that the rendering might take longer.
Support
Quality
Security
License
Reuse
Support
gitwig-package has a low active ecosystem.
It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
gitwig-package has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of gitwig-package is current.
Quality
gitwig-package has no bugs reported.
Security
gitwig-package has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
gitwig-package does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
gitwig-package releases are not available. You will need to build from source code and install.
Build file is available. You can build the component from source.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gitwig-package
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gitwig-package
gitwig-package Key Features
No Key Features are available at this moment for gitwig-package.
gitwig-package Examples and Code Snippets
No Code Snippets are available at this moment for gitwig-package.
Community Discussions
No Community Discussions are available at this moment for gitwig-package.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gitwig-package
A short notice: To destinquish between server and local commands I will use s> for the server and l> for local commands.
setup the hub repository: s> git init --bare --shared blog-hub.git
clone the live repository: s> git clone <path to hub> blog-live
download the [example blog][7] into the live repository, don’t clone it!
push the changes to the hub: s:live> git add -A s:live> git commit -m "import of example blog" s:live> git push origin master
download this project on your server and run python setup.py install
in the direcotry files are six files that need your attention. You will need to move them to their destination as noted below and (except for the `config.yaml` file) you'll need to adjust the file paths in them and set the execution bit
bare-post-update-hook.sh → blog-hub.git/hooks/post-update This will pull any changes from the `hub` to the `live` repository.
live-post-merge-hook.py → blog-live/hooks/post-merge This will render the changes after they were pulled from the `hub`.
live-post-commit-hook.sh → blog-live/hooks/post-commit This will push any changes commited to the `live` repository to the `hub` and render the site.
gitwig-update.py → in your $PATH as gitwig-update This script is run to render the site. You might need to adjust the locale in the script. If you want to change some things – for example adding code highlighting – this is your starting point.
gitwig-inbox.py → in your $PATH as gitwig-inbox This script is to process the `inbox` folder in your live or local directory.
config.yaml → blog-live/ All config possibilities can be found in the `settings.py` module of the `gitwig` package.
Adjust your webserver path to point to the deploy directory and the static directory. On my server I keep the deploy directory outside of the live directory and use a symlink to the static directory inside the live repository.
you’ll need get a copy of the gitwig-inbox.py file and put it somewhere in your $PATH as gitwig-inbox. Don’t forget to adjust the paths in the file and set the execution bit.
setup the hub repository: s> git init --bare --shared blog-hub.git
clone the live repository: s> git clone <path to hub> blog-live
download the [example blog][7] into the live repository, don’t clone it!
push the changes to the hub: s:live> git add -A s:live> git commit -m "import of example blog" s:live> git push origin master
download this project on your server and run python setup.py install
in the direcotry files are six files that need your attention. You will need to move them to their destination as noted below and (except for the `config.yaml` file) you'll need to adjust the file paths in them and set the execution bit
bare-post-update-hook.sh → blog-hub.git/hooks/post-update This will pull any changes from the `hub` to the `live` repository.
live-post-merge-hook.py → blog-live/hooks/post-merge This will render the changes after they were pulled from the `hub`.
live-post-commit-hook.sh → blog-live/hooks/post-commit This will push any changes commited to the `live` repository to the `hub` and render the site.
gitwig-update.py → in your $PATH as gitwig-update This script is run to render the site. You might need to adjust the locale in the script. If you want to change some things – for example adding code highlighting – this is your starting point.
gitwig-inbox.py → in your $PATH as gitwig-inbox This script is to process the `inbox` folder in your live or local directory.
config.yaml → blog-live/ All config possibilities can be found in the `settings.py` module of the `gitwig` package.
Adjust your webserver path to point to the deploy directory and the static directory. On my server I keep the deploy directory outside of the live directory and use a symlink to the static directory inside the live repository.
you’ll need get a copy of the gitwig-inbox.py file and put it somewhere in your $PATH as gitwig-inbox. Don’t forget to adjust the paths in the file and set the execution bit.
Support
I should define this a little bit more. With "blog support" I mean the automatic creation of daily, monthly, yearly and tag indices. And of cause a blog page, an atom feed and a tag overview page.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page