📂 Web File Browser
Go to file
2015-10-17 08:10:42 +01:00
assets fix save on non-codemirror-editor-pages 2015-09-30 20:47:56 +01:00
browse fix some things 2015-10-17 08:10:42 +01:00
config Remove non-hugo web gen support. See #27. Close #24 2015-10-16 19:34:27 +01:00
editor fix some things 2015-10-17 08:10:42 +01:00
frontmatter change name 2015-09-27 20:01:44 +01:00
templates update 2015-09-27 21:07:29 +01:00
utils Remove non-hugo web gen support. See #27. Close #24 2015-10-16 19:34:27 +01:00
.gitignore add some tests 2015-09-26 13:03:02 +01:00
.travis.yml update travis 2015-09-27 20:10:30 +01:00
Gruntfile.js change editor theme 2015-09-28 21:11:52 +01:00
hugo.go Remove non-hugo web gen support. See #27. Close #24 2015-10-16 19:34:27 +01:00
LICENSE.md updates and grunt 2015-09-16 12:18:12 +01:00
package.json change name 2015-09-27 20:01:44 +01:00
README.md readme changes 2015-09-29 22:17:42 +01:00

caddy-cms

Build Documentation

Powerful and easy static site generator with admin interface. By default it uses Hugo (and you don't need to install it separately) but you can use whatever you want.

Build it from source

If you want to try caddy-cms plugin (and improve it maybe), you'll have to install some tools.

If you want to go deeper and make changes in front-end assets like JavaScript or CSS, you'll need some more tools.

Run it

If you have already installed everything above to meet the requirements for what you want to do, let's start. Firstly, open the terminal and navigate to your clone of caddy-cms. Then execute:

go-bindata [-debug] -pkg assets -o assets/assets.go templates/ assets/css/ assets/js/ assets/fonts/

That command will create an assets.go file which contains all static files from those folders mentioned in the command. You may run with -debug option if you want, but it is only needed if you're going to make changes in front-end assets.

Now, open the folder with your static website and create a Caddyfile. Read the docs for more information about the directives of this plugin.

After creating the file, navigate to that folder using the terminal and run the following command, replacing {caddy-cms} with the location of your clone.

caddydev --source {caddy-cms} hugo

Navigate to the url you set on Caddyfile to see your blog running on Caddy and Hugo. Go to /admin to try the Admin UI.

Everything is working now. Whenever you make a change in the back-end source code, you'll have to run the command above again.

For those who want to make changes in front-end, make sure you have every needed tool installed and run npm install in the root of caddy-cms clone. Then, run grunt watch.