Skip to content

Clean up project root#32

Open
jeto wants to merge 1 commit into
masterfrom
cleanup-project-root
Open

Clean up project root#32
jeto wants to merge 1 commit into
masterfrom
cleanup-project-root

Conversation

@jeto

@jeto jeto commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator
  • Move backupSimo.sh, dumpExpl.sh, rebuildSimo.sh to scripts/
  • Delete addHost.sh (replaced by extra_hosts in docker-compose.yml)
  • Delete repeatSimo (Docker restart policy handles this)
  • Delete marker (stale timestamp file from 2019)
  • Delete ml-simo/ (GPU-based GPT-Neo experiment, unused)
  • Delete pybase/ (unreferenced base Dockerfile)
  • Delete virtual_private_simo/ (old standalone bot experiment)
  • Delete features/ml-simo.js (registered no commands, ml-simo container gone)
  • Remove deleted files from Dockerfile ADD

- Move backupSimo.sh, dumpExpl.sh, rebuildSimo.sh to scripts/
- Delete addHost.sh (replaced by extra_hosts in docker-compose.yml)
- Delete repeatSimo (Docker restart policy handles this)
- Delete marker (stale timestamp file from 2019)
- Delete ml-simo/ (GPU-based GPT-Neo experiment, unused)
- Delete pybase/ (unreferenced base Dockerfile)
- Delete virtual_private_simo/ (old standalone bot experiment)
- Delete features/ml-simo.js (registered no commands, ml-simo container gone)
- Remove deleted files from Dockerfile ADD
@Tsarpf

Tsarpf commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

What happens if the simojs process inside docker container crashes now, does the container restart itself? This is why rebootsimo was still being used even in the docker-era.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants