One week ago, I started playing around with Ghost.
This week, I've got my own Vultr Ubuntu 22.04 Ghost site up and running at https://daily.jimcarroll.com
I've got a new theme with it.
Here's what I know:
- I wish I knew back in 2016 that I really should spend more time tagging each post. I've got to do a lot of work now to go through and tag things in a useful way.
- I wish I knew how to find and fix CSS
- I wish I had decided early on to have a consistent image size
But wow - you can accomplish a lot in one week with a fun side project!
Give me a visit and sign up at https://daily.jimcarroll.com
Substack Migrants
Casey Newton @caseynewton Platformer https://www.platformer.news/
Molly White, @molly0xfff, Citation Needed, https://citationneeded.news/, Keep up with the happenings in the tech world without all the boosterism.
Futurist Jim Carroll, @jimcarroll The Daily Inspiration - Futurist Jim Carroll https://daily.jimcarroll.com/, In August 2016, Futurist Jim Carroll began writing his Daily Inspiration post. He has not missed one single working day since he began. Not one.
Daily Inspiration: "Move fast and make things!" - Futurist Jim Carroll
It's long been the key phrase of Silicon Valley - 'move fast and break things' - the entire thinking being that in the race to build a new market and dominate within it, speed is of the essence and that its ok to see a few things go wrong along the way. There's a lot of debate as to whether that is a worthwhile strategy or not, and I won't go into that here.
I've certainly used derivatives of the phrase around here before, suggesting it in the context of fast-moving trends and ideas - you should 'move fast and chase things!'
Or the idea that you should "move fast and fix things,' as an antidote to the whole 'move fast and break things' mantra.
Or that simply the idea of 'moving fast' will help your creativity engine.
But what if you simply move fast and do things? What if you simply set out to do something and get it done, rather than seeing it exist in a state of perpetual implementation and development? What if you started a project and simply finished it? What if you had momentum but didn't let it peter out - but saw an initiative through to completion? You can have an idea, but if you don't implement it, it's a failed idea.
And so that's what I did this weekend with the creation of a new Website for this Daily Inspiration series which can be found at https://daily.jimcarroll.com.
I moved fast and made a thing.
Original post: https://jimcarroll.com/2024/01/daily-inspiration-innovation-speed-move-fast-and-make-things/
Based on a post by @molly0xfff , I was intrigued by the idea of Ghost - and leaving Substack. I read the Platformer newsletter last week about all the controversy and will bail out of there shortly.
I started out creating a site over at Ghost.io, but I like self-hosting my stuff, so on a cold wintry day, I went down the rabbit hole.
I'm a huge fan of RunCloud for my server management, and so I followed this handy guide.
The result is I'm running a new instance for my Daily Inspiration over at https://daily.jimcarroll.com
A shoutout to @markstos for some guidance!
I'll use it as another path to post my Daily Inspiration post, which I have been writing every morning since early August 2016 (when some personal circumstances drove me to a life of clarity.) My next one goes out ... tomorrow morning.
If you could help me stress test my setup by signing up, that would help me out. You might like my posts too. You can leave at any time.
Visit at https://daily.jimcarroll.com
@markstos @molly0xfff I'm less concerned with getting the specifics of the mailgun credentials right for now, and simply getting my JSON right.
gives me these errors.
I've tried eliminating { etc .. but whatever I'm coming up with causes Ghost to fail to start.
Full JSON:
{
"url": "https://daily.jimcarroll.com",
"server": {
"port": 2368,
"host": "127.0.0.1"
},
"database": {
"client": "mysql",
"connection": {
"host": "127.0.0.1",
"user": "ghost",
"password": "xxxxxx",
"database": "xxxxx"
}
},
"mail": {
"transport": "SMTP",
"options": {
"service": "Mailgun",
"host": "smtp.us.mailgun.org",
"port": "587",
"secure": true,
"auth": {
"user": "xxxxxx",
"pass": "xxxxxx"
}
}
}
"logging": {
"transports": [
"file",
"stdout"
]
},
"process": "systemd",
"paths": {
"contentPath": "/home/ghost/webapps/daily/content"
}
}
@markstos @molly0xfff @markstos
@molly0xfff
I've now got a working self-hosted site at https://daily.jimcarroll.com ... managed to get my Substack import working fine. The biggest issue was tuning the server size to accept the import of my file - 897MB.
I'm struggling with the mailgun config though; I'm not familiar with JSON and have tried to run this through a few JSON validators without luck.
@molly0xfff - thanks for your pointer to Ghost - was never really aware of it and I will build out on it now. To build mine - I'm a huge fan of Runcloud.io for server builds - and they had this handy document that made the process all quite straightforward.
https://blog.runcloud.io/ghost/
The nice thing is it configs my server with fail2ban and other hardening, as well as pretty seamless GUI to the rest of the server config.
If anyone can offer up thoughts on my JSON formatting here it would be helpful. This version crashes. (I'm using the basic one for now)
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.