Optimised some text in posts
This commit is contained in:
@@ -24,16 +24,12 @@ databases for example.
|
||||
|
||||
Some of the disadvantages (for me):
|
||||
|
||||
- A lot more infrastructure setup (for my setup)
|
||||
- A lot more infrastructure setup
|
||||
- Editing and creating content can be a pain
|
||||
|
||||
**This is to no fault of _HUGO_ itself but the complexity of my infrastructure!!**
|
||||
Deploying the site in my environment was a challenge as I had to get the site
|
||||
files from gitlab and build a docker image that would compile the site as well
|
||||
as create an image to be deployed in my [docker
|
||||
swarm.](https://blog.ahmza.com/posts/building-a-docker-swarm-with-pis) I do feel
|
||||
I made this more complicated than it needed to be, but now that I have it
|
||||
working the workflow is great.
|
||||
Deploying the site in my opinion was a challenge. I feel I made this more
|
||||
complicated than it needed to be, but now that I have it working the workflow
|
||||
is great.
|
||||
|
||||
Because there is no integrated webui or CMS for _HUGO_, the experience
|
||||
you get when creating content will vary person to person depending on
|
||||
|
||||
Reference in New Issue
Block a user