Hi thelovekesh,
please make backblaze b2 integrate as storage,
or if it's possible make rclone config integrate ,
waiting for your commits
finest regards

When I try to click the "Deploy" on Heroku button, I get the following error:

Any plans on moving this deployment somewhere else as heroku will no longer be free?

Heroku auto detect that the code violates their terms of usage and doesnt allow the deployment of this repo

Heroku dynos have ephemeral storage so the cloudinary/s3 storage adapters take care of images. But other items such as the all important routes.yaml which is uploaded via Settings>Labs doesn't persist

I already had to find a work around for custom themes uploaded too by committing them into my fork of this repo.

But am not sure where to include routes.yaml / if even possible. Maybe a postinstall script?

I'm new to ghost.

Can anyone help / advise?

Edit 1:

All of Ghost’s routing configuration is defined in content/settings/routes.yaml - which you can edit directly, but you can also upload/download this file from within your Ghost admin panel under Settings » Labs.

seems like overwriting content/settings/routes.yaml with a local committed file will work

Edit 2:

Seems that simply committing my routes.yaml to content/settings/routes.yaml inside this repo works

Closing issue - but will leave for future reference

Mysql (Jawsdb) on Heroku will ignore connection pool settings to spawn a new connection for every alteration. If you're editing posts on Ghost beyond x amount of time (15m for me), it will exceed the database limit and you're effectively locked out.

FWIW I'm on a Nextjs front-end, deployed on Vercel.

I suppose upgrading the database plan might fix this, but a seemingly light activity shouldn't cause this issue to begin with. I would expect needing to upgrade if I was publishing 2-3 blog posts a day, not editing one for two hours 🥲

Reproduction

• Add a couple of posts on Ghost
• EITHER: wait for it to throw the error (which takes me 15-20m), or
• Read the instance APIs using the same stack

EDIT: I have confirmed that the error goes away when you upgrade the database base plan (I did Kitefin -> Leopard), so it's definitely related to the db limit.

When deployed via the button in this repo, I am unable to get the git access to further customize & develop the application.
For example the command heroku git:clone -a APP-NAME returns an empty repo.

However, as per doc, I was able to download code using the below command:

heroku slugs:download -a APP-NAME

But the download is not a git repo. What is the right method to continue development once the deployment is done? For example, how can I make changes in the code or install a new plugin or update the version of ghost deployed to heroku via this repo?

Hello all,

deploying ghost V4 with AWS S3 credentials to heroku gives the following error:
"messageItem could not be created:
We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy.
"

Please check the issue!

Thanks!

Best regards
Gerrit

Hi,

I was successfully able to create an app with the ghost template. But, when I tried cloning it to my local using the git commands, it gives me an empty repo. How do I get the source code of the heroku app into my GIT?

Can you please help me with this issue?

Thanks,
Neha

I get this error message Client request for 4.8 does not match server version 4.2.2 when setting up an app with the deploy button and going to https://YOURAPPNAME.herokuapp.com/ghost.

When trying to deploy on Heroku, I get the following error:

Recreate: Log in to Heroku. Click on the Deploy to Heroku button on the "ghost-v4-on-heroku" github page. Fill out the app name and APP_PUBLIC_URL. Click Deploy app.

The app fails and the above error message pops up in the top right.

Is anyone else experiencing this issue?

Hello,

I would like to update the ghost version to v5 since I need some of the new features. Is it even possible with this repo?

Currently, some users are facing an issue during the deployment of Ghost v4 on Heroku. During the deployment, an error is being shown related to the Heroku policies.

I believe it is due to some outdated project dependencies in Ghost v4.2 and the dependencies might have some vulnerabilities that's why Heroku is unable to deploy the Ghost apps.

Tasks to be done:

• Update Ghost to latest version.
• Update the Nodejs engine in package.json
• Update the JAWS DB Mysql addon with JAWS DB Maria DB

• Bump ghost version manually for now
• Add dependbot action

...got this error on mailgun:

An error was encountered when contacting the add-on partner to create mailgun:starter. Please try again later.

What to do now?

Thanks again!

Best regards
Gerrit

Hi,

Thanks for your job with this plugin 🙏 .

I'm having trouble creating new integrations and don't know why. I'm logged in with role Owner.

See attached screenshot.

This is a fresh install on a heroku dyno by clicking the button on github. Version 4.9.3 with mysql (JawsDB).

Any idea how to proceed with this?

Sidenote: I cannot remove previously created users either only create new ones..

does this app needs a paid account on heroku or it will still use the free tier but somehow heroku just require the cc for this app?

When trying to deploy a new site from your button, I get an error in Heroku:

Is it just me?

Hello,

thanks for the great blog. I cannot start blogging because of:

• security issue is displayed for update 4.48.2
  ghost update
• sign up/sign in shows error, cp. screenshot
• I cannot create post with a picture, upload works, but picture is broken

Best regards
Gerrit

I've used your repo to create a new Ghost v4 site. Thank you!

I updated the Mailgun account so I can send emails. I've updated the DNS settings, SMTP credentials, Mailgun domain, API keys, etc. I've tested these manually using curl and received the email. But when I try to send an email from the website (subscription confirmation), it doesn't work. Mailgun isn't even reporting the attempt.

Are you able to help, please?

Heroku returns the next message, when attempting the deploy:
Item could not be created:
We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy.

I get this

TypeError: Cannot read property 'connection' of undefined        
remote: �[1G           at exports.Provider.sanitizeDatabaseProperties (/app/node_modules/ghost/core/shared/config/utils.js:103:25)        
remote: �[1G           at Object.loadNconf (/app/node_modules/ghost/core/shared/config/index.js:54:11)        
remote: �[1G           at Object.<anonymous> (/app/node_modules/ghost/core/shared/config/index.js:93:27)        
remote: �[1G           at Module._compile (node:internal/modules/cjs/loader:1092:14)        
remote: �[1G           at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)        
remote: �[1G           at Module.load (node:internal/modules/cjs/loader:972:32)        
remote: �[1G           at Function.Module._load (node:internal/modules/cjs/loader:813:14)        
remote: �[1G           at Module.require (node:internal/modules/cjs/loader:996:19)        
remote: �[1G           at require (node:internal/modules/cjs/helpers:92:18)        
remote: �[1G           at bootGhost (/app/node_modules/ghost/core/boot.js:238:18)

Env variables:

APP_PUBLIC_URL:        ●●●●●●.●●●.●●●●●.●●●
DATABASE_URL:          mysql://mysql:●●●●●●●●●●●●@dokku-mysql-●●●●●●:3306/●●●●●●
DOKKU_APP_TYPE:        herokuish
MAILGUN_API_KEY:       ●●●-●●●●●●●●●●
MAILGUN_DOMAIN:        ●●●●●.●●●●●●●.●●●
MAILGUN_PUBLIC_KEY:    ●●●●●●●-●●●●●●●●●●●●●●●●●●●●
MAILGUN_SMTP_LOGIN:    postmaster@●●●●●.●●●●●●.●●●
MYSQL_DATABASE_URL:    mysql://mysql:●●●●●●●●●●●●@dokku-mysql-●●●●●●:3306/●●●●●●
S3_ACCESS_KEY_ID:      ●●●●●●●●●●●●●●●●●●●●
S3_ACCESS_SECRET_KEY:  ●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●
S3_ASSET_HOST_URL:     ●●●●●●.ap-south-1.●●●●●●.●●●
S3_BUCKET_NAME:        ●●●●●●
S3_BUCKET_REGION:      ap-south-1

"We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy."

node thelovekesh.js

TypeError: Cannot read property 'connection' of undefined
at exports.Provider.sanitizeDatabaseProperties (/Users//Repositories/ghost-v4-on-heroku/node_modules/ghost/core/shared/config/utils.js:103:25)
at Object.loadNconf (/Users//Repositories/ghost-v4-on-heroku/node_modules/ghost/core/shared/config/index.js:54:11)
at Object. (/Users//Repositories/ghost-v4-on-heroku/node_modules/ghost/core/shared/config/index.js:93:27)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:93:18)
at bootGhost (/Users//Repositories/ghost-v4-on-heroku/node_modules/ghost/core/boot.js:250:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node thelovekesh.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Hello,
After installing your repo, I git this error message:
Critical security update available — please update Ghost as soon as possible. Details here: GHSA-9fgx-q25h-jxrg

Fixed in 4.3.3, all 4.x sites should upgrade as soon as possible.
As the endpoint is unused, the patch simply removes it.

I have used this version of ghost on three publications but the favicon/publication icon does not work or does not show up.

What I have tried already

• Adding the favicon via the ghost admin settings panel under branding.
• Adding it via code injection in the {{ head }} section.
• Adding it locally by adding the favicon link tag in the theme itself.
• Clearing the browser cache, opened the websites from different devices.
• Clearing the build cache for node apps on heroku.
  All these have failed to work, I have started thinking this could be an issue with ghost itself though I am not sure.
  When I tried using ghost V3, the favicon was showing, but I cant use it on my publications because it doesn't have some core features I like.

Any help on resolving this will be highly appreciated.
Thank you