In `package.json`, change `devDependencies` to `dependencies`. The Heroku build will run the Node.js toolchain to build the assets. After you make this change, add *two* buildpacks: first `heroku buildpacks:add heroku/nodejs` and then `heroku buildpacks:add heroku/ruby`. In that order.

(The following steps assume you are familiar with Heroku, GitHub, Ruby on Rails, Mastodon, etc.)

Mastodon runs on Heroku with just a few minor tweaks. I intend to run a solo instance of Mastodon, and these changes allowed me to run this instance for free [on their free tier] and then upgrade [to their hobby tier or beyond] once it was clear everything was going to work out. My bill is currently $15/month.

now how do I migrate my Twitter tweets...! :-)

aaand it's up and running at https://epiktistes.com/

@Gargron@mastodon.social yes, I initially missed that step when setting it up on Heroku. I'll probably owe the federverse a couple beers for spewing debris while testing this out.

going to wire in https://letsencrypt.org/ next...

@Gargron@mastodon.social thanks! I created my local profile and followed my other profile (on mastodon.social) *before* I got my local configuration correct (specifically `LOCAL_DOMAIN`), so I suspect that resulted in the incorrect `profile_url`. it *should* all be correct on my side now.

I am testing Mastodon (https://github.com/tootsuite/mastodon) on Heroku.

first evidence of activity on other GNU Social/OStatus platforms arrive. life is good!