-
Notifications
You must be signed in to change notification settings - Fork 204
-
-log=path/to/log.txt- Lets Journey output its log to the specified file instead of the console.
-
-dev- Puts Journey in development mode. Features of development mode are:
- The theme directory is watched for changes to the .hbs files. Upon change, Journey will reload the theme.
- The plugins directory is watched for changes to the .lua files. Upon change, Journey will reload the plugins.
- Puts Journey in development mode. Features of development mode are:
-
-custom-path=/absolute/path/to/custom/folder- After specifying a custom path, the following files/folders will be read from the custom path:
config.json,log.txt,content/ - Note that you need to copy the theme folder from the journey directory to the custom path for this to work. So for the default theme (Promenade) you'd have to copy your-journey-folder/content/themes/promenade to /your/custom/path/content/themes/promenade.
- After specifying a custom path, the following files/folders will be read from the custom path:
-
-http-port=portnumber- Will override the port used for the HTTP server as set in the
config.json. Example:-http-port=8080
- Will override the port used for the HTTP server as set in the
-
-https-port=portnumber- Will override the port used for the HTTPS server as set in the
config.json. Example:-https-port=8081
- Will override the port used for the HTTPS server as set in the
Yes! Refer to Hosting Journey as a Windows Azure Web App for more information.
aneshas is working on one. It's called journey-docker.
Journey uses .lua files placed in your-journey-folder/content/plugins or any of its sub folders to execute custom helpers in theme templates. Refer to Creating a Journey Plugin for more information.
Yes! You can migrate your Ghost blog to Journey easily. Refer to Migrating from Ghost to Journey for more information.
Yes! Files placed in your-journey-folder/content/pages will be served under http://yourblog.url/pages/.
You will find the database in your-journey-folder/content/data/journey.db. Start the sqlite3 shell.
$ sqlite3 content/data/journey.db
sqlite> update users set password='$2a...' where name='your-username';
Replacing your-username with the username you want to reset the password for, and $2a... with the encrypted form of the password. To generate an encrypted password you can use this program.
1. Starting Journey gives me this error: "/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by journey)"
Your Linux distribution ships with an older version of libc6. Try updating libc6.
This may be tricky or not possible on Debian Wheezy stable. That's why there is a Journey release package for Debian Wheezy 64 bit. You can also try that package on other 64 bit distributions.
If all of this doesn't help, you can always compile Journey from source to link against your own version of libc6 (see Building Journey from source).
2. Starting Journey generates this error, but Journey seems to work fine: "UUID.State.init: address error: "
This error stems from the uuid package Journey is using. In most cases, it can be safely ignored. Please open a new issue if Journey behaves strangely after showing you this error.
Check if your theme folder is present. The default theme is Promenade, so there should be files in your-journey-path/content/themes/promenade.
If not, download Promenade and place the "promenade" folder into your-journey-path/content/themes/.
You need to set up yourblog.url/about and yourblog.url/projects by yourself (if you'd like to use the links in the default theme).
Do that by creating a new post in the admin area, give it the title "Projects" (or "About", both without the quotation marks) and make it a static page in the options.