fission-codes / heroku-ipfs-ghost Goto Github PK

The Ghost blog system upgraded with Heroku deploys & IPFS support.

License: MIT License

Shell 13.89% JavaScript 86.11%

heroku ipfs ghost-blog

heroku-ipfs-ghost's Introduction

Ghost Blogging on Heroku with IPFS

Ghost is a free, open, simple blogging platform. Visit the project's website at http://ghost.org, or read the docs on http://support.ghost.org.

Ghost v3.x

Edited the package.json to include the newest 3.x Ghost release and the newest Casper theme
For file storage, uses the IPFS Storage adapter for Ghost connected to the Fission IPFS Add-on for Heroku

This has been forked from the Ghost on Heroku by cobyism, originally written for Ghost v1.x. You can read some other tips in the README there about running Ghost on Heroku. This version only needs your Heroku app name to be configured and it should work right away.

heroku-ipfs-ghost's People

Contributors

Stargazers

Watchers

Forkers

mctaylor17 abhay-ranawat judydotlegal sgt-shaftoe forgondolin agentofuser 0x7d0 benshiue whatthefang wojiaoluyuan jeffgca faizulho unbanksytv devashleyd goodvibesohmly

heroku-ipfs-ghost's Issues

Update README to reflect changes to storage adapter

Update README with the following:

Remove S3 references
Include information about Ghost-Storage-Adapter-IPFS

Coding style guide

A recent PR highlighted the lack of coding style guidelines for this project.

In addition to adding a linter, a popular solution for JS projects is to use Prettier which helps do all the grunt work: https://prettier.io/docs/en/why-prettier.html

This issue could also apply to other repos, but this might be a good place to have the conversation.

Heroku build failing

Hi - the Heroku deploy button wasn't working for me so I hacked it and got a bit further along by using this link:

https://dashboard.heroku.com/new?button-url=https%3A%2F%2Fgithub.com%2Ffission-suite%2Fheroku-ipfs-ghost&template=https%3A%2F%2Fgithub.com%2Ffission-suite%2Fheroku-ipfs-ghost

I got the the attached screen which was looking more promising, however the build failed at the Pruning devDependencies step.

Any help resolving this greatly appreciated thanks!

       
-----> Creating runtime environment
       
       NPM_CONFIG_LOGLEVEL=error
       NODE_ENV=production
       NODE_MODULES_CACHE=true
       NODE_VERBOSE=false
       
-----> Installing binaries
       engines.node (package.json):  12.x
       engines.npm (package.json):   unspecified (use default)
       
       Resolving node version 12.x...
       Downloading and installing node 12.18.4...
       Using default npm version: 6.14.6
       
-----> Installing dependencies
       Installing node modules
       
       > [email protected] install /tmp/build_e652f5ec_/node_modules/dtrace-provider
       > node-gyp rebuild || node suppress-error.js
       
       make: Entering directory '/tmp/build_e652f5ec_/node_modules/dtrace-provider/build'
         TOUCH Release/obj.target/DTraceProviderStub.stamp
       make: Leaving directory '/tmp/build_e652f5ec_/node_modules/dtrace-provider/build'
       
       > [email protected] install /tmp/build_e652f5ec_/node_modules/sqlite3
       > node-pre-gyp install --fallback-to-build
       
       [sqlite3] Success: "/tmp/build_e652f5ec_/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node" is installed via remote
       
       > [email protected] install /tmp/build_e652f5ec_/node_modules/sharp
       > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
       
       info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-linux-x64.tar.gz
       
       > [email protected] postinstall /tmp/build_e652f5ec_/node_modules/core-js
       > node postinstall || echo "ignore"
       
       
       > [email protected] postinstall /tmp/build_e652f5ec_/node_modules/jsonpath
       > node lib/aesprim.js > generated/aesprim-browser.js
       
       added 1082 packages in 22.923s
       
-----> Build
       
-----> Caching build
       - node_modules
       
-----> Pruning devDependencies
       npm ERR! code 1
       npm ERR! Command failed: git checkout beta
       npm ERR! error: pathspec 'beta' did not match any file(s) known to git.
       npm ERR! 
       
       npm ERR! A complete log of this run can be found in:
       npm ERR!     /tmp/npmcache.fVzOl/_logs/2020-09-21T06_11_13_369Z-debug.log
-----> Build failed
       
       We're sorry this build is failing! You can troubleshoot common issues here:
       https://devcenter.heroku.com/articles/troubleshooting-node-deploys
       
       If you're stuck, please submit a ticket so we can help:
       https://help.heroku.com/
       
       Love,
       Heroku
       
 !     Push rejected, failed to compile Node.js app.
 !     Push failed```

Check casper theme in directly

For this to work on Heroku, casper (or whatever theme you're using) needs to get checked in directly to the themes folder.

https://github.com/fission-suite/heroku-ipfs-ghost/tree/master/content/themes

Delete the casper symlink, and check in the theme directly into this folder.

Change app.json to use Fission's Heroku addon

The app.json file currently references env variables for setup. This can be simplified/streamlined by adding Fission's Heroku addon like so:

{
  "addons": [
    "jawsdb",
    "mailgun",
    {
      "plan": "interplanetary-fission:test"
    }
  ],
}

Re-enable minor update (or update documentation)

According to documentation:

Upgrading Ghost

On each deployment, the Heroku Node/npm build process will auto-upgrade Ghost to the newest 3.x version. To prevent this behavior, use npm 5+ (or yarn) to create a lockfile.

During upgrades, package lock was added and package files were changed from ^(minor) to ~(patch) based on a related conversation. These will need to be reverted to allow for the described functionality.

Add configuration for optional IPFS gateway url

See: fission-codes/ghost-storage-adapter-ipfs#6

Dropped support for installing Ghost via npm

Summary

While troubleshooting storage adapter issues, I encountered a comment from the Ghost staff indicating dropped support for installing Ghost via npm. It's unknown how this might impact this project at this time.

Problem

Unknown

Impact

May have development/deployment implications

Solution

Unknown

Detail

Screenshots

Additional context
Via: https://forum.ghost.org/t/ghost-npm-module-contentpath-for-storage-adaptors/6288/9

Update for Ghost 3.x

Newest version of default theme should be included and checked-in.

Have no idea if this will just work by updating package.json and/or what the DB migration is.