some small thing...
the why
The advice to own your content, requires control of the content platform, on which you publish.
I have chosen to build and run my own.
Firstly to truely own the platform and content.
Also to do something practical, to create some small thing.
And deploy it.
There were a few side quests to solve problems to get it all working.
And I still need to apply some CSS to make it beautiful.
But now it’s up I can start writing, and share some stories and ideas.
the tech
I have selected Elixir, Phoenix and NimblePublisher as the language, web framework and content tool respectively.
Deploying onto fly.io
NimblePublisher doesn’t use a database.
Instead it is file based, each file composed of metadata and content formated using markdown.
This has a number of benefits, especially for managing content, in specific contexts.
NimblePublisher is not meant as a multi-user content management system.
It’s more a content library on which a specific content system is built.
I used this piece on the use of NimblePublisher and NimblePublisher’s documentation to help me build my content platform.
Deployed into fly.io, tweaked DNS, created certs, and here we are.
I tried to deploy from GitHubs Codespaces, as I wouldn’t mind coding, writing and deploying from the iPad.
But that’s a side quest I have yet to complete. (Deploy to fly.io fails)
meta
by Chris EstherTags: tech, elixir, phoenix