No description
- JavaScript 80.3%
- Dockerfile 7.2%
- CSS 6.2%
- Jinja 4.8%
- HTML 1.5%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| public | ||
| src | ||
| templates | ||
| test/.devcontainer | ||
| .dockerignore | ||
| .env | ||
| .gitignore | ||
| Dockerfile | ||
| down.yml | ||
| index.html | ||
| local.yml | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| TotalArchitecture.md | ||
| vars_prompt_test.yml | ||
| vite.config.js | ||
forgejo GPU appliance
absolute control over your data
This is a playbook to run foregjo as a DIN rail appliance with CUDA drivers and web-devcontainers. The idea is to use it to prototype, build, and continuously deploy models that run on the edge, in react-native, a pwa or an ipc.
ansible-playbook local.yml
HOST_UID=$(id -u) HOST_GID=$(id -g) docker compose up -d
- Note: I will add the docker compose up -d to the playbook
When you first bring up a dev container, run the following tasks.
git config user.name "Your_name_here"
git config user.email "Your_email_here"
git config local http.extraHeader "Authorization: token your_forgejo_token_here"
TODO
- finish refresh token and get git username and email in the project
- launch devcontainer without code-server add on
- get wordpress working well enough for Kelly to use it as a content management system
- speak with Kelly
- develop custom element for launching, updating, deleting and listing dev containers for a user, repo and branch. Integrate in forgejo
- add CUDA drivers
- install on gpu server
- make hyperdx and borgbackup appliance
- meet with Steve and Ernie for a demo