Add instructions of deploying a simple static HTML page #572
Open
opened 2024-02-13 10:36:20 +00:00 by basebuilder
·
4 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#572
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
helorecipe 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-sitebut 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-htmlwhich 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-htmldoesn'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-siteis 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.supplyon the same node aseotl.supplyhow 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-sitecurrently 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