- CSS 43.4%
- HTML 29.9%
- JavaScript 26.7%
|
Some checks failed
deploy / deploy (push) Failing after 16s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| assets | ||
| deploy | ||
| .gitignore | ||
| config.js | ||
| index.html | ||
| README.md | ||
moweb.ro
Static site. No build step — edit files, copy to server.
Edit content
config.js — name, tagline, message, email, links, company details. Empty value hides that part.
Change look
assets/css/style.css — colors and font in :root at the top. Background objects are the <svg class="obj"> elements in index.html; position them in the .o-* rules.
Add a page
Copy index.html to e.g. about.html, replace <main> content. Same CSS/JS apply. nginx serves /about thanks to try_files $uri.html.
Deploy (Proxmox LXC, Debian/Ubuntu template)
apt update && apt install -y nginx
mkdir -p /var/www/moweb
cp deploy/nginx.conf /etc/nginx/sites-available/moweb.ro
ln -s /etc/nginx/sites-available/moweb.ro /etc/nginx/sites-enabled/
rm /etc/nginx/sites-enabled/default
nginx -t && systemctl reload nginx
Upload from Windows: scp -r index.html config.js assets root@<lxc-ip>:/var/www/moweb/
HTTPS: apt install -y certbot python3-certbot-nginx && certbot --nginx -d moweb.ro -d www.moweb.ro (needs ports 80/443 forwarded to the LXC), or terminate TLS on an existing reverse proxy.
Auto-deploy (Forgejo Actions)
.forgejo/workflows/deploy.yml rsyncs the site to the LXC on every push to main.
One-time setup:
- Enable Actions for the repo and have a Forgejo runner registered (label must match
runs-on, defaultdocker). - On the LXC:
apt install -y rsync useradd -m -s /bin/bash deploy chown -R deploy:deploy /var/www/moweb - On your PC, make a dedicated key:
ssh-keygen -t ed25519 -f moweb_deploy -N "". Putmoweb_deploy.pubin/home/deploy/.ssh/authorized_keyson the LXC. - Repo secrets:
DEPLOY_HOST,DEPLOY_USER(=deploy),DEPLOY_SSH_KEY(contents ofmoweb_deploy),DEPLOY_KNOWN_HOSTS(output ofssh-keyscan <lxc-ip>).