Add instructions of deploying a simple static HTML page #572
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#572
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While the current New Operators Tutorial jumps straight to installing NextCloud, which certainly showcases the power of Co-op Cloud 🥳 🦾 that is a more complex app.
I think it would be useful to have a
helo
recipe which deploys a simple, basic webpage with some cute inviting text + art, and maybe some config values.I support this idea 110%. Maybe a forked https://git.coopcloud.tech/coop-cloud/custom-html?
Docs: add instructions of deploying a simple static HTML pageto Add instructions of deploying a simple static HTML pageOr perhaps now using
parasol-static-site
but that is scoped to sites build with Hugo, which might be good as the default install does a bit more (pulls from a repo, builds, etc.) than thecustom-html
which might be helpful in the learning process.I think there's some value in using an app that (a) people might already be familiar with and (b) demonstrates the power of docker swarm / coop cloud for deploying multiple-service stacks.
I think
custom-html
doesn't satisfy (b) – if someone is just trying to deploy a static HTML page then I guess coop cloud would seem massively overengineered.And possibly
parasol-static-site
is less good than Nextcloud for (a), and maybe even (b)? I'm not sure how many people will be familiar with Hugo, or understand why 2 services would be necessary, compared to things using language-plus-relational-database stack for dynamic functionality.I agree 100%. However, speaking from my own personal experience of trying to migrate sites + apps to Co-op Cloud- I found myself having multiple under used VPS that only served static sites so I wanted to deploy other software to those nodes, but then my brain landed on:
Ok, so if I setup
listmonk.eotl.supply
on the same node aseotl.supply
how do I update my HTML site?To me the question is not "how any are using Hugo?" but rather "how many people are still using Wordpress vs. the Static Sites?" I the think the answer to the later (perhaps while still smaller) is a quite high number and they are quite powerful these days. While
parasol-static-site
currently only works with Hugo, in theory it should be extensible to Jekyll, Pelican, Nuxt, Astro or whatever without too much work. However, the complexity of making any of those easy to update is non-trivial and fiddly.The recipe @decentral1se led on also covers the following:
So I also see the recipe as a simple path to educating new users with some other useful aspects of Co-op Cloud